As an Aha Administrator, I have a large number of products that link to one JIRA project and having to setup the same integration over and over again for these products is time consuming and painful. Setting up a JIRA integration at a higher level...
Aha! + JIRA feature/story relationships (e.g. is blocked by, depends on) should match
If one feature depends on another, and you create that dependency in Aha!, it will not be reflected in JIRA currently. If Aha! and JIRA feature/story relationships were maintained back and forth, then we could create more realistic roadmaps and st...
We have different workflows in JIRA for our Epics/Charters than we have for estimates or actual work tickets. It would be nice if when setting up the integration we could individually map both the feature and the requirements status messages indiv...
Allow customization of on-prem Jira link displayed in Feature details so that link actually works
High-level:
The URL that is used for integration with our on-prem Jira implementation is not the same as the URL that we use while on our network. Consequently, clickin on the Jira link within any feature takes us to nowhere. This enhancement req...
We use Master Releases when we have multiple products shipping together. I need the Master Release name to appear in Jira for reporting.
I'm flexible as to how this can be done. Maybe a way to create a custom field on the feature level that auto-p...
Avigail Ehrenhaus
over 9 years ago
in Jira
0
Shipped
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
For some reasons, I had to delete the integration with JIRA for a specific product line from Aha an...
Aha! relies on time tracking in JIRA being set to the default value of minutes. If the value in JIRA has been altered to anything else, it throws time tracking estimates off.
As of the 6.4.x version of the JIRA REST API a GET is available that ret...
Danny Archer
almost 10 years ago
in Jira
13
Shipped
Track effort (estimates) to prepare features for JIRA separately
When Aha!-JIRA integration is enabled, updating the features estimates on one of the tools, will cause an update on the other.
We suggest to have the possibility to un-map the estimates fields between the 2 tools. So updating on one tool won't aff...
The ability to do a bulk import exists, but if the issue already exists in Aha! it does not re-import. It would be useful to have the ability to alternately do a bulk update. This is particularly useful in the off chance something breaks with the ...
Danny Archer
almost 10 years ago
in Jira
2
Shipped
Configure JIRA integration for multiple products/projects at once
We have a large organization with ~400 projects in JIRA, where 1 JIRA project = 1 agile team. We would like to sync all teams' epics with Aha, but the current UI only allows creating integrations 1 product at a time. Assuming 1 Aha product = 1 JIR...