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.




Migration 2.2.7 -> 3.1.1 no "Private" Marks

web-app

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
AmaIT
Replies (10)
helpful
0
not helpful

Hello,

You should find that Private Issues/Comments are visible only to those users in the migrated "Private Issues" Global Group.

Remember: private issues have been replaced by Issue\Comment Visibility -- you select which group can view the issue or comment.



Harvey Kandola
· 212
Harvey Kandola
helpful
0
not helpful

Hello,
thank you!

Could you explain us through an example, how to set the roles, the global or project gruops and the schemes correctly, that the private issues can be seen and managed only by the allowed users, please.


AmaIT
· 1
AmaIT
helpful
0
not helpful

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.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

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
then set visibility = groupA

Or can we do this over a batch functionality?


AmaIT
· 1
AmaIT
helpful
0
not helpful

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.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

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.


AmaIT
· 1
AmaIT
helpful
0
not helpful

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.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

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.

We have round about 3500 Calls in our Gemini System, an thera are Calls an Comments marked as privat in 2.2.7. After testupgrade to 3.1.1 the calls have no visibility mark, so i have to change this manualy to the corresponding group. And therefore i need a tool to do this in a safe way. We pay for support and i think that is a support theme.

I cannot believe that we are the only ones with this problem.


AmaIT
· 1
AmaIT
helpful
0
not helpful

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)


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

thanks for this answer. we will test it asap.


AmaIT
· 1
AmaIT