Application
Sort by:
Trending
Status:
Likely to implement
Showing 7746
3
VOTE
Add workspace name as a field on records
What is the challenge? Aha! allows teams to build complex roadmaps with work from across a portfolio contributing to an overarching endeavour. When reporting on the work rolling up, it's necessary to see which workspace that work belongs to. Aha! ...
0
Future consideration
7
VOTE
Teams can inherit delivery risk settings from the team line.
One can set delivery risk settings on the team line but these appear to have no effect. It would be nice to have teams be able to set their delivery risk settings to inherit from their team line, similar to how card customizations are intended to ...
0
Future consideration
35
VOTE
Lock Release and Features
Once we have created a release and scoped all the items into it, it would be helpful if we could "soft lock" the features in that release. A soft lock could be an option on each release with a toggle and a message. Once the toggle is ON and a new ...
6
Unlikely to implement
1
VOTE
Enable integration mapping for custom fields referencing custom tables
What is the challenge? We are using custom tables to define workspace specific values and a corresponding custom field to select the value from a feature. We also have a need to send the value in our integration mapping to Rally. Currently the cus...
0
Future consideration
2
VOTE
Ability to view external links from Record Links reporting
What is the challenge? If you have External Link research concepts, and you bring in those Record Link relationships into a list report or Pivot Table, users cannot access the external link directly from the report. What is the impact? You will ha...
0
Future consideration
3
VOTE
Add portal user created date to export
What is the challenge? There is currently no way to easily see when a particular portal user was added to the system. What is the impact? This can make it difficult to audit portal user lists or determine when a particular individual was added. De...
0
Future consideration
4
VOTE
Change feature rank standard field name
Who would benefit? User utilizing the prioritization page for features, and other record types What impact would it make? Reduce confusion on feature rank vs prioritization rank How should it work? Change the name of the standard field Feature ran...
0
Future consideration
4
VOTE
Automatically resize content when exporting to pdf
Who would benefit? anyone sharing pdfs What impact would it make? lift the barrier for duplicating effort by exporting content to excel then pasting in word docs How should it work? Auto shrink any content to fit to page. When I export an Aha! doc...
3
Future consideration
4
VOTE
Capacity planning for teams: define story point average velocity at the team level
Who would benefit? Teams using story points for team capacity planning What impact would it make? Greater flexibility to accurately define a team's available capacity in story points How should it work? Background: Story point average velocity (to...
0
Future consideration
6
VOTE
Update the Release associated with an Epic or Feature using Automation
We've integrated Aha! Roadmaps and Jira but the release information is not being synced. We can use automation to copy the Epic/Feature Release name to a custom PI field and use the integration to sync the custom PI field with Jira. But when the P...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved