Column Order of new Status' in 2D Filter

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|


5 answers

1 accepted

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

Will give that a go - cheers

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++
}

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';

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).

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.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,009 views 12 18
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot