Migration 2.2.7 -> 3.1.1 no "Private" Marks
Hello,
after we have updated our Gemini from 2.2.7 to 3.1.1 all the "private" tags gone. This affected a complete Issue and single Comments.
Is there any resolution for this problem?
AmaIT
· 1 |
|
Sunday, February 22, 2009, 7:29:43 PM |
0
|
Hello, |
||||
|
0
|
Hello, |
||||
|
0
|
The "private" issues are nothing to do with roles. It is just if you belong to the user group (project or global). So say you want only Manager (global group) to see an issue, then only user who is in the Manager global group (you assign this in edit user in admin) will see the issue. |
||||
|
0
|
Hello, is a SQL script available, which can switch the private mark to a custom visibility? Like, for example: if privatemark = true and projectid = 0815 Or can we do this over a batch functionality? |
||||
|
0
|
Unfortunately, there is no batch update for this. You could create the update in SQL by checking the old issues table for the private flag and setting the relevant visibility group in the new gemini_issues table. |
||||
|
0
|
now my question is that if such a major change is introduced, it should have something ready for this issue to resolve. I can not check all the Issues by hand or write a script at my own risk for a supported productiv system. |
||||
|
0
|
It is migrated, to the private group, but you might need to tweak the security around it. This is because we have changed the security model in 3.x. |
||||
|
0
|
I understand, but after migration the privat call have no visibility mark. So i have to chance each call and comment visibility to the target group. I cannot believe that we are the only ones with this problem. |
||||
|
0
|
Create a global group for user who can see private issues and note that group id (hover over the link to it) then run the SQL below with the group id. UPDATE gemini_issues SET visibilitymembertype = 2, visibility = YOUR GROUP ID WHERE issueid IN (SELECT issueid FROM issues WHERE isprivate=1) |
||||
|
0
|
thanks for this answer. we will test it asap. |
||||
|