Currently if a story has belonged to more than one sprint, the sprint field concatenates the sprint.
For example, a story was in sprint 2019.5 and then moved to 2019.16 and then moved to unscheduled. In JIRA the story is none +2 indicating that ...
Integration with Jira: Ability to filter imported Jira releases/versions by date
Integration with Jira: Ability to filter imported Jira releases/versions by date
Problem: A lot of manual clean up is required when integrating with Jira projects that have many past releases. There is no functionality to filter out old releases. ...
I would like to know how the Original Estimate and Work Done fields are configured in Aha!. I have mapped (Jira)Total Story Points to (Aha!) Original Estimate and (Jira) Completed Story Points to (Aha!) Work Done. I'd like to know how to these pop...
Allow me to set up an account wide JIRA connection
We have several "products" in Aha and we have setup integration to JIRA on many of them. When our JIRA password changes, we have to visit each products settings page to update the JIRA connection. It would be nice if I could set up a JIRA connecti...
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...
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...
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...
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 ...
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.