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.

We currently sync a field in Aha! to Jira when a record is created. We’d like to clear that field if the record is deleted from Aha! I’m looking to send an update to the field or set an event trigger to make a note that the field value has changed.

Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.

We need a way to prevent an end user from selecting the option in Integrations to Send to Jira unless the Status = Open. With it set to any other status, it causes Integration issues. We dont want to have to set up approvals to verify this. Just w...

When you make a change to an Integration being used as a template by other workspace/integrations, while the update is progressing through the dependent workspace/integrations sometimes you see an "[Updating]" tag next to the name in the left navb...

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.

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....

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...

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...

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.