Jira
Sort by:
Trending
Status:
Planning to implement
Showing 3
7
VOTE
Features and Epics should move to integrated parent Release upon updates
What is the challenge? If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but t...
0
Planning to implement
1
VOTE
Ability to sync Jira's "Team" bidirectionally
What is the challenge? Out-of-the-box Jira field values cannot be synced, causing the inability to bidirectionally sync that field between Aha and Jira. What is the impact? Aha is meant to be the singular solution for Product teams to set their st...
0
Planning to implement
46
VOTE
JIRA: Detect default unit of time tracking
Aha! relies on time tracking in JIRA being set to the default value of minutes. If the value in JIRA has been altered to anything else, it throws time tracking estimates off.
As of the 6.4.x version of the JIRA REST API a GET is available that ret...
12
Planning to implement
© 2024 Aha! Labs Inc.•All rights reserved