Hi,
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.
Kindly,
Gilad
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.
Hiding fields would be a little harder but if you are up to it you could install the plugin jsincluder and create a javascript (or jquery) to do that and map it to the respective screens (create, edit, view, transition) of the projects you want it implemented.
Regards
Dave
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.