Remove Releases and Features Default fields from layouts
Right now, you can remove custom fields from layouts and HIDE default views. However, when you "hide" them, people can still see them in the records, they just have to click "Show More". This was confusing for us AND Aha staff who tried to figure ...
Megan Sanders
over 4 years ago
in Releases
0
Future consideration
Some of our project teams perform work for product teams where they wish to present their project roadmap to include specific tags on the bars similarly to how these are added to Feature cards (for example)
Guest
over 4 years ago
in Roadmaps
0
Already exists
On the notifications page, it clearly refers to only browser-based and email alerts. However, disabling them turns off in-app alerts. That is a very different thing from browser alerts and caused me to lose a month of notifications in Aha. Should ...
Guest
over 4 years ago
in Account settings
0
Future consideration
Remove Epic as mandatory field while a feature is created.
To create a feature I must link it to an Epic before I can save it, but then I can go back and unlink the Epic. If I can go back and unlink the Epic, then why not allow the user to create a feature without linking it to a specific Epic from the be...
Guest
over 4 years ago
in Features
0
Already exists
Ability to add context to to-do e-mail reminders - for ex: Initiative Name - to-do; Release Name - to-do
Aha! sends out the "consolidated" to-do notifications in e-mails which is a nice functionality. However, as the number of to-dos increase from various goals, initiatives, releases the confusion increases as to which context these are related to. F...
Colour roadmap bars based on simple formula or tag conditions
I would like to create a roadmap where bars are coloured based on a conditional check against tags in a custom field. I use SAFe "Program Increments" as a editable custom tag field and would like to highlight my roadmap based on a condition of tag...
Mark Gerrard
over 4 years ago
in Roadmaps
0
Future consideration
Ability to add specific field from elements like feature (currently only defaults to feature name for example)
When adding other entities like scenarios to a feature, it is useful if we can associate a feature number rather than the feature name which is the default field when you use the many to many table
Arun Kalyanaraman
over 8 years ago
in Features
1
Already exists
Don't change case of customized terms in Terminology
As a Product Manager, I want terms to be displayed a certain way so that it communicates my intent. Instead of "feature", I prefer the "PBI" and "Product Backlog Item". My terms, however, get as "Pbi" and "Product backlog item", respectively. I th...