How to make certain JIRA issues only visible by a group of people? [closed]

Question

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

Want to improve this question? Update the question so it's on-topic for Stack Overflow.

Closed 2 years ago.

Improve this question

My company is trying JIRA and we were wondering if there is a way to make issues visible only by a certain group of people. For example if the issue was open in Germany it should only be visible by German users, if it was open in Japan only by Japanese users. The only exceptions are admin and devs that would be able to see globally. In redmine this is fairly easy achieved with the sub-project feature, but how to do the same with JIRA?

PS: I would like it to be automatic and not based on a field the user has to chose.

Answer 1

I believe it is not possible without a third-party plugin (or a custom plugin built for your JIRA).

JIRA has "issue security" concept that allows you to control who can see the issue. You can make an issue to be visible (by default) only to the Reporter and your staff. But you can't make it visible (automatically) to some group of users associated with the Reporter.

The shortest implementation path, from my point of view, would be to

1. Create a custom field of type "Group", call it "Visibility Group".
2. Create issue security scheme that by default would make the issue visible to your staff and to the members of the group selected in the "Visibility Group" field.
3. Create a custom plugin (or have an Atlassian Expert do that for you) that will set the default value of the Visibility Group field to some value based on the Reporter -- this can be added to the workflow as a post-function of the "Create" step.

There might be a plugin out there already for that, but quick search does not suggest anything.

Hope this helps! Igor

Answer 2

To restrict issue visibility in JIRA, you will have to define an issue security schema first. Atlassian offers a tutorial on that.

You will still have to assign your users to groups (more advisable) or roles first to be able to take advantage of the restrictions.

Answer 3

Usually we define the levels in the issue security scheme and then use something like the Script Runner plugin to create a post function that sets the issue security at creation.