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.




Visibility scheme weirdness

web-app

I have set up three visibility schemes in Gemini 3.5.4:

  1. Issue create
  2. Issue edit
  3. Issue view
They are set as the appropriate visibility schemes for all issue types and "Issue view" is set as the Administration | Security Settings | General | Field Visibility Scheme setting.

There's two things I'm struggling with:
  1. I have set Reported By to be visible on issue creation to Gemini Admins and Project Admins only. Also, Assigned To should be visible only to a global group I have defined called "All Internal Users" (i.e.it should be hidden from external users in all circumstances). When I go back to view/edit a visibility scheme, however, the "Everyone" global group appears as selected for both of these fields. It's actually not "really" selected, as I can hide/reveal the fields by selecting/deselecting the Everyone group and saving the scheme (well, "Assigned To" seems to be greyed out on creation, rather than hidden, but it works the same way). Each time I go back to the visibility scheme, Everyone appears selected again...
  2. The Assigned To field appears/disappears (or, as I said above is greyed out on creation) in the issue create/view and edit pages as I add/remove groups from the scheme. It stubbornly refuses to disappear from the issue list page though - even though the Issue View scheme is set as the global default.
Any ideas?
nharris
· 1 		nharris
Friday, September 18, 2009, 5:34:45 PM
Replies (6)
helpful
0
not helpful

We think this might be a bug that is fixed in 3.6, which is due out next month.

Do you have a lot of cutom fields?

Can you please try and create a new visibility scheme, select the correct visibility setup in it and click save? We believe that it should work (only when first created).
Saar Cohen
· 5000 		Saar Cohen
Friday, September 18, 2009, 9:40:42 PM
helpful
0
not helpful

No, same result, I'm afraid.

I created a new visibility scheme, made the appropriate settings and saved it (once). I then made that the Administration | Security Settings | General | Field Visibility Scheme setting and went to a project to view the issue list. "Assigned to" was still visible. When I went back to the visibility scheme, "Everyone" appeared selected against "Assigned To".

I then tried again by deleting that new scheme and creating another new one. This time I set visibility for Assigned To only (I had set groups for all fields before). Same result when I went to view the issue lists, though this time when I went back to view the visibility scheme setting, "Everyone" did not appear as selected.

Not sure what constitutes "a lot of custom fields", but we currently have 17, spread across the various projects.
nharris
· 1 		nharris
Monday, September 21, 2009, 1:06:37 PM
helpful
0
not helpful

Did you set the new visibility scheme for the project? Edit the project and set it.
Mark Wing
· 9108 		Mark Wing
Monday, September 21, 2009, 1:44:01 PM
helpful
0
not helpful

OK, that was the problem. Unfortunately, I'm now confused about the Administration | Security Settings | General | Field Visibility Scheme - if you set the issue list visibility for each individual project, what is that setting for?
nharris
· 1 		nharris
Monday, September 21, 2009, 2:11:23 PM
helpful
0
not helpful

This is used when you select more than 1 project in the projects list (filtering).
Mark Wing
· 9108 		Mark Wing
Monday, September 21, 2009, 2:12:07 PM
helpful
0
not helpful

OK I see, thanks.
nharris
· 1 		nharris
Monday, September 21, 2009, 2:31:52 PM