My ideas
Sort by:
Trending
Filter by:
Status
Showing 8967 of 8967
1
VOTE
Add a 'Viewed' button to 'Idea's with vote's' area
Why is it useful? This is useful because we monitor the ideas so we do not end up with hundreds of ideas in this queue for an unlimited amount of time. So I know if everyone that is a stakeholder has at least viewed the idea. Who would benefit fro...
0
Future consideration
1
VOTE
1
VOTE
'Add as logged time' setting only works on initial completion
Current behavior (working as expected): Create a feature in Aha! And send it to Jira Update the “Story Points” field in Jira to 10p which syncs back to Aha! Change the Jira Story status to ‘Done’ which syncs back to Aha! and updates the ‘actual ef...
0
Future consideration
3
VOTE
Integration between Aha! and Jira Align (formerly Agilecraft)
Jira Align is a requirements tracking platform that was formerly Agilecraft, and is fully integrated with Jira. Our teams that are using both Jira and Jira Align are mapping their Epics in Jira to parent Epics in Jira Align, so that the roll-up pr...
1
Future consideration
4
VOTE
Allow related record links to persist when records are converted
Currently when you convert a record (ex. Feature to Master Feature), all record links are severed. It makes sense to sever the link to parent/child records, but links like "relates to" and "depends on" would still be relevant even if the record is...
1
Future consideration
8
VOTE
Ability to choose how each Aha Initiative/Feature/Requirement should be mapped to JIRA, as opposed to one mapping setting for an Aha product.
As a user, when creating a new Aha Initiative or Feature, I would like the ability to choose whether the Aha Initiative/Feature/Requirement should be mapped as a JIRA Epic, User Story, or Requirement, so that I can have more flexibility when creat...
0
Unlikely to implement
4
VOTE
Ability to set a default sorting for all releases
In addition to the "re-rank features by" status within the individual releases, there should be the ability to set a DEFAULT ranking of features within a release for all releases, for example, by status, so that all new releases added would have t...
0
Future consideration
3
VOTE
Allow mapping Release as a field on Requirements in Azure DevOps integration
Due to our iterations setup in Azure DevOps (ADO) we do not currently map Releases as a record. We are sending this instead as a field on the Epic and Feature records to a custom field in ADO. We would like to do the same on Requirements but it is...
0
Future consideration
1
VOTE
Improve UX when searching for linked record
Linking records together is a really useful function but we find it is not self-explanatory for our users and leads to many questions. Just adding some additional directional text here telling folks they can type ahead of search would really help.
0
Future consideration
1
VOTE
