All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5871
1
VOTE
Exclude completed ToDos from summary counts on Features and Initiatives
Who would benefit? everyone What impact would it make? large How should it work? When I look at a Feature or an Initiative and see a count of "todo"s, I would like this count to exclude completed items so I can focus on only those items which requ...
0
Future consideration
1
VOTE
change chart checkbox logic
Who would benefit? anyone making a chart What impact would it make? better ux How should it work? when i select a top level parent category checkbox to filter by, and it has children paramters, they should all get checked too. Also, when I save ch...
0
Future consideration
2
VOTE
1
VOTE
make it easier to work with Epics
Who would benefit? PMs What impact would it make? Ability to more quickly prioritize, sequence and schedule work in the context of user need driven planning (epics) as opposed to functionality driven planning (features) How should it work? If you ...
0
Future consideration
1
VOTE
Batch Update Workspace Settings
Who would benefit? Aha Administrators What impact would it make? Reducing my time spend manually updating workplace settings, specifically ones that do not have the ability to inherit from the parent i.e Scorecards for Initiatives How should it wo...
0
Future consideration
1
VOTE
Add Github integration for all repositories
We need to enable all of the repositories for the issue linking and enable new repositories automatically. Currently, within the GitHub integration page we need to provide the repository names explicitly. I am not sure if this is the target extens...
0
Future consideration
2
VOTE
Enhancements to ideas --> Overview
Some enhancements to the Ideas Overview to make it more useful: Allow admin to configure the order that statuses appear in the list to allign to workflow or business process vs. organized by largest number. Create a Kanban view (workflow view) of ...
0
Future consideration
6
VOTE
Integrate Master Features and related features to different JIRA projects
In this scenario, there is one Program product workspace in Aha! and one Program project in JIRA which contains Master Features per Agile Release Train. All Stories (Aha Features) and sub-tasks (Aha Requirements) are with one or many Agile Teams (...
1
Future consideration
6
VOTE
Require approval for changes to certain fields
We would like to be able to 'lock down' some fields unless there is approval to change them. For example, Release date (or due date) Budget Designated people in the company would be required to approve any changes to these fields. Along with this,...
1
Future consideration
1
VOTE
Enable Sorting Release Phases Numerically - Gantt Chart
Who would benefit? Customers whose milestones need to tie to line items on a project plan or other numerical milestone designation What impact would it make? Enable those organizations to plan in Aha! rather than MS Project How should it work? Sim...
0
Future consideration