Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 179

History of items created via integration

In Jira integration 2.0, there's no link or reference to the items created by the integration once you approve them. A modal notification like you currently use would work at a one-by-one level. If that makes sense. Even better would be a tab in ...
Max Cascone over 7 years ago in Jira 1 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 over 7 years ago in Dependencies / Jira 3 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 7 years ago in Jira 1 Future consideration

Add ability to map Custom Aha! Tables to Jira

Add the ability to map custom fields from custom tables in Aha! to Jira.
Guest about 8 years ago in Jira 6 Future consideration

Ability to create JIRA integration thorough Aha API

We have teams with several projects and creating it through templates is not practically scalable, hence require an API to create JIRA integration manually
Guest about 8 years ago in Jira 3 Future consideration
205 VOTE

Dedicated Integration User

It would be great to have a dedicated integration user instead of having to use a user license for this purpose. I would love to keep my user and the updates from integrations (Jira, TFS,...etc) separate so that it is clear who made the update in ...
Guest over 8 years ago in Integrations / Jira 16 Future consideration

Sync story points to Jira without Capacity Planning

My teams doesn't use capacity planning, as we have the same team members each week, but we'd like to be able to automatically link story points to Jira. Currently this is only accomplishable when you have enabled capacity planning, which causes me...
Michael Clinton about 9 years ago in Jira 1 Future consideration

Support for Jira Code Markup

Need to support the Jira code markup option. If the developer enters sample code as part of the description in Jira, the description gets updated in Aha! However the code markup is translated into very large tables in Aha! At some point, Aha! upda...
Guest over 9 years ago in Jira 2 Future consideration

Handle multiple FixVersions in JIRA

An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix versio...
Danny Archer over 9 years ago in Jira 17 Future consideration