We set the rank order of what features should be developed next. The ranks change week to week (Agile methodology) and those changes are also set by product managers. It would be preferred if rank order was updated by Aha! then sent/updated to JIRA.
Aha! will now use the JIRA Agile API to rank issues within JIRA when they are first created. Aha! will use other issues already linked between Aha! and JIRA to determine the rank order.
The ranking in JIRA will only be performed when the issue is first created by Aha!. Changes to the rank in JIRA, or changes to the rank in Aha! will not be reflected in the other system.
This idea is shipped. If you are seeing an issue with the ranking when items are sent to JIRA please email support@aha.io with a description of the problem and our customer success team will be able to help.
Is this closed or is this still an issue? Feels a bit like it might be still open...
It's a start, but hopefully this issue can be resolved soon. This is the #1 biggest time suck in using Aha & Jira: dealing with the manual sorting of features.
It would be really nice if we could even just get something like a button in the release to "send rank to Jira" that would re-sort a given release.
The issue that this does not actually update rank into JIRA in a useful way is at https://big.ideas.aha.io/ideas/APP-I-2292
I dont' think it solves the issue. By using the Aha! Rank field in JIRA you can see the Aha rank, but it doesn't update the actual rank. The only way to do it properly is to change the JIRA board filter to use Aha! rank instead of rank, but then we cannot create sprint !!
We are now stuck. We have 2 systems:Jira and VSTS, none of them integrate nicely with Aha!
That's quite an issue
For the record, this does not solve the issue. It just turns it into a field in Jira that can't even be shown on the same screen as feature reordering (so you can't look at this field and reorder as a result). So it is no more useful than having it only in Aha.
This seems crazy to me: I'm trialling Aha and I thought I was missing something. How do you even use the product if the priorities that the PMs set aren't reflected through to the development system?
Would be very helpful for us as this is causing the product team to do duplicate work and reducing their desire to work in Aha - forcing the to spend more time in JIRA