Order JQL Result by status order

[VINCENT DUPONT]

Hello

Is there a way to make JQL "ORDER BY status" really order the items in a desired sequence?

Depending on the workflow, sometimes I want to order (for example) Backlog, Open, In Progress, In Review; and sometimes I want to see the order as Backlog, Open, In Review, In Progress

By default, it seems that the 'order by status" uses the rank of statuses from the complete list of statuses in the admin pages. However we have here around 60 statuses used in many workflows by many people, and I cannot specify a complete ordering.

I have seen people using "opsbar-sequence" as a property on the workflow transition. But this seems not to work on JQL queries (for example in a filter)

Any other idea?

This seems to me a trivial need. Why not just sequence numbers in every workflow?
Thank you
Vincent

[Meurice Frank]

I have a similair ask 
Is it possible to change the "order by status" from ASC to [Done, Rejected, On hold, In progress, Committed, Analyse, backlog] ?

As you see, not alfabetical. Would be great to have this filter by array kind of functionality instead of as suggested to make a custom field "RANK" which needs to be created and applied.

[Aron Gombas _Midori_]

It would be rather unfriendly, but in theory, if you renamed your statuses to "1 - Done", "2 - Rejected", "3 - On hold", etc. (or used another set of alphabetically ordered prefixes), it would work.

I don't know about other workarounds. Not even with apps, because although apps can provide additional JQL functions, they cannot provide additional ORDER BY clause extensions...

[Aron Gombas _Midori_]

Workaround idea:

1. You add a number type custom field "Status Rank"
2. You implement an automation rule which initializes / updates the "Status Rank" field based on the "Status" field (it is effectively a lookup like "Backlog" -> "1", "Open" -> "2", and so on)

Then in JQL:

project = FOO order by "Status Rank"

[Marc -Devoteam-]

Hi @VINCENT DUPONT 

1st question what is the scope of your search?

If you search within certain project, there should not be 60 statuses, if there are in my opinion this is not a best practice.

opsbar sequence options are for a status in a workflow not at global level, these properties are there to determine the possible status transitions a specific order, this order could be different in another workflow, so this is why.

I don't see the trivial need, you have.

My question would be where is the governance in the instance, are the 60 status there are they needed, are there statuses that mean the same, then use a single status.