Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Private comments from old Gemini are not visible to our project groups

web-app

Hello,

We migrated our Gemini v2.2.6 to v3.7.1 recently and noticed next issue.
Exist private comments are not visible to our custom project groups like Developers, Testers, Customers while they are to another custom project group - PMs.
All those groups have different permissions set, and PMs has the most powerful permissions.
The problem is that I cannot see how could I configure it that Developers, Testers could see old private comments together with PMs, while Customers should not see them.
Which particular permission in security scheme defines that? Could someone help me?

slava.boyko
· 1
slava.boyko
Replies (15)
helpful
0
not helpful

Sure, create another group (say internal) and add all testers, developers and managers to it.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Hmm, not sure that I got it...
If I create such group, then I need additionally include all users from testers, developers and managers groups to that group on all projects (groups in groups feature would be good there actually). That is not efficient.
But anyway which permission exactly I should give to that group, so that its members could see old migrated private comments?


slava.boyko
· 1
slava.boyko
helpful
0
not helpful

No permissions needed for that group. It is just so you can limit the visibility to internal users.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Ok, but could you please describe with more details which steps I should do after I created new Internal group and added all users from Developers, Testers and PMs to that group for all projects.


slava.boyko
· 1
slava.boyko
helpful
0
not helpful

Edit the comment(s) in question and set the visibility of them to that new group.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

This is not an option unfortunately. There are couple of thousands private comments.
I think we probably  need sql script to update all exist private comments and set visibility.


slava.boyko
· 1
slava.boyko
helpful
0
not helpful

You can do this is SQL:
update gemini_issuecomments set visibility = NEW GLOBAL GROUP ID, visibilitymembertype =2 /* Gloabl Group */ where visibility = YOUR CURRENT PRIVATE VISIBILITY


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Thank you.
But we have a request to make those exist (old migrated) private comments should be visible to only Developers and Testers project groups while they should not be visible for Customers project group.
Could you please adjust mentioned sql query for that?


slava.boyko
· 1
slava.boyko
helpful
0
not helpful

Sure: update gemini_issuecomments set visibility = NEW PROJECT GROUP ID, visibilitymembertype =3 /* Project Group */ where visibility = YOUR CURRENT PRIVATE VISIBILITY


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

The problem is that we have up to 3 project groups that should see those comments. And we don't really want to create a new project group and then add all of users from those up to 3 groups to new one and then run script with this new group id as a NEW PROJECT GROUP ID.
But seems there is no other way because it is purposed to set Visibility to only one group (not multi-select), right?

Another confusing thing - I see next in geminiissuecomments table:
old comments mostly have '8' in 'visibility' field and '2' in  'visibilitymembertype' field.
But I don't see any global (and even project) group with such id in database (gemini
globalgroups and gemini_projectgroups tables). I cannot understand this, is this is upgrade issue? As I see there even was not visibility feature in v.2.2.6, so from where this '8' id come?


slava.boyko
· 1
slava.boyko
helpful
0
not helpful

Correct, you can only select one group as visibility.

As for the existing data, did you delete any groups after migration?


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Ok.
Yes, I deleted all Global Groups except 3 system ones that cannot be deleted.
So you mean that all private comments' visibility was set to some global group during migration process?


slava.boyko
· 1
slava.boyko
helpful
0
not helpful

Yes, we create a new global group for that during migration.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

It would actually really nice if Visibility field is multi-select field instead of drop-down...

What do you think about next workaround that should be quick.
We actually are not going to use global groups - instead we created 4 project groups and manage security in that way.
1. But we would create a new global group called "<our company name>Employees". Then add all our employees (developers, testers, PMs etc) to that group. This is quick.
2. When we want to use "private comments" (like 2.2.6 old style), then when for example our developer creates a comment and set Visibillity to "<our company name>Employees" group. That this comment is visible internally, but not visible for our customers.
And other security is still managed on per project level using project groups.
3. Also, we could run mentioned sql query to make all those private comments visible to "<our company name>Employees" group


slava.boyko
· 1
slava.boyko
helpful
0
not helpful

Yes, that will work.


Mark Wing
· 9108
Mark Wing