Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
I want to limit a reporter from transitioning his/her own issue from Open to the next Status. This transition indicates that the issue is approved and can be moved on in the workflow process from the Open status, which is why I don't want the reporter to be able to approve his/her own issue request. I tried the Separation of Duties condition, but since "Create Issue" is not considering a transition, this doesn't work. Suggestions?
Thanks! I see that add-on. I would hate to pay for this add-on just for this small piece of functionality. I did find a convoluted workaround though. I added a custom field called "Reporter 2" and added a post-function to assign the Reporter to Reporter 2 on the Create Issue transition. Then on the transition from Open, I added the condition 'User Is In Custom field' from the JIRA Suite Utilities add-on. I set this condition to "Current user must not match the field Reporter 2". It works but its not the prettiest configuration.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs