We have a big implementation project that will span across the organization.
We are planning to have an Epic for each Team.
We would like to set security levels so that each team only sees their Epic while the implementation team can see all the Epics.
Team1 Epic <- Team1 Group can see only Tickets in their Epic
Team2 Epic <- Team2 Group can see only Tickets in their Epic
Team3 Epic <- Team3 Group can see only Tickets in their Epic
All Epics and Tickets <-Project Group can see all Tickets
Reading the documentation on Security Levels it is not clear how the setup to connect the Epic to the Security Levels would be configured.
All guidance and suggestions appreciated.
Hi @Rich Wolverton,
For your requirement you can construct a security scheme like below
Security Level -- Group(s)
Team1 Team1, Project Group
Team2 Team2, project Group
Team3 Team3, project group
Using Scriptrunner you can apply/set security level based on Epic as a condiition
1. if you associate epic link during issue creation. you can use "Set Issue Security Level" which is one of the scriptrunner's post function
post-function --> Scriptrunner post-function --> Set Issue Security Level
this is simple but have to add more functions as many as your security levels are
2. You can also use custom script post-function to validate epic and set security level
3. If you associate epic link at anytime(in edit form after creation). then you can think about script listener to set security level
There will be some other add-ons also available if you search in marketplace
Thanks Leo. That is just what we have done. I was looking to see if there was a way to make it a little more Project centric. Allow the Project Manager to create an EPIC of format TEAM1 Something something.... and that work the Issue Security Scheme. Right now a JIRA Admin has to do work to create groups and add security levels as a new Team is added.
In that case I would suggest to use Project Roles instead of Groups in Security scheme
which is generic to all projects. and each project admins can decide each team's members without reaching to jira admins every time
But of course, they'll have to help you out in the initial setup of project roles and in security scheme
Roles are --> Team1/Alpha , Team2/Beta...
Security Level -- Role
hope this would meet your requirement
Hello everyone! We are very excited to announce some much needed changes to the issue create experience in JSM (the blue "create" button) at the top of the screen. We have just starte...
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