Share your product feedback

ADD A NEW IDEA

Jira

Showing 174

Jira integration reset

In some cases depending on workflow stories created in JIRA prior to an Epic being linked in Aha do not flow to the aha record. In this case we would like to have an option to not only resend the epic record values but also all the linked records.
David G about 4 years ago in Jira 0 Future consideration

Jira Sync Aha Release Phases and To-Dos

Please enable the ability to sync a release phase to an Epic in Jira. And also sync release phase To-Dos to tasks in Jira. Use Case: I have a release template with my release phase and associated to-dos. These to-dos are what govern my Jira tasks....
Guest over 4 years ago in Jira 0 Future consideration

Include Jira Dynamic Dates in API

When integrating AHA / Jira the field mapping only shows fields that can be editable. We are looking to bring in Created Date and Resolved Date on both the Jira epic and Jira story. These fields are dynamically created and populated based on the f...
Roger Octobre over 4 years ago in Jira 0 Future consideration

Add Closing Comment for Jira Integration

Our Jira environment has a requirement to enter a comment when "closing" a ticket. Aha does not have a place for this so if Aha! users close a feature in Aha, they will have to login to Jira and close it there as well. The request is to allow a "c...
Guest over 4 years ago in Jira 0 Future consideration

Assign Integration to Specific User

Need the ability to assign a JIRA integration to a specific Aha! user instead of having each PM need to navigate to the integration and select Run As.
Yancey Larochelle-Williams over 4 years ago in Jira 0 Future consideration

Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features

Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
Dale Potter over 4 years ago in Jira 0 Future consideration

Parent version mapped to 2 different releases - let user decide where to import

The same Jira version may be associated with releases from more than one Aha! workspace. This can happen when different products in Aha! are all being released together. When auto-import is enabled on the integrations and a new record is created i...
Mark Crowe over 4 years ago in Jira 0 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

Jira Integration of custom calculated field

We have a Jira project that supports multiple engineering teams. Each team has their own release schedule. We need a way populate fixversions in jira with team specific values. The creation of a custom field that combines "product prefix-release n...
Russell Roach over 4 years ago in Jira 3 Future consideration

Add support for Jira Portfolio "Team" field

Jira Portfolio adds the Team custom field to JIRA. This team is used in Portfolio for planning. Aha! should support mapping this custom field so that the assignment of work and resource planning can be synchronized between Jira and Aha!
Scott McLean almost 5 years ago in Jira 1 Future consideration
Idea management by Aha!
Create your own ideas portal to crowdsource feedback
© 2025 Aha! Labs Inc.•All rights reserved