Jira
Sort by:
Trending
Status:
Future consideration
Showing 261
68
VOTE
Handle multiple FixVersions in JIRA
An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix versio...
15
Future consideration
11
VOTE
Support updating JIRA Integration Links by csv upload
While I recognise that moving JIRA issues between projects breaks the AHA integration links, the workarounds proposed here are not helpful. Option 1 ("Relink each record manually") is the only viable workaround, with options 2 and 3 being too haza...
0
Future consideration
12
VOTE
Provide alternative way to match users when email address is not exposed in Jira
Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...
1
Future consideration
30
VOTE
Jira sprint dates as feature end dates
With the Jira integration it is possible to pull through the Sprint name as a custom field into Aha Master Features/Features. It would be useful to be pull through the sprint finish date and apply that to all linked items within Aha. This would al...
4
Future consideration
40
VOTE
4
VOTE
Epic progress doesn't update when it has children in different projects
Who would benefit? Customer using Jira epics to manage work in multiple projects What impact would it make? They would be able to see their progress in Aha! correctly How should it work? If you have an epic in Project A, and it has multiple childr...
0
Future consideration
1
VOTE
Jira integrations : Add the capability to use filters instead of boards to set up integrations
What is the challenge? the boards only have tickets currently worked on , we want to load all tickets , so we can plan , this is because the team sometimes their create their own What is the impact? if you need to split a jira project with multipl...
0
Future consideration
37
VOTE
Integrations 2.0: Add dependency link to connect records without natural relationships together
In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other. ...
3
Future consideration
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
5
VOTE
Improving handling when Jira users change issue type across record hierarchy
Who would benefit? Users of Jira integration What impact would it make? Users who are changing issue types in Jira after records are integrated. How should it work? Right now, if a Jira user changes an issue type on an integrated record, the integ...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved