I've created a very simple workflow for one of our project teams:
They use the agile boards, so we have a board configured with statuses mapped like this:
I've run into something strange, and I'm not sure if it's a setup issue or a bug; we're pretty new to using the boards. If I have an issue with a status of Backlog, it shows up in the To Do column of the board. The strange thing is, I can't drag it to the In Progress column, but I can drag it to Code Review or Done, completely bypassing In Progress (the workflow itself does not allow this; when using the workflow on the issue itself, you must go through In Progress to get to In Code Review, and then from there to Closed.)
Where am I going wrong with this setup? I did see this response, but the workflow has no conditions or validators on any of the transitions, and I'm able to transition an issue from directly within the issue using the workflow buttons.
The workflow is hard to read, you probably should spread it out a little, but...
I can see that you have the backlog and todo status both in the 1st column, so you can not drag the backlog status to the todo status - you would have to open the full screen for an issue and use a button to advance it.
My guess is a backlog status has no direct flow to In Progress and needs to go though the to do status first. It also appears you have an additional workflow involved as the new, reopened and review statuses are not shown in the flow you attached. Depending on which workflow the issue is using, you may need to make some adjustments.
Suggestion: add another column for the new and backlog statuses and make sure you have transitions in place to go to 'To Do'
In addition to the excellent comments from @Tom Proctor I would also suggest you look at two other types of transition on your workflow.
1. Reuse a single transition from multiple statuses
2. Use the ALL transition to a single status
I would certainly also spread out your workflow diagram to make it easier to look at. Remember that your users may have permission to view a read-only version and it will help them understand the routes through the workflow too.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot