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. ...
Danny Archer
over 7 years ago
in Dependencies / Jira
3
Future consideration
Including Dependencies in Jira integration at requirements/story level
We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
Trey S
almost 4 years ago
in Jira
0
Future consideration
Add the "[Updating]" tag to Integration Reports where applicable
When you make a change to an Integration being used as a template by other workspace/integrations, while the update is progressing through the dependent workspace/integrations sometimes you see an "[Updating]" tag next to the name in the left navb...
Jor Bratko
over 4 years ago
in Jira
1
Future consideration
In some cases depending on workflow stories created in JIRA prior to an Epic being linked in Aha do not flow to the aha record. In this case we would like to have an option to not only resend the epic record values but also all the linked records.
David G
over 4 years ago
in Jira
0
Future consideration
Features assuming the same release as its parent master feature when importing from Jira
Given that I have an epic in Jira, linked to a Master Feature in Aha
And the Master Feature is found in "Release X",
When I create a story beneath that epic in Jira,
Then the story should be imported as a child to the Master Feature,
AND assume ...
Guest
over 5 years ago
in Jira
0
Future consideration