Status sequence is wrong when drag and drop issue on active sprint board

Jeffrey Holdeman October 30, 2017

We have an active sprint board with five columns.  The columns are configured with several statuses (on the low side one column has ony one status, on the high side one column has eight statuses, other columns have two or three statuses).  We have ordered the statuses vertically in a column in a specific sequence following our workflow.  When we use the active sprint board and drag and drop an issue from one column to the next, the board temporarily is shown with a blue background and the possible status codes become visible in each column.  (The process I am describing is explained here.)

However when dragging the issue, the status codes are not vertically ordered in the same wasy as they are configured in the column of the board.  This is difficult especially when working with the column that has eight statuses.  How can we get the status codes available when dragging and dropping an issue to follow the order of the status codes configured in the column?

Thanks,

Jeff Holdeman 

1 answer

0 votes
Peter DeWitt
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 30, 2017

@Jeffrey Holdeman, the order the statuses appear in the actual board when dragging issues is related to the order of the workflow transitions. The statuses will appear in the same order as their respective transition do on the actual issue.  Try setting the opsbar-sequence property for the transitions.  This will allow you to specify the transition order and thus the status order.

 

https://confluence.atlassian.com/adminjiraserver071/workflow-properties-802592825.html

.pd

Jeffrey Holdeman October 31, 2017

Hi Peter,  thanks for that idea, unfortunately that does not solve the sorting issue during drag and drop.  We already had setup the opsbar-sequence property in the transitions so that the statuses were sequenced in the correct order in the issue detail. 

Suggest an answer

Log in or Sign up to answer