I have a use-case in which company would like to restrict project between groups, meaning:
On one hand , groupA at project A - could browse/edit only specific related issue.s
While on the other hand, groupB should be able to edit related specific issues on projectA.
Another issue was raised, could we restrict system field or custom fields?
For example, Comment fields can't be hide.
Restricting issues could be accomplished with issue security schemes and automation rules with the plugin Automation for Jira. Depending on what you want to hide for group B it could take multiple automation rules and even custom fields to provide you with users or groups that are allowed to see the issue.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events