Application
Sort by:
Trending
Status:
Showing 7646
4
VOTE
Allow to-do's to be moved to iteration records
Who would benefit? Develop users What impact would it make? Currently users are able to move to-do records to all other roadmap record types (goals, releases, epics, features, etc), but not iterations. Iterations already support to-do's so this wo...
0
Future consideration
4
VOTE
Add option to delete child notes when deleting a folder
In Knowledge, when a folder is deleted, the child folders/notes are not deleted with it. It would be helpful to present the user with an option in a modal to delete just the folder, or delete the child folders/notes as well. Though you can use Shi...
0
Future consideration
24
VOTE
Ability to configure automated status logic
For almost all our workflows, a parent record's status is dictated or a reflection of it's child record's status - similar to how the progress of a parent record is an aggregate of it's child records and that functionality. I would like the abilit...
3
Future consideration
15
VOTE
Support approval gates in Aha! Develop
Quality is critical for my product. I want to ensure that all features go through QA testing before being marked as "done". The approval workflows implemented by Aha! Roadmaps solve my need well. I want Aha! Develop to respect those workflows as w...
1
Future consideration
10
VOTE
Requirements capacity planning
We have users stories mapped to requirements in Aha!. When viewing the capacity planning at a requirement level it uses the feature level start and end date, we want to see the start and end date of the requirement (Story). Also related to this in...
0
Future consideration
8
VOTE
Automated Rule for License from Owner/Contributor to Reviewer/Viewer
I would like to explore if Aha can provide that automation wherein if Admin users like owner/Contributor who have not contributed to Aha in the last 1 month or so (which can be configured) and downgrade the same to Reviewer/Viewer so that those li...
1
Future consideration
30
VOTE
Ability to show 2 types of records in one column (master feature and feature records) but in different cells/rows in a Pivot report when the records are not linked.
In our configuration, we have either Epics(Features) or Master features linked to a Goal. In a pivot report, we want to show all Epics and Master Features linked to the Goal in one column.
For the report, the primary record is the Goal and Epics...
8
Future consideration
2
VOTE
Customizable header and footer section in shared web page
What is the challenge? When a shared web page is generated an automatic header is generated. This header is not editable and most often not aligned with Aha customer brand + not allows for navigational elements, contact information etc. What is th...
3
Future consideration
4
VOTE
Whiteboard - Miro Card Functionality
Who would benefit? Users in planning phases, not yet ready to commit future work to a Feature/Epic yet. What impact would it make? More information and context to a whiteboard item to determine where it should be planned. How should it work? Curre...
2
Future consideration
6
VOTE
Automation conditions based on related item fields
Who would benefit? All Users What impact would it make? We'd like to be able to create automations such as the following which is currently not possible: When an activity is created or updated and the related workspace changes (EG - the activity i...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved