Hi,
I am looking for a way to automate the prioritisation of our Jira backlog WITHOUT using Foxly.
I have been playing around with the automation rules and custom fields but have not found a way to make it work.
Any suggestions?
Hi @Jeanne-Mari Benn -- Welcome to the Atlassian Community!
What would automated prioritization look like to you? How would it work relative to any manual prioritization?
The default sort for a backlog / board filter is ORDER BY Rank ASC. When that is used, the manual drag-and-drop to change rank / order words. Any other ordering prevents that.
It is possible to update the Rank of an issue, relative to another issue, using the REST API functions and the automation action of Send Web Request. Although that may not help if you mean order-changing based on something other than ranking.
Kind regards,Bill
Hi Bill,
Thank you for your response.
We want to try move away from manual prioritisation, if possible. For example, dragging the highest priority stories to the top of the backlog.
I was hoping to use the "Priority" field and a custom field for "Priority rating" in an automation rule to organise our backlog from high to low priority. But so far that plan is not working very well. I cannot find the automation rule components to build a rule like that.
The ORDER BY for the board filter could be changed to sort as you wish. For example,
project = myProjectName ORDER BY yourCustomField ASC
Then any changes to the field(s) would be reflected in the order of display.
What would you expect the automation rule to do? Is it calculating the value of your "Priority Rating" field?
In that case, if you can define the algorithm to set the field, based on other issue data, that may be possible.
I guess I could just sort on the custom field. If we rated the priority of the Jira issue from 1-10. (10 being highest priority), then hopefully the ORDER BY could sort it from highest to lowest priority and vice versa. It will be more granular than sort with the Priority field that will have 40 tickets all with a priority of high.
We came up with a solution at our site that worked quite well with custom fields, Automation and Smart Values. You can change the automation trigger to your liking, but a Score is set to the ticket according to different initial inputs and it's triggered manually.The example below is grabbing the value of three custom fields and calculating the average, pretty simple, but you can customize however you like with smart values. I even tested the response in different types of custom fields to make sure it workedThe fields in this example are a Single Select List going from 1 to 5.{{#=}} ({{issue.customField_16702.value}} + {{issue.customField_16703.value}} + {{issue.customField_14700}}) / 3 {{/}}https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/
Hey Jeanne-Mari, coming back to your original goal of moving away from manual prioritisation. If you want to keep it native, the working pattern is: number fields for your criteria, an automation rule that computes a weighted score into a 'Priority rating' number field using the {{#=}} ... {{/}} math smart value, then sort with a board filter like ORDER BY "Priority rating" DESC (as Bill showed). The catch is the ORDER BY approach replaces Rank, so you lose drag-and-drop, and the rule chain gets fiddly to maintain as criteria change.
If you'd rather not hand-roll that, full disclosure, I work on Product Management Priority Scoring at ChefStackz. It does RICE, WSJF, ICE and MoSCoW scoring right on the issue and writes the result to a normal number field, so it plugs into exactly that ORDER BY sort and any automation you already have: https://marketplace.atlassian.com/apps/3064060819/product-management-priority-scoring-for-jira
Hope that helps.
Alex
It looks like you're new here. Sign in or register to get started.
