Skip to Main Content
ADD A NEW IDEA

Jira

Showing 41

Need configuration to allow allow/block execution system (JIRA) initiated Epics back to Aha

For Epics which get initiated in Aha and flow down to JIRA, we want to enable 2-way integration so that updates which happen in JIRA are realized in Aha. However, if a NEW Epic is initiated on the JIRA side, we may not want that to be visible in A...
Guest about 6 years ago in Jira 1 Already exists

Automatically reduce feature estimate when requirement is completed

When using the requirements level estimates to drive the total estimate on the feature level we would like the feature level estimate to be reduced when a requirement is marked in a complete status. Also we would like to have the feature status au...
Guest about 6 years ago in Jira 0 Already exists

"Update JIRA" option for Requirements

If I update a Requirement after the Feature has been synced to JIRA, I want to be able to immediately have the corresponding Story in JIRA updated to match it. The synchronisation seems to take more than 10 minutes to go through. Like we have Acti...
Guest about 6 years ago in Jira 0 Already exists

Fix Time Tracking Totals when using Requirements

Currently: With the JIRA 1.0 integration. When using Requirements for Time Tracking the "Total Time" is not displaying the correct data. In Aha the Time Tracking says 73d 4h. Screenshot "Aha Time Tracking.png" In Jira the Time Tracking says 2w ...
Guest about 6 years ago in Jira 1 Already exists

Add Support for JIRA Data Center / Server

Larger customers who are on Server and Data Center can take advantage of your add-on.
Guest over 6 years ago in Jira 0 Already exists

Update JIRA with updated Aha Requirement definitions

When we update a requirement in Aha with a new or updated requirement definition, and there is already an existing JIRA link, the updated copy doesn't transfer over to the JIRA User Story, even when we select "Update JIRA" from the Actions menu.
Guest almost 7 years ago in Jira 1 Already exists

Provide the ability to map multiple ticket types to requirements

We are hooking Features into Epics, and discussing with development and the rest of the product team, the individual enhancements, new features, and tasks that are required to be performed for the "Epic" to be completed. Aha/Jira integration only ...
Guest over 7 years ago in Jira 3 Already exists

JIRA integration - Send to JIRA - labelling

Hi Guys We have mutiple JIRA to single Aha! product, so when sending we see the image attached. You cannot distinguish which JIRA in this list - please extend to: Send to JIRA: VIS - where VIS is the name of the JIRA project. Seems a simple qu...
Andrew Tipton over 8 years ago in Jira 2 Already exists

Pull JIRA Original Estimate not Remaining Estimate

We use sub-tasks or even regular tickets in JIRA to do our estimates so they can be planned into sprints. When these estimate tickets are closed on the JIRA side it seems that the estimates they are for are zeroed out on the Aha side. The only thi...
Guest over 8 years ago in Jira 0 Already exists

Assignee does not get sent to Jira if using Default Assignee functionality

If you use the "default assignee" functionality, then that assignee will not get sent to Jira, even if that user exists in Jira. This could be considered a bug.
Avigail Ehrenhaus over 8 years ago in Jira 0 Already exists