RankPulse for Jira

Backlog prioritization scores for Jira: RICE, WSJF, ICE and Value/Effort on every issue, a ranked project view, JQL search by score and a dashboard gadget. By PuzariCloud.

Where to find it

The frameworks

FrameworkInputsScore
RICEReach (a number, e.g. people per quarter), Impact (Minimal 0.25× … Massive 3×), Confidence (50/80/100%), Effort (e.g. person-months, more than 0)Reach × Impact × Confidence ÷ Effort
WSJFBusiness value, Time criticality, Risk reduction / opportunity, Job size, on a modified Fibonacci scale (1, 2, 3, 5, 8, 13, 20) or 1–10(Business value + Time criticality + Risk reduction) ÷ Job size; weights are adjustable
ICEImpact, Confidence, Ease, each 1–10Impact × Confidence × Ease (1–1000), or their average (1–10)
Value/EffortValue and Effort, each 1–10Value ÷ Effort

Scores are rounded to two decimals. A score appears only when every input is set; the panel says which inputs are missing or invalid (for example an Effort of 0).

Scoring an issue

Open Priority score, choose a framework tab (the project's framework is marked ★), set the inputs and choose Save. The score and the calculation update as you type. You can fill in more than one framework; the project's framework is the one used for ranking and for rankpulseScore. Clear removes one framework's inputs. Changing scores needs the Jira Edit issues permission; everyone who can see the issue can see its score.

Searching with JQL

Scores are saved on the issue (issue property rankpulse) and indexed by Jira, so you can use them in filters, boards and automation:

Jira indexes a score when it is saved. If you change the project framework or scales, the Prioritization page offers Update stored scores so JQL matches the new settings.

The Prioritization page

Project settings

Project admins can set the project framework, edit the RICE Impact and Confidence levels (labels and weights, 2–10 levels), the units for Reach and Effort, the WSJF scale and weights, and how ICE is combined. Inputs already saved on issues are kept; scores are recalculated from them.

Moving from Backlog Prioritization for Jira (Free)

The free Connect app no longer receives updates. Its scores are kept in its own storage, which RankPulse can't read. To switch: install RankPulse, choose the same framework and Impact scale in Project settings → RankPulse, then on Prioritization use Score missing for common values and adjust individual rows inline. From then on scores live on the issues themselves, are searchable with JQL and stay in Jira whatever apps you use.

Security and data

RankPulse runs on Atlassian Forge ("Runs on Atlassian"). It works in your browser with your own Jira permissions, makes no calls outside Atlassian and keeps its data in Jira: scores in issue properties, settings in a project property. See the privacy policy.

Support

Email support@puzaricloud.in. We reply within two business days.