I am working on creating a custom workflow in Jira. Our first state is ASSESSMENT and that transfers to the ASSIGNED state. There are a few things that have to be done during the ASSESSMENT state before we should transfer to the ASSIGNED state, one of which is assigning the issue to someone. Is it possible to prevent someone from transitioning to the ASSIGNED state unless there is someone assigned to the issue? If so, how is that done?
I think we could possibly make that work, but I think it would have to be a little more complicated. We were hoping to have the Project Manager transition the issues even though they weren't the ones assigned the issue, so we would have to grant them permissions too and hope they don't mess up. It looks like there is a way to possibly do this using the transition properties that would be a little more convenient for us, but I'm struggling to figure out how those work and if they even do what I think they do.
But if we give our Project Managers permissions to change states, they will be able to do it when it is unassigned. Our hope is that the PM is able to manage the Jira transitions even though it is assigned to the engineer working on the issue. We were trying to prevent the PM from changing the state until the engineer was assigned.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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