Show prioritization views and dominant rank on records

What is the challenge?

• Teams use prioritization views to rank records in context, but that ranking is currently trapped inside each individual view

• When a feature, idea, epic, or initiative appears in multiple prioritization views, there is no clear way from the record itself to see which prioritization view(s) it belongs to or which rank should be treated as the primary one

• Today, prioritization rank is view-specific and separate from the record’s standard rank, so teams resort to copying rank values into custom number fields when they want that information to appear elsewhere or stay synchronized

What is the impact?

• Records lack important prioritization context at the point where people are reviewing them, making it harder to understand why an item is ranked the way it is

• Teams that maintain multiple prioritization views cannot easily identify which ranking should drive reporting, integrations, or real-time record display

• Manual workarounds with custom fields create setup overhead, increase the risk of stale or conflicting rank data, and make prioritization harder to trust across views

Describe your idea.

• Allow records to display the prioritization view or views they are associated with directly on the record card and in reporting where relevant

• When a record appears in multiple prioritization views, allow workspace admins to choose one prioritization view as the dominant source of truth for that record type’s synchronized rank

• Keep the selected dominant rank updated in real time as records move within the chosen prioritization view

• Expose that dominant rank consistently anywhere a shared rank is useful, such as record cards, standard reports, and integrations that rely on a single always-current prioritization ordering

• Preserve the existing flexibility of view-specific ranking while adding an explicit way to designate which prioritization view should power a shared, always-updated rank