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.




Disable fields for certain users (groups) when creating an issue?

web-app

I created global group (it names Reliance Customers). I created a scheme (it names Reliance Public Issue Tracker) and in this scheme Reliance Customers can only:

View Project
Create Issue
Edit Own Issue
Create Comment
Edit Own Comment

I created an user for testing (his user name is reliancecustomer) and he is part of theses groups:

EveryOne
EveryOne (Authenticated)
Reliance Customers

When this user is creating an issue he can more than is allowed in scheme: He can assign resources, change visibility, edit workflow, ...

Please tell me what's wrong? Thank you!
stepand76
· 504 		stepand76
Tuesday, December 16, 2008, 9:54:17 AM
Replies (8)
helpful
0
not helpful

We can not seem to replicate this. We have created the same setup and all seems fine.

Please double check the permissions for the group and user.
Mark Wing
· 9108 		Mark Wing
Tuesday, December 16, 2008, 10:53:10 AM
helpful
0
not helpful

Ok, thanks. We have managed to recreate it.

We are investigating this and come back ASAP.

To work around this issue for the time being you can set the visibility schemes for these fields to not included the user group in question.
Mark Wing
· 9108 		Mark Wing
Tuesday, December 16, 2008, 12:49:53 PM
helpful
0
not helpful

[quote user="MarkWing"]

To work around this issue for the time being you can set the visibility schemes for these fields to not included the user group in question.

[/quote]

I already tried it, but it seems to Field Visibility Schemes is good for list of issues only, not for creating issues. Am I right?

Another hint: Look on Gemini3.png. There are "Create Project" and "Add new project to Gemini" labels, but I just clicked on "Edit" link in the list of projects.
stepand76
· 504 		stepand76
Tuesday, December 16, 2008, 12:56:27 PM
helpful
0
not helpful

The field visibility schemes are for create, edit, view and issues grid.

Create, edit and view schemes are configured per issue type! so you have to go to the issues types screen and assign it there.

As for the labels, this is fixed for 3.1, it is just the labels that are wrong.
Mark Wing
· 9108 		Mark Wing
Tuesday, December 16, 2008, 12:58:32 PM
helpful
0
not helpful

[quote user="MarkWing"]

The field visibility schemes are for create, edit, view and issues grid.

Create, edit and view schemes are configured per issue type! so you have to go to the issues types screen and assign it there.

[/quote]

I see, that's great. Thank you!

But in Gemini management Guid is: "Optionally, each project can be assigned a default project field visibility scheme that determines which issue attributes can be seen when viewing project issues list. This provides further visibility control because field visibility schemes associated with issue types do not apply to the issues list."

[quote user="MarkWing"]

As for the labels, this is fixed for 3.1, it is just the labels that are wrong.

[/quote]

I understand. But I'm not sure if our license is enough for 3.1 :-(
stepand76
· 504 		stepand76
Tuesday, December 16, 2008, 1:17:12 PM
helpful
0
not helpful

Yes, this is the issues list visiblity sheme and you have 3 more for each of the types.
Mark Wing
· 9108 		Mark Wing
Tuesday, December 16, 2008, 1:28:34 PM
helpful
0
not helpful

Mark, I have temporarly solve it by Field Visibility Schemes. Thank you very much for your idea.
stepand76
· 504 		stepand76
Tuesday, December 16, 2008, 1:53:15 PM