Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Permissions - Restricting user groups browsing based on issue status has stopped working...

Jonathan Hood
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 26, 2018

Hi,

Would appreciate any help anyone can offer - I setup a project a year+ ago where we needed to restrict view/browse access to issues based on their status in the workflow (i.e. one usergroup cannot see issues before they have been approved past a certain stage).

After some investigation, it looked like this could be done by adding permissions to each workflow step property, i.e.

  • property key=jira.permission.browse.group      property value=my group

(https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status)

And we tested this at the time - when logged in as users from the other restricted group, they were unable to view the issues which were in the restricted workflow steps... yey.

But I've become aware that those users are now able to view the details of those issues.  I've no idea what could have changed since setup to affect this - but effectively it looks like this command doesn't work any more?  I've also tried:

  • property key=jira.permission.browse=denied    property value=restricted group

But this doesn't appear to work either...

Need to find a solution pretty quickly... any thoughts on where I've gone wrong?

Thanks!
Jon  

1 answer

0 votes
Mirek
Community Champion
April 26, 2018

Not sure what happen. Maybe a JIRA upgrade happen since you configured it. In order to do it more effectively you can configure a Security Level and Issue Security Scheme which will be much better to manage visibility on a specific issue. Then on specific status you just change the level of security and issue would not be visible.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events