It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
I have a project, in which many functional people work on it. A field "From Functional Team" in issue screen is associated with each issue, for example, From Functional Team - BA, From Functional Team - Dev, From Functional Team - Testing, From Functional Team - QA....
I also set up a couple of user groups by functional team, such as QA group. Now I hope QA group members can only see the issues involved in QA team, can I use the field "From Functional Team - QA" as a condition to restrict people access the "QA" issues, except QA group? Thanks for your feedback.
IT's a bit of a faff, but you can do it.
You could set up an "issue security scheme" which has levels that grant access to different groups.
If you selected the right type of field for "functional team" (specifically a group picker, and you have you groups set up appropriately), then that should restrict issues by that field. Only problem is that people could create issues that then vanish from their view if they pick a group they're not in.
Thanks, Nick.
Unfortunately, the original design of screen used a select list (single choice), all of team names in the select list are not fully consistent with group names yet. Do you think your solution is available for my realistic situation? If not, what should I do to meet my goal? Change field type (select list->group picker) and remapping existing field to the changed group picker? I appreciate for your feedback.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreHey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.