Hi everyone,
I have ran into the following behavior and I am not sure as to what could be causing it.
In one of our project boards the issues within a specific column are ranked based on the numeric value entered in the custom field "Calculated priority".
However, this only happens in one of the columns, the rest are unaffected and the issues are not ranked by that order.
The board filter itself is set to sort the Epics descending based on their Key.
"project = XY AND issuetype = Epic ORDER BY cf[10166] DESC"
The board sub-filter also does not show anything that would cause this behavior:
"fixVersion in unreleasedVersions() OR fixVersion is EMPTY"
Does anyone know what would cause this to happen? I have also not found anything in the workflow itself for the affected column.
Help or any hints are highly appreciated as I am a bit lost what would cause this. It is quiet useful and I would like to have a similar functionality for another column on the project board.
Thanks in advance!
In the board filter, the JQL contains "ORDER BY cf[10166] DESC," which means that issues are ordered by the custom field (cf[]) with the ID of 10166. In your case, I assume this corresponds to "Calculated priority."
That's why you are seeing the cards ordered by that custom field.
Hi @Sarp Egemen
thank you! At closer inspection of the filter that seems to be the case.
I will mark your answer as accepted. Maybe just a follow-up question:
The rank of the board is determined by the numeric value entered in the calculated priority. However issues without a value in that field appear on top of the column. Would there be a way to move those, with no calculated priority value, to the bottom of the column (below all issues with a value entered into the field).
Also is there a possibility to only sort a specific column by the order in which the entire board is currently filtered by?
Thanks a ton!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you try using ASC at the end instead of DESC to change the ordering from descending to ascending? That might work.
If that doesn't do the trick, create an automation to set the calculated priority to the lowest when an issue is created with no calculated priority, so that it goes to the bottom.
Regarding sorting only a specific column, I will polish up my workflow and JQL knowledge, and then I will update you about it. Perhaps someone else could help with that as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sarp Egemen ,
thanks again for your feedback and don't worry about the last question, that would only be a novelty functionality, nothing essential!
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.