Jira
Sort by:
Trending
Status:
Showing 261
1
VOTE
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.
1
Already exists
1
VOTE
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 resp...
0
Unlikely to implement
1
VOTE
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 ...
3
Already exists
1
VOTE
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...
0
Unlikely to implement
1
VOTE
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...
0
Will not implement
1
VOTE
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 quic...
2
Already exists
1
VOTE
Allow tracking simultaneous tracking of both Feature-Level and By-Requirement estimates
The current AHA/JIRA estimate integration allows feature level OR requirement level estimates, however as we don't use JIRA for time tracking we want to use JIRAs 'Original Estimate' field with AHA's per-requirement estimates.
My suggestion would ...
0
Unlikely to implement
1
VOTE
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...
0
Already exists
1
VOTE
0
VOTE
Add support for Jira transition webhooks
Jira has two kinds of webhooks: Event webhooks that are triggered when a Jira event happens, for example an issue is updated. This is supported by the Aha! Jira integration Transition webhooks that are triggered when a Jira issue changes status. T...
0
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved