We want to show a dependency of one of our Features on a deliverable from another team without having to create a separate feature and map and sync it through the regular JIRA integration. I think being able to import the JIRA link (and description) and show it as a blocking dependency as I can with Aha! records would meet this need without having to set up a separate feature to cover their deliverable.
Thank you for your idea. One option that could help here would be to create a custom field where you can list any dependent records from Jira on your features in Aha!
At this time, based on historical demand for this idea and the option listed above, we are unlikely to implement this idea. We hope you can understand.
It would also be great if we could sync all dependency links from Aha! to Azure DevOps.
For example, we use Aha! to map dependencies between Features to display on the Gantt Chart. These dependency links appear on the Feature under "Record links" as "depends on" or "is a dependency of" links. When I sync the Feature with ADO, it would be great if those links could be synchronized and appear in ADO under "Related work" as "successor" or "predecessor" links.
Something I missed off originally - If a Feature is given blocking JIRAs as described above I would also like any synchronized/integrated JIRA linked to the Feature to have these same blocking JIRAs. Thus engineering can and navigate all their dependencies within JIRA and PM can see and navigate all their dependencies in Aha!.