All ideas
Sort by:
Trending
Status:
Showing 9041
2
VOTE
Please turn off the product suggestions and popups
Who would benefit? Everyday users What impact would it make? The popups with "news" is getting old quickly and disrupts everyday work. They are more frequent than before, almost to the point that I anticipate that I need to click something away be...
1
Already exists
2
VOTE
Add "Category" field to Documents & Links (Notebook Tab & Research Tab)
Who would benefit? Anyone looking for a specific kind of link or document. What impact would it make? It would reduce time to find documents, if you don't know the name. It would enable reporting out on specific kinds of documents. For instance, i...
1
Future consideration
5
VOTE
Restore the remaining estimate when a Requirement is moved from Shipped back to In Development
When a Requirement is shipped the remaining estimate will go to 0, but if that Requirement is re-opened then it will stay 0. Is there a way to restore the remaining estimate when a Requirement is re-opened?
3
Future consideration
7
VOTE
Including Dependencies in Jira integration at requirements/story level
We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
0
Future consideration
11
VOTE
Ability to see more than the last 200 logs in Aha-Jira Integrations
Sometimes we need to investigate synchronisation errors between Aha! and Jira. We can find these errors long after an initial error might have happened. We might need to go back to the original error which may have happened months ago. The limitat...
2
Future consideration
8
VOTE
Ability to restrict workspace owners to adding Viewer and Reviewer users only
It would be extremely beneficial to limit the control of adding paid seat user to administrators whilst still allowing workspace owners to add viewers and reviewers to their workspace. Where adding users is required to be restricted to administrat...
0
Future consideration
10
VOTE
12
VOTE
Synch story point estimates between Zenhub and Aha Epics (features)
We have linked Epics (Features) in Aha with Epics in Github Enterprise, and that is working fine. however we are using Zenhub to create story point estimates within Github, and would like to be able to reflect those estimates in Aha so we can do c...
4
Future consideration
15
VOTE
Allow for mapping to-dos in Asana integration
In some cases, Asana sub-tasks are more closely related to Aha! to-dos than requirements. For example, a feature may have to-dos related to marketing tasks which need to sync with Asana.
An option to map To-dos to Tasks or Subtask would provide a ...
4
Future consideration
20
VOTE
Allow sub-releases to have independent release dates from a Rollup Release date
We're operating in a CI/CD environment, and prefer to release "releases" (especially API's) as soon as they clear integration and performance testing. Forcing all of the sub-releases in a Master Release to inherit that release date is not meeting ...
11
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved