RELATED IDEAS
Allow sorting by Initiative Prioritization Rank
What is the challenge? |
When I sort my strategy roadmap by rank, it is not the rank I assigned in prioritization, it is a hidden field in the details view which is actually the order of tickets |
|---|---|
What is the impact? |
By using the term "Rank" in prioritization, and then allowing sorting by "rank" in other views, but it isn't actually the rank you assigned, it is very confusing. If you want to sort by the rank you actually assigned, you need to reorder again in the details view. |
Describe your idea |
"Sort by rank", should be the rank in prioritization. Do not use multiple ranks. If there is a need to allow sorting based on the order of cards in the details view, then call it "Details Order" for example, not rank (since rank is used in Prioritization) |
© 2025 Aha! Labs Inc.•All rights reserved
Hi there,
Adding additional context on why this enhancement is needed:
The current “Rank” field creates confusion because it cannot be used in any meaningful way outside of this single screen. If the Rank value can’t be referenced in reporting, sorted against, or used as a data point, it raises the question of what purpose it actually serves. Our use case requires Rank to function as an actual prioritization value—something we can pull into dashboards, use in scorecards, and sort by consistently across views.
Right now, the Rank shown in the strategy/roadmap view is not the same Rank assigned during prioritization, which makes the field unusable for decision‑making. If Rank is not intended to function as a true prioritization field, then its value and intended purpose need to be clarified. But ideally, the Rank that is set during prioritization should be the same Rank available in reporting and sortable in all relevant views.
In short:
If Rank can’t be used outside this screen, what is its function?
Making Rank a consistent, reportable, sortable data point would solve this and support its intended use in prioritization and scorecarding.