In Agile board, dragging to column with multiple statuses, how to control status order?

Robert Nickel June 2, 2017

We have a JIRA Agile board in which the final column represents two statuses: "confirmed" or "closed". Mostly, when people drag an issue to this column, they want to transition to "confirmed". However, "closed" is at the top, and so if people are not being careful, they often transition to the wrong status. It would be so much easier to use if we could just put the "confirmed" status at the top. (See wrongorder.png)

The same issue is seen in the dialog for a parent issue, after clicking the "Move to Confirmed/Closed" button: "Close" is the first choice and is the default. (see wrongorderparent.png)

I found this article (https://community.atlassian.com/t5/JIRA-Software-questions/Agile-Board-Order-the-statuses-on-a-coulmn-with-multiple/qaq-p/406701), but it is from 2014 and the advice given did not resolve our issue:

  1. Within the workflow, the transitions are already in the order we'd like them (see transitionorder.png)
  2. Within the Ops bar, same-- we control the order with opsbar-sequence. (see opsbarorder.png)
  3. The statuses are also in the order we'd like (see statusorder.png)
  4. In agile board configuration, the statuses are in the correct order (see boardorder.png)

We have JIRA v7.3. Any help much appreciated.

----------

wrongorder.png

----------

wrongorderparent.png

----------

transitionorder.png

----------

opsbarorder.png

----------

statusorder.png

---------

boardorder.png

2 answers

0 votes
Austin Sasko January 18, 2019

This is a bug in JIRA currently documented in https://jira.atlassian.com/browse/JSWCLOUD-16086

0 votes
Randy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 16, 2017

This doesn't really answer your question directly but have you considering restricting the users who have access to the Close transition using a transition condition in the workflow?

That might limit the accidents from happening.

Suggest an answer

Log in or Sign up to answer