Issue security

Vita Zinets March 20, 2012

I want to control who can and cannot view different types issues in a single project. Issue security assigns to theproject and doesn't assign to the type issue. How can I control who can and cannot view different types issues in a single project.

2 answers

0 votes
Vita Zinets March 20, 2012

Thank you :)

Andrzej Pasterczyk
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 20, 2012

no problem, hope it helps.

And just a tip (in case you're not familiar with Atlassian Answers yet) - if that answers your question it's best to mark the answer as accepted - kind of let's others know that it's "resolved" :)

0 votes
Andrzej Pasterczyk
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 20, 2012

Hmmm... i guess you could set up issue security ( http://confluence.atlassian.com/display/JIRA/Configuring+Issue+Level+Security ) and create project roles or groups for particular types of issues e.g. "bug-viewers", "story-viewers".

Quite some administration overhead as then you need to assign users to proper roles/groups but I think it would serve the purpose.

Andrzej Pasterczyk
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 20, 2012

One more solution is create different issue security levels per issue type and then make them come up as default ones... more details here http://blogs.onresolve.com/?p=74 - I don't think that's the best choice but it's up to you :)

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 20, 2012

If you're willing to find/write plugins, some people set security levels in their create-issue post-functions. As you can have different workflows by issue type, you can do things like "set security to level 4 if it's a bug, and level 2 for an improvement"

If you do it like this, I'd like to gently nudge you to look at how it functions. If you set security levels for people, it's possible for users to create or edit issues so that the person reporting/editing then cannot see, so it's worth thinking that through carefully.

Also, the "current reporter browse permission" is not directly relevant here, but I find it very handy for some cases and you might too (It's disabled by default because you really need to read the docs before using it) - http://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events