All ideas
Sort by:
Trending
Status:
Future consideration
Showing 6231
6
VOTE
Autofit dashboard panel content to panel size
I have created a dashboard that looks great on my big monitor, but when viewed on a smaller screen (like a laptop monitor), the pivot columns are cut off, and charts are unexpectedly cropped. Ideally, there would be an option to autosize the panel...
0
Future consideration
65
VOTE
Updating of Feature 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
18
VOTE
Apply workspace templates to lines
Often settings like layouts, terminology, and navigation for parent lines may be purposefully different than workspaces. It would be helpful to drive standards for lines by allowing templates to be applied at those hierarchy levels. A few examples...
0
Future consideration
1
VOTE
1
VOTE
Add ability to add conditions to automatic actions
What is the challenge? Currently you are only able to add conditions to the trigger. Sometimes when creating automations, there is a desire to add conditions to the actions themselves. What is the impact? This would allow automations to be signifi...
1
Future consideration
8
VOTE
Automated Rule for License from Owner/Contributor to Reviewer/Viewer
I would like to explore if Aha can provide that automation wherein if Admin users like owner/Contributor who have not contributed to Aha in the last 1 month or so (which can be configured) and downgrade the same to Reviewer/Viewer so that those li...
1
Future consideration
29
VOTE
Restrict the visibility of specific custom fields to different users
We use Aha! for all our product planning, however we currently do some financial estimates outside of Aha! which we don't want to share with the wider development team. This causes us to fragment our data and use permissions in other portals as th...
7
Future consideration
15
VOTE
Pass data in shared fields between objects through linked objects
We would like data to be passed using shared fields across objects the same way promoted objects work. Today, if a field (e.g UCMGID) exists with same API key in IDeas, Features, Epics etc, that data will be passed when the Idea is promoted. What ...
0
Future consideration
19
VOTE
Change the roadmap time scale to Sprints (for all Agile teams)
Hi Aha! Team, as an organization we use Aha! together with Azure DevOps (both integrated) in order to track the progress and delivery of initiatives. As we work in an Agile environment, our roadmaps are usually built on a Sprint basis (e.g. Initia...
1
Future consideration
55
VOTE
Configurable destination of imported features
As a product manager, I should have control over the destination of where imported features and epics go so that they are in the release or parking lot where they belong. Today, the destination of imported items seems almost up to chance although ...
9
Future consideration