I have a Aha to JIRA integration set up which allows me to prioritise features in Aha by a combination of Rank and Score. We frequently re-prioritise cards in Aha (therefore changing the rank) but this doesn't trigger an update in JIRA. I rarely change the Score, as I don't wanted to use this to manipulate any change in priority.
I have been trialing Aha for my company over the last year, and have recently managed to convince the company of the benefits of Aha as a product management tool and to adopt for all our product teams across the globe. However, this is my number one gripe with Aha and the lack of support for triggering updates to JIRA (which all our dev teams use) is perceived as a problem.
This was raised under support request #312749 and was told that this could 'create a lot of traffic' with regards to JIRA updates. Well, I'm creating that 'traffic' today, and the only problem its causing is that I have to remember to 'resend all fields' for all cards below the card I've re-prioritised. Not a great use experience and one that causes confusion.
Also - there is a bug where the ‘history’ on the feature isn’t updated when the ranking changes for cards that aren’t moved.
Mapping an Aha release to a JIRA release is not an option for me, as these are 4 weekly releases, and I don’t want to map Aha features into 4 week windows.
I could really do with Aha supporting the ability to resend an updated priority to JIRA whenever a card priority changed.
Thank you for the idea. Currently, you can save the priority of features from the prioritization view to a custom field — then send the rank directly to your dev tool via an integration. This will allow you to have unique ranks for each feature, while the rank determined by the placement in a release can lead you to have multiple features with the same rank. Additionally, automatically updating the order in Jira when a feature is reordered within an Aha! release could unintentionally send a large number of Jira notifications without a user knowing.
Given the capability above for syncing rank from the prioritization view, we are unlikely to implement this idea. We hope you can understand.