I have a user "pirate" which is a member of a group "Pillaging and Looting (unit head)".
My permission scheme grants browsing permissions to:
The Cc Groups field is a Multi Group Picker custom field and the Budget Unit field is a Select List custom field, with the group name copied exactly as one of the select list options.
If I add the "Pillaging and Looting (unit head)" group to the Cc Groups group picker, the "pirate" user is able to see the issue when browsing the project and can view the issue. However, if I select "Pillaging and Looting (unit head)" in the Budget Unit group, the "pirate" user is not able to see the issue when browsing the project, BUT can still see the issue if he searches for the issue key.
Why is the "Budget Unit" Select List not allowing pirate to browse the issue, but the "Cc Groups" Multi Group Picker is allowing pirate to browse?
Furthermore, there is a workflow action which has a condition: Only users in group(s) specified by custom field Budget Unit can execute this transition.
This condition DOES allow "pirate" to perform the workflow action, so the "Select List" custom field seemingly DOES work for granting group permissions based on value, and the value of the list option correctly matches the group name. So it works for workflow conditions, but not permission schemes.
It is just the difference in implementation. Permission schemes, notification schemes etc won't take group values from select lists. The custom field has to be of group picker.
Why are you using the select list instead of group picker? If you must use that, have you considered copying the value of the field to a group picker field in a workflow transition or something?
Thanks. I'll try copying the value.
I'm using group picker because I only want users to be able to select from a subset of the groups which represent budget units in our organization. I also want them to be able to just click and see a dropdown list of the options, rather than searching with the group picker.
Andrew
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jobin,
I found this: https://jira.atlassian.com/browse/JRA-12865
which seems to suggest what I'm doing should work?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, just also found this, which seems to be a regression:
https://jira.atlassian.com/browse/JRA-29196
You're right.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmm.. interesting. But seems it is not working for you? Maybe you want to check with support? Could be a bug.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, this is a regression - see https://jira.atlassian.com/browse/JRA-29196
You might want to use one of the workarounds mentioned in that issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.