Setting up issue Security

Kathleen Jacobs

I have a project where I have a 3rd party company that is going to be added. We only want them to see Issue Types of Bugs. They shouldn'tbe able to see anything else. But besides this 3rd party group, everyone else in the project can also see Issue Type Bugs as well.

My understanding with Security Issue is I would but the 3rd party group into a security level.

And in the workflow for this issue type, add that if they are within a project Role I created for them, to auto set the security to them.

Am i missing anything? Would this do what I want? Will this affect any other issue types or existing tickets?

Paul Greig

Hi Ninjairose,

The process for implementing issue security requires the following:

• Create an issue security scheme.
• Create an issue security level named 'Private' for this scheme.
• Add appropriate people to the 'Private' security level.
• Associate the issue security scheme with the relevant projects.
• Set the security level of specific issues to 'Private'

This would then be applied to all issue types in your project, except for issue type bugs, which you would want ot retain as public.

This process will only effect existing issues where a security level was applied. In that case it will prompt you to select a new security level to replace each previous level.

If you need additional guides the following two will also cover all of the above items:

https://confluence.atlassian.com/display/JIRA/Configuring+Issue-level+Security

https://confluence.atlassian.com/display/AOD/Setting+Security+on+an+Issue

Cheers,

Paul