ADD A NEW IDEA

Jira

Showing 245 of 8636

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

Integrations 2.0 - Only show valid integration directions for Release <-> Fix Version

Integrations 2.0 - Please only show valid integration directions for Release <-> Fix Version. I had opened ticket https://support.aha.io/hc/requests/176083 because I could not connect to the Jira version using Actions > "Link with existin...
Guest over 6 years ago in Jira 0 Unlikely to implement

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

Prevent "roadmap drift" by displaying JIRA Epic labels next to Aha! Requirements.

This idea is a proposed work-around to this problem: https://big.ideas.aha.io/ideas/APP-I-2702. Until that problem is fixed, I need an easy way to spot when Requirements and Stories have inadvertently drifted (i.e. Stories have been moved to anoth...
Guest almost 7 years ago in Jira 0 Future consideration

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

Two-factor authentication for the integration Aha! to JIRA

Quoting my mail replying back to Brian deHaaff: Hi Brian,thanks a lot for the offer to help with my onboarding – the idea to trigger this communication from the Founder / CEO indeed transports a feeling of importance that makes it hard not to res...
Guest about 7 years ago in Jira 0 Unlikely to implement

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 almost 8 years ago in Jira 3 Already exists

Features linked to JIRA tickets should have JIRA in control of status

When I have a feature linked to a JIRA and a few requirements also linked to JIRAs my expected result is that fields linked with JIRA are controlled by the data in JIRA. For example, if I close all of the requirements within the feature but the JI...
Guest about 8 years ago in Jira 0 Unlikely to implement

Prevent feature workflow from moving if a feature is in JIRA already

If the feature taskflow is aligned with the status of features in JIRA, the status of the feature will automatically update in Aha as the feature progresses through the development phase; this is good. What's problematic though is the user can adj...
Dale Burnett over 8 years ago in Features / Jira 0 Will not implement

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