RELATED IDEAS
Need to "Link with existing issue in JIRA" at requirement level
We have JIRA and Aha today and the tools are integrated as follows:
- Aha feature - JIRA Epic
- Aha requirement - JIRA story
- NA - JIRA sub-task
- Aha requirement - JIRA story
For some reasons, I had to delete the integration with JIRA for a specific product line from Aha and thus, lost the link between Aha and JIRA. I could rebuild the links between Aha feature and JIRA Epics as there is a "Link with existing issue in JIRA (Via Connect)" at the Aha feature level.
However the links are lost at the Aha requirement level because I don't have the same button at the requirement level... Even worse, when I rebuilt the integration, Aha pushed the Aha requirements as new JIRA stories in JIRA, although those stories do already exist in JIRA!
I was told by the Aha support team to delete the content from Aha and reimport it from JIRA... but this is a big action that I'm not ready to perform as I'm not sure about the quality of data in JIRA...
This needs to exist in the Jira 2.0 integration as well.
any update on this - it says 'likely to implement' but that is from 2015. It would be very handy to be able to link an existing Jira ticket with an Aha requirement
This is a major need for all PMs in my team. If Aha allows you to delete the jira issue associated with the requirement, it should also allow you to associate an existing jira issue with the requirement.
Agree with Jemi. We are gradually losing our links and cannot revert. As time goes, we'll end up with no integration at all on any of our requirements...unless we blank either JIRA either Aha to get back to the initial state, losing comments, history and so on.
We created a Jira ticket then decided to track things in Aha, but couldn't find a way to link an existing Jira ticket with an Aha requirement. It works well reverse-linking a jira ticket to a feature, but not for requirement.
Hi Cy Caine,
We also thought about linking as you explain (Aha initiative - JIRA Epic and Aha feature - JIRA Story) but as you say also, we didn't want to "bastardize" the use of initiatives in Aha... This is unfortunate that you are also having troubles with this structure... :(
Having a 3rd level of categorization would be great indeed, but I'm totally convinced that whatever the categorization we want to implement, we should be able to manually link the elements between Aha and JIRA at those 3 levels. Otherwise, everytime there is a big change in JIRA, we lose the link and it sucks not be to able to manually re-link to existing Aha requirement/features... :(
A suggestion from Aha support was to delete everything and re-import, either from JIRA to Aha, or from Aha to JIRA, but this is not a right approach for us because we want to keep the Aha and JIRA IDs... because we communicate those IDs to many stakeholders and we cannot afford to change those IDs...
So we're currenlty stuck with broken links at requirement level... :(
We are having a similar but somewhat different problem. In our setup we have the following structure:
The problem with this is that we have to use the Epics feature in JIRA so we have had to bastardize the use of initiatives in Aha. And this is really frustrating because it makes it impossible for us to use the new Strategy-Roadmap features that were rolled out recently. I think we need another level of categorization in Aha so that things could be organized like this:
I will add that we are not currently using requirements in Aha because the each cause a different ticket to be created in Aha and this has proven very confusing. Maybe this is due to our setup, but we haven't figured out a way to take advantage of Aha Requirements capability.