JIRA components permissions

[Tony Montana]

Hello!

We have one project. In the project has Component = CRM. How to make that person saw only issues with this component and other issues - not.

Thank you in advance

[Joe Pitt · Accepted solution]

You would have to apply a issue security scheme to the issue. If you have scripting you may be able to do it that way when the component is selected.

[Tony Montana]

A separate issue type with a restrictions cannot be?

[Nic Brough -Adaptavist-]

No, project permissions are done at that project level.  A user can either see all the issues in the project, or they see none of it.

The only lower layer is "issue security".  This lets you set a "level" on each individual issue which can restrict its visibility to a sub-set of people with project permissions.

It's done on an issue by issue basis with a single "security level" field, not by component or issue type or anything else.  This is why Joe mentions scripting - you could write a script that does things like "if component = CRM, set security level X"

[Tony Montana]

In Script Runner, or Post Function? 

[Nic Brough -Adaptavist-]

Post-function.  I mentioned script runner because it gives you the ability to write post-functions directly in JIRA, rather than having to write your own add-on to provide the post-function you need.

[Sergei Aldoukhov [Adm]]

good day,
interested in exactrly the same issue resolution:

all tasks with [Component] = "Import"

_visible_ only to [User group] = "Import_department"

if anyone could help HOW TO set this up - in coding or post function or whatever - that can actually DO IT - would kindly appreciate. (freelance coders also interest) - or any suggestions where to find the solution...

thank you in advance

[Nic Brough -Adaptavist-]

First, set up a issue security scheme that does what you need (one level for "import", with a rule "only group import_department")

Second, use the ScriptRunner built-in script (see https://scriptrunner.adaptavist.com/latest/jira/builtin-scripts.html#_set_issue_security ).  That wasn't built in until recently.

[Sergei Aldoukhov [Adm]]

thank you! will try and report.

[Andrew Zakharov]

Seems the ScriptRunner for Jira Cloud didn't have "Set issue security" built-in function. Can you suggest, please, what we can do in this case?

thank you in advance