I'm trying to limit issue visibility to a certain group by issue type. I think I found a workaround to doing this with a script, which involves using the 'Set issue security level based on user's project role' post-function The problem is that this post-function isn't working.
What I'm doing is creating 2 groups (Group A and Group B) and assigning each group to a different project role (Role A and Role B). I've created an issue security scheme with two levels (Level A and Level B, with Level B as the default). Level A is only visible to Group A, and Level B is visible to both Group A and Group B. I then created a workflow and added the post-function in the creation transition. The post-function changes the security level to Level A if the current user is in Role A. Then I made a workflow scheme that assigns all issue types except Story to the workflow and all Stories to a default workflow. The goal is that all issue types other than Story are raised to Level A when I create them (I'm in Group A), so that only Group A can see them. But, as mentioned, the post-function doesn't work. Adding other post-functions to the creation transition work fine though. Just this post-function doesn't work.
Has anyone else had problems with this post-function? Or do you have any other suggestions for me?
I'm using the Cloud version of Jira.
Thanks for any help.
Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events