Hi there, is it possible to configure the names of roles in Aha! Calling the system admin role "Product Owner" is a really issue for us internally - we have product owners by they're relatively junior... Myself (senior product manager) and my boss...
Suzanne Vaughan
over 9 years ago
in
1
Will not implement
Keep webhook URL the same when updating custom domain
I recently updated the custom domain on my account. What I didn't realize is that this would also update the URL to my webhook for the JIRA integration, and ultimately cause the JIRA -> Aha! push to stop working. To avoid this in the future, I ...
The billing page displays all invoices, it seems logical that a payment status column should be added so that the page displays the invoice number, date, amount and status. It would help admin users ensure there are not lingering overdue invoices ...
Danny Archer
over 7 years ago
in Account settings
0
Will not implement
The diagram view is really great but white on gray background is not always so readable, so it would be great if the color & font size could be changed.
Andreas Lauringer
over 5 years ago
in Reports
1
Will not implement
Visualize connections between products or product lines and custom fields and custom field layouts
There are many ways to configure the custom fields and custom field layouts for a product. They can be inherited from the product line or setup locally for the product.
It is easy to get lost and make mistakes when configuring this. A graphical vi...
Kenneth Palm
over 7 years ago
in Account settings
1
Will not implement
Ability to bulk edit areas of the customization area. For instance, in the configure status, workflows, and feature types areas, it would be beneficial to be able to select multiple flows at once in order to clean things up quickly.
Idea: Ability to custom remove to-do functionality from features, releases, etc. Use Case: Users sometimes add to-dos instead of requirements. To-dos are nearly impossible to track at a project level unless you are the assignee.
Calli Phillips
almost 6 years ago
in
0
Will not implement
Documentation on all standard fields supplied by Aha! on all record types.
As a new developer working to customize Aha! I would like to see documentation on all standard fields supplied by Aha! including a definition on usage, field type, whether it is required or not and what record(s) the field is used for so that I un...
Deb kelchner
almost 4 years ago
in Application
3
Will not implement
API - support sending multiple parameters/values in search query
The API currently only accepts a single value search parameter. There is a requirement to be able to pass multiple parameters/values through the API. For example, execute a search through the API for features that contain 3 specific tag values.
Matt Case
almost 8 years ago
in Integrations
1
Will not implement