Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 276

Epic progress doesn't update when it has children in different projects

Who would benefit? Customer using Jira epics to manage work in multiple projects What impact would it make? They would be able to see their progress in Aha! correctly How should it work? If you have an epic in Project A, and it has multiple childr...
Kyle d'Oliveira almost 2 years ago in Jira 2 Future consideration

Ability to map custom Initiative fields in Jira integrations

What is the challenge? Currently you can add custom initiative fields to record layouts, but these fields are not available to map in the Jira integration. What is the impact? Unable to pass this information over to Jira Describe your ...
Stephanie Lechner 4 months ago in Jira 0 Future consideration

Ability to create a report of integration errors across multiple workspaces

Currently the only way to look at the integration errors across multiple workspaces is to bring up the Integration Updates dialog and use the Send outgoing changes tab. But you can't filter on error text, or expand the window to see the everything...
Jor Bratko over 4 years ago in Jira 7 Likely to implement

When linking an Aha! record to an existing Jira record, perform a full sync of all fields

What is the challenge? When "Use Jira and overwrite Aha!" is selected, there is a full sync of all fields, allowing fields to update in Jira. But, when "Use Aha! and overwrite Jira" is selected, that same full sync is not performed, and one-way ...
Leigh Villalovos 9 months ago in Jira 0 Future consideration

Jira sprint dates as feature end dates

With the Jira integration it is possible to pull through the Sprint name as a custom field into Aha Master Features/Features. It would be useful to be pull through the sprint finish date and apply that to all linked items within Aha. This would al...
John Biltcliffe over 6 years ago in Jira 5 Future consideration

Integrations 2.0: Add dependency link to connect records without natural relationships together

In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other. ...
Danny Archer about 8 years ago in Dependencies / Jira 3 Future consideration

Improving handling when Jira users change issue type across record hierarchy

Who would benefit? Users of Jira integration What impact would it make? Users who are changing issue types in Jira after records are integrated. How should it work? Right now, if a Jira user changes an issue type on an integrated record, the integ...
Stephanie Lechner about 2 years ago in Jira 0 Future consideration

Support the ability to change a Jira project key

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.
Wayland Fox almost 5 years ago in Jira 0 Future consideration

Keep formatting from a Jira table

What is the challenge? The Jira integration does not currently support the table markdown syntax What is the impact? The result is a formatting issues when a record including a table within the description is synced to Aha! via the integration Des...
Terri Salie over 1 year ago in Jira 1 Future consideration

Notification when an integration is down

Would like to see some way of setting user(s) to be notified if there is an interruption in communication between integrated system.
Guest over 2 years ago in Jira 1 Likely to implement