I have set my project/agile board up to use the "Agile Simplified Workflow" and have added several columns (and status') and removed a few of the default status'.
I have created a Dashboard which a 2 Dimensional Filter widget, with Status on the x-axis (and Type on the Y). The column order presents the default Status' first, then the new ones (in a random order) - but that does not reflect the new workflow and makes it hard to read.
Is there any way I can force my project-specific status' to be ordered as desired?
*Current Order*
||Open||Closed||In Development||Ready for Sys||For Gatekeeping||For Dev Commissioning||Dev + Test Complete||For SYS Testing||
|Default|Default|Default|New|New|New|New|New|
*Desired Order*
||Open||In Development||For Gatekeeping||For Dev Commissioning||Ready for Sys||For SYS Testing||Dev + Test Complete||Closed||
|Default|Default|New|New|New|New|New|Default|
Hi Steve,
It's ordered on status id, so you could try to recreate all states in their desired order.
Or you might take a look at the following page : https://confluence.atlassian.com/display/JIRA/How+to+re-order+statuses
Both seem like a lot of work for something like this.
Best regards,
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What @Steve Butler1 said worked for us.
Go to Admin > Issues > Statuses and use the arrows to establish the order you want to reorder the 2D columns.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Christian.
If you click the arrow multiple times, it will move multiple locations. That can make it a lot faster. I'm on 7.6 Server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If anyone else if looking for how to do this using Groovy / Script Runner here is my working code (just run it in the Script Console):
import com.atlassian.jira.config.StatusManager import com.atlassian.jira.component.ComponentAccessor StatusManager statusManager = ComponentAccessor.getComponentOfType(StatusManager.class) def id = '6' // ID of the status item def moves = 110 //number of moves def up = true //change the direction of the moves def i = 0 while (i < moves){ if (up) { statusManager.moveStatusUp(id) } else { statusManager.moveStatusDown(id) } i++ }
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This works for me. Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Found one solution that works for Jira Cloud across all projects:
Re-ordering the status column
Go to: Admin > Issues > Statuses > [reorder the statuses]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
JIRA 6.3.8 helps somewhat with this issue. There are arrows so you can move the order around and this affects the 2-d filter display.
However it is probably not a usable solution when the number of statuses gets very high and they are all unsorted, like from a migration from a previous bugtracker or for whatever reason they are all unsorted. If on 6.3.8 they had a way to drag a status up and down the listing that would help, but they don't – it's just arrows which are OK for tweaking the order of one or two statuses.
In this case SQL is still the solution.
Here is a SQL example of sorting an organization with 29 status or so status codes (multiple departments converging on the status table). You don't have to get fancy as the field has no uniqueness constraints, and you could probably re-run it as many times as you want if things change:
update issuestatus set sequence=1 where pname='Deferred';
update issuestatus set sequence=2 where pname='Open';
update issuestatus set sequence=3 where pname='Reopened';
update issuestatus set sequence=4 where pname='To Do';
update issuestatus set sequence=5 where pname='Gathering Requirements';
update issuestatus set sequence=6 where pname='Research and gather requirements';
update issuestatus set sequence=7 where pname='Feedback';
update issuestatus set sequence=8 where pname='Assigned';
update issuestatus set sequence=9 where pname='In Progress';
update issuestatus set sequence=10 where pname='In Development';
update issuestatus set sequence=11 where pname='Waiting for Code Review';
update issuestatus set sequence=12 where pname='In Code Review';
update issuestatus set sequence=13 where pname='Remigrate to Testing';
update issuestatus set sequence=14 where pname='Pending User Approval to Test';
update issuestatus set sequence=15 where pname='User Approval to Test';
update issuestatus set sequence=16 where pname='IT Manager Approval to Test';
update issuestatus set sequence=17 where pname='In Test';
update issuestatus set sequence=18 where pname='Waiting for QA';
update issuestatus set sequence=19 where pname='In QA Review';
update issuestatus set sequence=20 where pname='Pending User Approval to Production';
update issuestatus set sequence=21 where pname='User Approval to Production';
update issuestatus set sequence=22 where pname='IT Manager Approval To Production';
update issuestatus set sequence=23 where pname='Acknowledged';
update issuestatus set sequence=24 where pname='Confirmed';
update issuestatus set sequence=25 where pname='Documentation';
update issuestatus set sequence=26 where pname='Resolved';
update issuestatus set sequence=27 where pname='Closed';
update issuestatus set sequence=29 where pname='Done';
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Steve.
Your post is from 2013 but the issue never gets old. heh
I just shared an article on reordering statuses using JMeter.
https://community.atlassian.com/t5/Agile-articles/Reordering-Jira-Statuses/ba-p/938473
Cheers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply. The new column ordering functionality might just do the trick - I will try and get a look at 6.3.8 - thanks for the heads up (and for the SQL, which might be a good alternative).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.