Private comments from old Gemini are not visible to our project groups
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 |
|
Wednesday, September 8, 2010, 3:10:10 PM |
0
|
Sure, create another group (say internal) and add all testers, developers and managers to it. |
||||
|
0
|
Hmm, not sure that I got it... |
||||
|
0
|
No permissions needed for that group. It is just so you can limit the visibility to internal users. |
||||
|
0
|
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. |
||||
|
0
|
Edit the comment(s) in question and set the visibility of them to that new group. |
||||
|
0
|
This is not an option unfortunately. There are couple of thousands private comments. |
||||
|
0
|
You can do this is SQL: |
||||
|
0
|
Thank you. |
||||
|
0
|
Sure: update gemini_issuecomments set visibility = NEW PROJECT GROUP ID, visibilitymembertype =3 /* Project Group */ where visibility = YOUR CURRENT PRIVATE VISIBILITY |
||||
|
0
|
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. |
||||
|
0
|
Correct, you can only select one group as visibility. |
||||
|
0
|
Ok. |
||||
|
0
|
Yes, we create a new global group for that during migration. |
||||
|
0
|
It would actually really nice if Visibility field is multi-select field instead of drop-down... |
||||
|
0
|
Yes, that will work. |
||||
|