Skip to Main Content
Status Future consideration
Categories Jira
Created by Danny Archer
Created on Jan 5, 2018

Integrations 2.0: Add dependency link to connect records without natural relationships together

In integrations 1.0 if I mapped
Features = Story
Requirement = Task
Aha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other.
In 2.0, we do not do this. Additionally, we do not allow any type of "Links to" connection to be created since the two JIRA records do not have any type of normal connection with each other like an Epic and a Story or a Story and a sub-task would.
This would be handled through allowing a JIRA side "Links to" value of "Relates to".
This is different than full support of dependency mapping since we are using the dependency to create a link -- the Aha! end wouldn't necessarily have a dependency since the records are already related.
  • Attach files
  • Puneet Singhal
    Sep 13, 2018

    In our environment, it makes sense to relate Jira Epics with Aha Features, and Jira Stories to Aha Requirements.  Dependencies are a KEY aspect of why I even started to look into Aha!.

    Before I can turn Aha into the system of record, I have to be able to import the dependencies from Jira.  There is no way for me to manually recreate the 1000's of dependencies already established within Jira. 

    After I turn Aha into the system of record, and start bulding dependencies in Aha, would the dependency go into Jira?  Or would it need to be manually created again?  Looking at this idea, it seems to be another area that makes Jira integration extremely difficult.

  • Guest
    Aug 3, 2018

    The relationship of the records is imperative. I run large to small project that have inter-dependencies. I concur with Danny Archer that we need this to ensure JIRI alignment. 

  • Kevin Burges
    Mar 22, 2018

    We were using this functionality in the 1.0 integrations and were surprised to find that the dependencies are no longer created in the 2.0 integrations. We looked at migrating to a more "traditional" structure of having Features map to Epics, but due to other automated processes that run off our current JIRA configuration, this is not an option.

  • +1