Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 271 of 9560

Add option to show additional columns/fields in "Integration updates" window for Jira

The "Integration updates" window currently only shows the issue summary of incoming issues. Presumably the JSON payload being received by Aha contains the full set of information for the incoming issue ... it would be incredibly valuable to be abl...
Guest almost 2 years ago in Jira 0 Future consideration

Link user stories (requirements) in JIRA when under the same epic (feature)

We have features in Aha mapped to epics in JIRA, and then requirements mapped to user stories. I'd like the user stories in JIRA that I send over to automatically include links to their sister stories under the same epic, so that developers can ea...
Guest over 7 years ago in Jira 2 Future consideration

Please make the Jira Integration Ticket Link clickable

Please make the Jira Integration Ticket Link clickable, so it launches Jira
Guest almost 2 years ago in Jira 1 Already exists

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 ...
Guest over 7 years ago in Jira 1 Future consideration

JIRA Integration - Hide 'Send To' Options

Within the JIRA integration, add the ability to hide options to 'send to' JIRA and only show the 'link with existing' options. This would be helpful for integrations that are designed/configured to be only 1 way (JIRA to Aha).
Guest almost 2 years ago in Jira 1 Future consideration

JIRA integration Import of only linked epics

When stories in JIRA are moved between epics they are not automatically updated in aha. Also, for stories created prior to mapping a JIRA epic the stories are not automatically imported to aha. The import can be used to pull these in but the Impor...
Guest over 5 years ago in Jira 0 Future consideration

Only update Jira FixVersion if the Release has actually changed in Aha and the Jira FixVersion has not been edited

In my process I want Aha to be my master in terms of planning, but allow Jira to update details as actual releases are made. By this I mean that I will plan a release such as "Q4 2017" in Aha and push to Jira. As work is completed in Jira the issu...
Guest almost 8 years ago in Jira 0 Unlikely to implement

Ability to map Jira Web Links with Aha! URL at Integration

Why is it useful? Web links at Jira are used to show all the links associated to an issue/record. Who would benefits from it? Its easy for all users to view Aha! link at Jira epic or story rather than having it at a custom field. How should it wor...
Guest almost 4 years ago in Jira 0 Future consideration

Ability to aggreate work done value from both feature and requirements

Dear aha, in our scenario when AHA is synced with JIRA with time tracking attributes, we come into a problem with showing the complete work done on the feature when: 1. there is a time log in JIRA on epic (synced to feature) 2. there is a time log...
Guest almost 6 years ago in Jira 2 Future consideration

Allow users to name "Send To JIRA" when multiple JIRA projects are integrated

Allow users to name "Send To JIRA" when multiple JIRA projects are integrated Currently, I have three JIRA projects integrated to a single AHA product: LCI TEAM METHD UXH Currently, these three projects show up as Send to JIRA Send to JIRA Sen...
Guest about 8 years ago in Jira 5 Already exists