All ideas
Sort by:
Trending
Status:
Showing 9122
2
VOTE
Allow Jira-related fields to be included in automation rules
It would be helpful for fields like the Jira key or integration link to be available in automation rules. That would enable my team to create triggers that look at when an integration link is changed or is no longer available.
0
Future consideration
2
VOTE
Allow for null Release Date
Currently the release date field is required. But usually when a release is first written up there is no realistic idea for when it might be delivered. For releases that are postponed or of lower priority, the initial entered dates which seemed so...
0
Future consideration
1
VOTE
Provide "Confidential" as a watermark on printed/pdf roadmaps
We wanted to send a pdf copy of the strategic roadmap to a partner however it would be nice to put a watermark on it so we can identify it's confidential. As a stretch if we could even customize it then we could put the partner's name on it.
0
Future consideration
1
VOTE
Promote a requirement as "is a dependency of" instead "Relates to"
Sometimes a requirement needs to be done one sprint before the related feature. So we need to promote it as a feature. The relationship between the new feature and the previous one is created as RELATES TO. This is a problem, as Gantt chart shows ...
0
Future consideration
4
VOTE
Feature effort estimate total instead of capacity on Features board
If a release doesn't have a capacity entered, instead of just showing "n/a", i would like to see the total of the estimates for the features in that release.
Extra points: Enable a velocity chart on the feature board. Perhaps a chart can be hacke...
0
Unlikely to implement
4
VOTE
1
VOTE
Allow link of a requirement to a release (sprint)
We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which i...
0
Future consideration
1
VOTE
Promote Notes OR To Dos to Feature
We are trying to bring our Cross functional partners into Aha and would like a way to easily request work from them. We had been copying our Feature and assigning the UX-specific Feature to them. This allows for the details from the Product Develo...
0
Future consideration
2
VOTE
Sync Sprints betweeen Aha! and Rally
As product owners use Aha as the primary repository to develop and track their roadmap, they want to enhance their planning phase by improving the existing configuration between Aha and Rally. Currently, capabilities, features, and user stories ar...
0
Future consideration
2
VOTE
Allow child releases for a master release to retain unique names
There are instances where multiple releases exist within the same product workspace that are separated intentionally for visual management. Creating a rollup release causes the children to inherit the parents name, but it would be useful for the c...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved