All ideas
Sort by:
Trending
Status:
Showing 8938
1
VOTE
Mobile App - New Idea should match new idea entry layout
What is the challenge? Current mobile app implementation forces new idea entry to show the view layout and make all fields required. Only specific fields should be required for new idea entry as some are derived after-the-fact. What is the impact?...
2
Future consideration
1
VOTE
Steps within user story maps can't be utilized in a pivot table
What is the challenge? unable to include user steps from a story map to help provide a comprehensive view of a release with a pivot table What is the impact? requires multiple pivot table views to tell complete story Describe your idea allow user ...
0
Future consideration
1
VOTE
User story maps should respect custom card layouts for Epics/Features
What is the challenge? Not enough information is displayed in cards in story maps requriing constant clicking through to details What is the impact? Difficult to use story maps interactively with users Describe your idea Use card layouts for epics...
0
Future consideration
1
VOTE
Cross-workspace user story maps
What is the challenge? Most of our user journeys go across multiple products. When we story map these journeys, and create features off them, we want to be able to add features across multiple workspaces in AHA. What is the impact? Can only story ...
0
Future consideration
1
VOTE
4
VOTE
When creating a new Ideas record, you cannot add new Tags values like you can in the same field on the edit screen
When working with Ideas directly in Aha! (not via the Ideas portal) there is a discrepancy with how the Tags field works. On the Create ideas form, the Tags field does not allow you to add new values (see attached Create Idea Tags field no results...
2
Future consideration
4
VOTE
Provide a warning explaining consequences when changing the workflow used in a workspace
When a user moves to a new workflow in a workspace or team, there can be a loss of data related to the statuses like cycle time, time in status, etc. I would like to understand these consequences before making the change so I am not surprised with...
1
Will not implement
2
VOTE
Retrospective should ignore records that were moved in with "Will not implement" status
Who would benefit? Product Owners and Project Managers What impact would it make? This would reduce the list of records shown as "incomplete" when the records were added to the release after already been assigned "Will not implement" How should it...
0
Future consideration
27
VOTE
Kanban Board - Work-in-Progress (WIP) limit for status columns
Reference: https://en.wikipedia.org/wiki/Kanban_board
Work-in-progress (WIP) is a key design principle for Kanban. The ability to limit the number of items for each status column is part of the Kanban workflow. The limits per column should be use...
6
Unlikely to implement
25
VOTE
Self Registration Capability for User Acess
We are a large organization with many users. We would like to share Aha! with interested individuals and that number could be hundreds or thousands. In order to alleviate that, the recommendation is to allow a self registration process that would ...
8
Unlikely to implement