Is having a distinct security level per JIRA issue problematic?

I need a highly granular security scheme for a JIRA project, where each issue has its own distinct, group of users permitted to access it. I intend to implement this by defining a separate issue security level for each new issue when it is created. The issues and their associated security levels are created programmatically.

  1. Is this a viable approach?
  2. Should I anticipate issues with JIRA functionality or performance as a result of having a large number of security levels active for this project?
  3. Can this approach affect the performance or stability of other projects in the JIRA instance?
  4. Other than the very long list of security levels that will be present in the security level selection menu, are there other usability issues with this approach?
  5. Can you suggest a different approach to achieve my requirement?

2 answers

1 vote

Quite simply, no, this won't scale.  You'll rapidly run into problems with performance, globally, and the administration screens for the levels will quickly grow to a point where they can't be rendered.  If your issues in this project are rarely created and used, you'll be ok, but I'd say you'll start to notice problems when you reach a couple of hundred.

I'd define a single scheme which names a group-picker as the visibility and then set that picker (you'll still have way too many groups, but that won't cause you anywhere near as many problems)

There is one way around it. If you base you permission schemes on something like watchers this kind of allows you to simply allow someone to browse, comment, work on issues on a pretty individual base per ticket. It does however force you to keep the watchers field up to date with whoever needs to be on the ticket. It makes sense that you limit the "Manage watchers" permission, as this could grant people to involve others.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

214 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you