All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5643
4
VOTE
2
VOTE
Ability to "hide" completed To-Do's on a record
Who would benefit? Eveyyone that uses To-Do's heavily. What impact would it make? Easily be able to see just what is left to be completed. How should it work? Similar to the Status filter on the related tab views. Have the ability to filter by the...
0
Future consideration
2
VOTE
Warn user of integration on epic deletion
Who would benefit? Integration users What impact would it make? How should it work? When you delete a feature which is linked to a dev system you get a warning (attached). When you delete an epic, you do not get a consitent warning. This suggestio...
0
Future consideration
2
VOTE
Group Level integration in Aha.
Who would benefit? All the teams who are using aha and Gitlab setup for their SAFe ways of working What impact would it make? Streamlined and logical grouping of features which are created in aha and synced to Gitlab How should it work? Group leve...
0
Future consideration
4
VOTE
Make the terminology around "Organization" customisable
Across most of Aha! you are able to re-name key items, such as Objectives, Epics, Ideas etc... this is great as it helps you align to the terminology used inside your company. It is not currently possible to do this for Organizations. I believe it...
0
Future consideration
11
VOTE
Ability to create pre-populated custom fields
Our Use Case
We have a process that we've actually implemented as a product within Aha! that helps us track Change Requests. We set it up as a separate product within Aha! because this process has a different workflow that we wanted to capture, in...
0
Future consideration
9
VOTE
The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.
Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...
1
Future consideration
1
VOTE
Auto disable Users when their Okta account is disabled
What is the challenge? When users leave the company and their Okta accounts are disable, their Aha user accounts remain active What is the impact? This impacts our available user license count in Aha Describe your idea Improve the Okta integration...
0
Future consideration
2
VOTE
3
VOTE
Allow editing the layout of Related tab
In addition to being able to edit the layout of the Overview tab, it would be helpful to be able to specify what information shows on the Related tab. As an example, it would be good to see the sprint or story points associated with each feature i...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved