We receive new issues from both end-users and developers in our Jira (Cloud). When end-users create issues, I want them to go into the Triage state (from where a developer can place them into Backlog or Not to be Fixed). When a developer creates an issue, however, I want it to go straight to Backlog.
I want both end-users and developers to be able to create the same types of issues. I do not want to create separate workflows for different issue types.
I've investigated having the "Create" workflow transition go to a different starting state based on group membership, but this doesn't seem possible. I would also be OK with showing different "Create Issue" fields based on group memberships (so that a developer can choose the starting state of Backlog, but an end-user cannot), but this doesn't seem possible either.
I am not interested in Marketplace add-ons, I am looking for an out-of-the-box Jira solution.
What are possible solutions to this problem? Thank you.
The create transition in a workflow can only have one end state, you can't change that. So you'd need a different workflow and issue type for each different starting status in your system.
However, if you're happy with add-ons, there is a way to do this. Several add-ons provide "fast track transitions". These can pick up an issue as it transitions, check if it matches a rule and initiate a second transition to another status. The issue is created in the initial status, but before the user gets a refreshed screen, moves on to another one.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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