How to assign issue security based on component

I'd like to assign an issue a security level by default, based on the component an issue is assigned to. Possible? Suggestions? Thanks so much in advance.

3 answers

1 accepted

2 votes

Unfortunately, the answers you've been given so far only work for one very specific situation - they do NOT set the security level, they set the assignee to one person and then rely on the default security scheme in the project to do things like "hide the issue from everyone except that person".

If that's what you need to do, then it'll work (with the additional caveat that you also really need to understand the rules about who the component lead is when the user selects multiple components)

To actually do "security level set by component", you need to do some coding. You need to find/write a post-function to add to the "create" transtion (or listener if you want to do it on edit actions). The code is a simple "if component X, then set security Y" block of statements. I'd look at using the script runner plugin to do it.

go to your project configuration page, edit the component and define "component lead" as tandard assignee

This way, every time a component has been selected and the assignee is set to the default "Automatic", it will be assigned to the component lead

you can configure security level for current assignee.

i hope this will help you!!

where do I configure security level for current assignee.

In the "security scheme"

thanks for quick reply Nic. i don't see where. unless mis-interpreting something, in the scheme I can just say which users can SEE issues with this level. I don;t see a way to SET the level based on security

A security scheme defines a set of levels that can be applied to an issue.  Each level is a set of rules that say who can see the issue with that level.

To set a security level on an issue, a user must

  • Have the permission to edit the issue
  • Have the permission to set issue security
  • Be covered by the rule that defines the level they are trying to set 

As prasad suggested, if you want only the assignee be Component Lead then ok.

If you also want security to view that issue by key or by means of Issue Navigator then you need to set Browse Project permission to Current Assignee. You can find here.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,334 views 14 20
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot