Ability to associate a feature created in JIRA to a Master feature in Aha!
We have Engineers that take the Customer focused epic and break that down into multiple epics (sometimes technical), so we don't want to have them to get out of the tool they work in (JIRA) and switch to Aha!, just to enter the new features for th...
It would be great to be able to easily communicate the rank order of a feature from Aha! to JIRA. If we created a custom field in JIRA for "Aha! Rank" and send the rank over to that field that would be a step in the right direction. Or alternately...
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 re...
We currently use Google SSO for our JIRA system. The Aha! integration however requires a username/password user account & not an SSO user.
I need to be able to use an SSO user for the integration, since that is the only option that our JIRA ...
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 ...
Improve warning for integrations "Update Records" action
For a development tool integration (i.e. Jira), there's an "Update Records" button. When clicked, you get this attached warning. This doesn't warn you that Aha! will send data for any one-way mapped fields (Aha! --> Jira) as well. It would be h...
Better requirements link handling in Jira integration
From the Jira "READ SECOND" blog post: "If a new issue is created in JIRA that belongs to a record that is already link to Aha!, then the issue will be automatically imported to Aha! This applies to issues created under a version, stories created ...
Aaron Bawcom
almost 9 years ago
in Features / Jira
1
Shipped
Currently, we need two Jira integrations - one for Bugs, and one for everything else. But when importing/linking Bugs, they get linked to a regular ol' Feature of "New" type.
As someone in this situation, i want imported/linked Jira Bugs to set t...
Two Way Jira Sync for Initiative/ Epic custom fields
As far as I am aware you can only map feature custom fields, and I'd like to be able to maintain due dates, team and other custom fields at the Initiative level.
Ability to sync more than one Issue Type to a Record
It's critical for us to track bugs/defects in Aha! related to a specific release but these bugs/defects belong to Features that have other WIP Stories. We need to be able to sync different Issue Types from JIRA to the Requirement record in Aha! Th...