Hi @Puneet Sachdev
If you need users to create issues - they'll need access to the project. This means they'll need to see the issues within it, which would include those within Sprints.
That isn't to say this isn't possible though - Issue Security Schemes allow you to control and can and cannot view issues. You can control who can provide security levels - along with what they do.
---------------------
You'd need to be a Jira Admin to set this up and this needs to be a Classic project - but here's a brief overview of how this might work manually:
- Go to Jira Settings > Issues > Permission Schemes
- Locate the Permission Scheme for your project and open it
- Next to the permission "Set Issue Security", ensure you limit this to the roles/groups who need to see sprint issues and manage accessibility
- Next, go to Jira Settings > Issues > Issue Security Schemes
- Create a Scheme - eg. Sprint Security - and access it
- Next, add a Security Level - eg. Team Member - then press "Add" under Actions
- Decide how you'll manage issue access. For example, you might decide only users within a specific role can see the issue, or perhaps within a specific user group? You could also use Reporter to allow users to see an issue they created - but not any others!
- To make this level the default during creation, select "Default" under Actions
^ Using this method, users would be able to see the project and create their issues - but not see any restricted issues unless you provided them access using a user type like "Reporter" or "Assignee"
---------------------
You can modify this a little - such as:
- Have multiple Security Levels - such as "Team Member" and "None", limiting levels based on user type.
- The example above pre-sets issue security at creation - but you can start with no issue security (don't set a default)
- If you have multiple roles and want users to modify the field from the issue screen, you'll need to go to Jira Settings > Issues > Screens and add the field "Security Level" (alongside access to the limited user type and the permission)
---------------------
Idea:
To think outside the box on this you could:
- Create a custom user picker field called "Viewer"
- Set an automation rule that copies the creator into the Viewer field during issue creation for specific issues (i.e those you want them to see)
- Set the security level for these issues automatically during creation (same automation rule)
- Possibly utilise a second automation rule which sets a more restricted security level for those issues you don't want to share at creation also
^ This way you could manage visibility post-creation depending on the security level without initial manual intervention! This is a bit cleaner than the manual version above!
---------------------
See more on Issue Security on this page! And Automation on this page!
Let us know if you need any further assistance!
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.