All ideas
Sort by:
Trending
Filter by:
Status
Showing 9172 of 9172
1
VOTE
Allow scorecard at release level
Right now custom scorecards can be assigned only at the workspace lvl, which does not really allow for changing priorities and weightings. Worse, if we do change any fundamental portion of a scorecard, it will mass update everything in that worksp...
0
Future consideration
2
VOTE
show feature status for roadmap items marked "Not Shown In Notebook"
when you unselect a feature on a roadmap so that it will "not show in notebook", it moves to a section below the items that are shown grouped by status. Just because I don't want something shown in the notebook, doesnt mean that I don't want to kn...
0
Unlikely to implement
1
VOTE
Reporting on release phases/milestones comment field should only show the entered comment
When reporting release phase (or milestone) comment, the user who entered the comment and the date the comment was entered is included. Desire to see ONLY the comment in reports and NOT the "log" associated with the comment. Perhaps a second field...
0
Future consideration
1
VOTE
Watch changes in a workspace, but Releases OR Features only, not everything.
Currently I can watch at a workspace level, but it is overwhelming with the number of features being added. I would like to only be notified for changes happening on release timeline (phases and milestones). I don't really care about new or modifi...
1
Unlikely to implement
2
VOTE
Better Comment Visibility / Consolidated View
Aha does a great job of surfacing all the attachments onto one page ((product > files), no matter where in the content they are(initiative, feature, requirement, release, added to a comment, etc). But if people write comments, they are buried d...
1
Will not implement
2
VOTE
When new users are added to Aha, default them to unchecked in the workflow boards.
We're using the Workflow board and loving it. However, whenever new people from our company are added to Aha, they are added by default to the board and it screws it all up. We really only assign stories to our designer and the rest go to "default...
1
Already exists
2
VOTE
Break the Product Family/Initiative Hierarchy Restriction
Currently you can only have as many levels of initiative hierarchy as there are Product Family/Products. But in tools like Version1 or Jira, the Epic structure is not similarly restricted – I can create as many levels of Epics as I want in V1 (I a...
0
Unlikely to implement
2
VOTE
Allow blocking off time periods when release should not be shipped (promoted to production).
In our operations, we have some periods where no changes are permitted in production. It would be beneficial to add blackout periods so that any release dates within the blackout periods can be highlighted/reported.
0
Unlikely to implement
1
VOTE
Progress Bar Update for Features to Match Releases
You are currently able to up date Releases to calculate Feature progress as 'Features' or 'Features Complete'. You should have this same option for Feature>Requirements. I understand that there is the option to calculate from Story Points but n...
3
Future consideration
1
VOTE
Release Should Be Marked as Shipped only when all Integrations for JIRA projects are shipped
If multiple integrations are enabled at release level, allow workflow rule for release to be considered as shipped when all integrated JIRA projects have shipped the release If someone marks the release as shipped in JIRA, its changing the status ...
0
Unlikely to implement
© 2025 Aha! Labs Inc.•All rights reserved