I’m just playing around with the new prioritization list for Features and Epics (https://www.aha.io/support/roadmaps/strategic-roadmaps/features-and-activities/feature-prioritization-page) and I wondered: if the rank changes in that list due to sorting or drag’n’drop – does it have any influence on the ranking in the Workflow or Board views? It does not. This means, we go to the prio list to rank and then rank again in the Board view per release (because that’s the view we’d use to present the release plan to stakeholders or because the ranking there allows us to sort list reports by rank which we can use in Dashboards), and then rank again in Azure DevOps after synchronizing the records for the dev team, this is not an optimal workflow and creates lots of room for mistakes.
It is not clear to me what the value of this new prioritization feature for Epics and Feature records is if it does not influence any other place in Aha! and the rank value cannot be used for sorting in other views or exporting to external systems. It was super exciting when I read the announcement, but now it's just frustrating.
A new way to share priorities with engineering — from the prioritization view
Capture a feature's priority in a custom field and map it to the development tool of your choice. Now engineering has a quick view of the most important work.
I can do that, yet it���s a manual step. The issue specifically is we can���t pull it into the Cards we use on the Workflow board or release boards.
Not sure how to describe this?
Great this is shipped, I don���t understand what that means as I���ve not been involved in but only a few ideas. What does shipped mean and how will we use it, what���s enabled?
Yep super want this to work (and agree it should be optional). I assumed it would propagate anyway. Thought I was doing something wrong till I contacted support...
If this is implemented, it needs to be a product line or workspace level feature that can be turned on or off. Our business is complex enough that I cannot have priority ranking changes automatically affecting other areas. Jira does not allow this functionality in Jira Advanced Roadmaps and it is a big issue that led us to using Aha for PM.
Our company really needs this functionality to be expanded to other places, it's a huge constraint and it's leading us to consider alternative options (like Jira's roadmaps) to do this 1:many prioritization
The prioritisation board is a great add to Aha! It replaces pivot reports already in use with the additional benefits of drag and drop, sort by, easy access to Aha! score and cross-product/initiative prioritisation to set the rank.
Now, we'd really like to see a blog post from Aha! which explains, having used the prioritisation board... What do we do next? How do we translate the work done on the prioritisation board into meaningful, easy, automated priorities for the features/epics in our workspaces so the teams know what they need to go and get on with?
The ranking I set in Features > Prioritization should be visible elsewhere in the application, at a minimum:
In any list report (now in Roadmaps)
In an epic, when viewing the 'Related' tab
In a Release
I suspect that this prioritization is complicated by the fact that there is prioritization in Releases, which for my company, is pointless. We do not use Releases in Aha. However, for those that do, maybe there should be a setting that determines whether prioritization comes from or translates to the Releases.
If the ranking ability is made to transfer to other areas, this should be a feature that can be configured and not automatic. I wouldn't want this ability to transfer to other areas active in our situation.
Maybe then it's a button that synchronizes the ranking as a batch from the view you are in, or a default view that is synced with the rank on other views - but not synchronizing at all cannot be the final version of this feature. I don't understand how I would have multiple prioritized lists that are not the same prioritization, though - there can only be one backlog and it is prioritized globally. You can filter that backlog by customer or initiative or status or release or... but the relative ranking of the remaining records needs to stay. Otherwise, you are communicating confusing priorities to different stakeholders.
I agree that it's frustrating and the new ranking doesn't make much sense because it doesn't link though with the current functionality, I wouldn't want it to sync with any other ranking. There can be multiple prioritization views created for one workspace and if you open one view up to editing by more than yourself conflicts could be unintentionally created. I was working with another resource on the same view and when I made a change she couldn't see it though she had the option to "Save Changes" on her screen, which, if she saved, would override everything I just did.