Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 177

We need the Initiative ID available in JIRA integrations so they can be reference-able in other tool dashboards.

We use the Aha API to populate views in Tableau. The Initiative [API] ID is a crucial portion of making sure what we sync to JIRA from Aha and what we are looking at in Tableau which provides a combined view of both tools, is one and the same. I a...
Wen-Wen Lin over 5 years ago in Jira 1 Future consideration

Ability to apply a Jira Integration Template to an EXISTING Jira Integration but only have it update the URL and Jira Login/Password settings

We had a very large number of Jira Integrations created before we had central administration of our Aha application. I need to apply a Jira template to these integrations so that the URL and password can be managed from a central person, but if I ...
Leanne Miller over 4 years ago in Jira 0 Future consideration

Enable Field Filters for when to Sync to Aha

I would like to be able to set a filter in my Integration for which Jira Issues to sync up. An example would be to not push stories into Aha until there is a point value or time estimate entered in Jira. Another would be to only push to Jira if it...
Kenny Burnham almost 6 years ago in Jira 0 Future consideration

Add a way to push all features from a master release to Jira at once

I am managing a few master releases right now with dates that are moving around, and it is currently time-consuming to send updated release dates of all sub-releases to Jira (and easy to miss one!). I’d also like the ability to reshape features, e...
Guest almost 6 years ago in Integrations / Jira 2 Future consideration

Ability to configure integrations not to create new records in Aha

In the 1.0 integrations I had configured it to not try to create new Aha! records when records were created in JIRA. I would like to be able to do the same in the 2.0 integrations. Currently when someone creates a new issue in JIRA I see this appe...
Kevin Burges about 7 years ago in Jira 0 Future consideration

Push mock-ups from Aha! to Jira Draw.io plugin

We create UX/UI mock-ups in Aha!, and I would likedevelopers to be able to see them after the feature is pushed into their Jira backlog. I noticed that both Aha! and Jira use Draw.io for mockups. Is there any way Aha! can upload mock-ups associate...
Guest about 6 years ago in Jira 4 Future consideration

JIRA integration to track correct users in history of issues

Today the Aha JIRA integration will leverage the user account setup in the integration settings as the actor for all integration sends between the systems. This creates a lot of confusion for who actually made changes in one system or the other. F...
Austin Churchill over 3 years ago in Jira 1 Future consideration

Jira Integrations: Map Aha Releases to a custom Jira Version Field

Who would benefit? Any Aha customer with jira integration that uses a separate jira field that has version data as values to enter. In my jira project I use a different field (other than fix version) to track what release our features will release...
Kyle Shannon over 1 year ago in Jira 0 Future consideration

Integration with JIRA needs better Error handling support

Aha! integration with JIRA does not notify users on errors that would have happened during the integration (i.e. push/pull). This keeps the users in dark on what would have gone wrong and requires manual intervention to detect errors.
Guest over 5 years ago in Jira 1 Future consideration

use Jira credentials of the user to record changes in Jira

In the Aha! user profile, request the Jira credentials of the user. When making updates to Jira tickets, use these credentials so that we can see in the JIra ticket who actually mae the update. Kendis does this.
Guest about 4 years ago in Jira 0 Future consideration