Skip to Main Content
ADD A NEW IDEA

Jira

Showing 168

The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.

Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...
Andrew Sweet about 5 years ago in Jira 1 Future consideration

Auto-sync of sprint field between JIRA and Aha

We implemented the sprint field mapping and have found that the sync isn't quite automatic. When we rename a sprint in JIRA - that shows up as a new sprint value along with the old one. This happens a lot and currently we run into a lot of confu...
Guest over 5 years ago in Jira 2 Future consideration

Ability to update a file attachment of a feature and update in the linked record of JIRA as well

Hi - We have Aha! - Jira integration where our features are mapped to JIRA stories. Features also have several file attachments which get propagated to JIRA stories. However, our Product Managers need to update the file attachments. Currently ther...
Michael Zadda over 6 years ago in Jira 1 Future consideration

Show required fields in integration mapping

When setting up an integration, it would be helpful to have a way to be prompted to map required fields in Jira. Currently, it is possible to create an integration that does not have field mappings for required fields in Jira. This causes the inte...
Madeleine Black over 1 year ago in Jira 1 Future consideration

Do not allow requirements to be mapped without a Links To relationship set

It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha! This results in import errors where requirements cannot be importe...
Madeleine Black over 1 year ago in Jira 0 Future consideration

Integrating with a specific Jira board

It would be helpful if we could use the Jira integration to send features to a specific board. We have several dev teams working within a single project, but they utilize different broads. We would like to send a feature to open a record is a spec...
Reut Levi over 1 year ago in Jira 1 Future consideration

Urgent Jira Integration Needs: Resolution, Resolved Date & Percent complete

These are critical to the success of our organization wide integration efforts which are ramping up very soon. Set a resolution in Jira when record is closed in Aha When Jira issues are closed the user is required to set a resolution during the tr...
Marcie Gardner about 2 years ago in Jira 2 Future consideration

Persistent filters for integrations and incoming product updates

Using JIRA integrations, I have an Aha product that spans several JIRA projects. To work with this I have set up an integration per project with a specified JQL filter. For example my filter could include "priority = high". Other products througho...
Guest over 5 years ago in Jira 0 Future consideration

Fix field population in Aha/Jira integrations to only rely on email address or other specific data

Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
Guest almost 2 years ago in Jira 1 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 over 2 years ago in Jira 0 Future consideration