Ability to show idea data based on parent category.
We need ability to show idea data based on high-level category. (ref attached picture) Every week I provide exec summaries to our product leadership who are only interested in data around the product at a high-level view. To accomplish this, I hav...
Laura Giles
almost 4 years ago
in Reports
1
Future consideration
Ability to filter records in the ‘integration updates’ based on a field (eg: categories or tags)
Currently Integration update brings in all new records from Rally project. And there is no way to filter the data before import. Want the ability to filter on some Rally fields (eg. status & tags) which will help to import on the required reco...
Jyothirmayi Talaparthy
over 3 years ago
in Rally
2
Future consideration
New features created via an ADO integration are assigned to the parent epic release by default
Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...
Remove Requirements from custom Feature Card layout
We would like to remove "requirement" from our custom feature layout as this adds "too many layers" to the work. We want to utilize "to do" only within our workspace.
Carolee Snarr
over 3 years ago
in Features
2
Future consideration
Allow scorecards to be inherited from the product line
We have a lot of sub-products in our company, but we'd like to use the same general scorecard, linked to our general product goals, for all of them. It seems that currently scorecards need to be configured for each and every product, which isn't e...
Guest
over 7 years ago
in Product
1
Future consideration
It's currently possible to create a new release in a new workspace that is a copy of a release in another workspace, which will also copy all of the features within that release. If I need to copy a single feature to a new workspace, though, I hav...
Finn Meyer
over 1 year ago
in Features
0
Future consideration
We are a large organization with many users. We would like to share Aha! with interested individuals and that number could be hundreds or thousands. In order to alleviate that, the recommendation is to allow a self registration process that would ...
Guest
about 8 years ago
in Account settings
8
Future consideration