How to restrict specific users from seeing specific issue types when they are in specific statuses

[Michael]

Hello,

We are trying to prevent specific users who have access to a specific issue type from seeing said issue type if it is in "x" status. For Example:

Issue type A:

Submitted >> In Progress >> In QA >> Complete

We want User A to be able to see/access Issue Type A when it is in "Submitted", "In Progress", & "Complete" but not when it is "In QA". 

We'd like Issue Type A to become "invisible" / inaccessible when it is within that specific status for User A.

Does anyone know of any way we can complete this?

Thanks,

Mike

[Garrett McCreery · Accepted solution]

Hi Michael!

You should be able to use issue security with some automation rules.

You could turn on the issue security when in the "In QA" status and turn it off when on the other statutes. Add the QA users to the issue security rule when it's turned on so they can see it.

[Michael]

Hi Garrett,

Would you be able to explain this a little more? I've read the info within the link attached by Craig below - but I'm still a bit confused.

I've created an issue level security scheme, and added the needed users to it; but I can't figure out how to attach it to the specific status within our workflow.

Thanks,

Mike

[Garrett McCreery]

This would need to be done in Jira Automation, not in the Jira Workflow. Have you used Jira Automation?

https://www.atlassian.com/software/jira/features/automation

You would need two automation rules: (use "When Issue transitions"):

1. When issue transitions from (leave blank) to "In QA"
   1. Edit Issue -> Security Level field
2. When issue transitions from "In QA" to (leave blank)
   1. Edit Issue -> Security Level field

[Craig Nodwell]

Hi @Michael 
As a post function on the transition in the workflow.
Have a look at this page.
Jira Server configure-advanced-issue-workflows -- Post-functions 

[Nic Brough -Adaptavist-]

You can do it in the workflow, and it's arguably a better place to do it because the post-functions you would need run when your users are changing the status of issues.

Also, that automation fires too often, you don't need it to run on edit, you need it done on transition.

[Michael]

thanks everyone!

[Garrett McCreery]

@Nic Brough -Adaptavist- and @Craig Nodwell It's also fine to do it on the workflow, but make sure that you are not sharing the workflow on any other projects. :)

[Craig Nodwell]

Correct, but wasn't sure if he's got automation. 
He's tagged this with a label as server, the automation solution on server requires a plugin.
I was going on those details.

[Garrett McCreery]

Good Catch. I am on cloud and it comes with it, and I love the automation!

[Craig Nodwell]

I like it too :) and it's just one of the many current and planned features selling this old server (since jira 3) guy.

[Craig Nodwell]

Hi @Michael as per @Garrett McCreery issue level security will satisfy this.

Jira Server configuring-issue-level-security