All ideas
Sort by:
Trending
Filter by:
Status
Showing 8928 of 8928
4
VOTE
Allow team members with Aha! Develop permissions to be able to add and update research notes on features from Aha! Roadmaps
What is the challenge? When features are assigned to a team in Aha! Develop, team members that don't have roadmap permissions can not add additional documentation to the research tab as it attempts to add the notes to the Roadmap level Knowledge B...
1
Future consideration
103
VOTE
Updating a feature's dates should automatically adjust dates of features with downstream dependencies
Summary:
This comes from a project management use case where a team manages a set of activities/tasks through Features for a project and the activities have a very sequential delivery with fixed offsets between each activity. The plan starts off ...
10
Future consideration
7
VOTE
Multi-language support in KBs
What is the challenge? Non-English speaking users need to access content in a KB. Currently a separate KB must be generated in each applicable language. How would you solve it? Provide KB translation. What impact would it make? Allow non-English s...
3
Future consideration
53
VOTE
Report on a values historic values
Enable the user to report on the values of a field based on its history. maybe a calculated field property where you indicate the field and the version back for that field. History(Custom_Field1,1) would show the value of that field one change bac...
5
Future consideration
38
VOTE
Show child initiatives nested under parent initiatives on the strategic roadmap
We have initiatives with child initiatives and those child initiatives contain releases, epics and features. The child initiatives are in a separate workspace line from the parent initiatives. The Strategy>Initiatives>Roadmap view works fine...
2
Future consideration
24
VOTE
Allow formatting and wrapping text on chart labels
I never use Aha charts in our internal reports because the labels display poorly. It's a shame, because it prevents our org from more fully adopting Aha. I export everything to do reporting in a Spreadsheet simply because the labels are unhelpful ...
2
Future consideration
8
VOTE
Ability to Configure Epic View as Default for all workspace views (Board / Prioritization)
Who would benefit? Enterprises who maintain Epic only or use Epic as primary record type. What impact would it make? Reduce confusion. The teams are currently directed to feature view on the board and prioritization view by default. Per Aha concie...
0
Future consideration
13
VOTE
Show more context for added/removed records in retrospective report
I want to understand more about the records that are added to or removed from a release: When was it removed? Where was it moved to? What is its current status? I would like to see this information in the retrospective report
1
Future consideration
85
VOTE
Don't remove lane in feature board view once shipped
Currently when you ship a release the lane disappears from the feature board view. It would be great if instead of disappearing all together the lane was simply greyed out or marked as shipped. The feature board view is where we look to see what w...
26
Unlikely to implement
4
VOTE
Knowledge base page publishes automatically once approved
What is the challenge? We want KB pages to be approved before they are published. What is the impact? It is a manual process right now and we have to trust users that they will not publish a page before all the approvals have been given. Describe ...
2
Future consideration