As a user of Aha! I would like to be able to search account audit/history to determine who/when made a change to a custom field. Right now custom list fields are not searchable via the audit.
Tom Bailey
about 2 years ago
in Application
1
Future consideration
Restrict broadcast messages to specific Product Line(s)
In our large organization, we have three top-level Product Lines to represent each corporate division. Some broadcast messages are useful for the entire organization, but others would be more meaningful if they were visible to users of a specific ...
Who would benefit? Product Managers, Product Owners, Program Managers, Project Managers, anyone concerned about governance What impact would it make? This would allow workspace Owners to draw other users' attention to built-in, optional fields (e....
David I.
12 months ago
in Application
0
Future consideration
Support One-to-Many relationship custom field on create screen
Part of our process for writing features is to essentially create a living document using the feature layout and custom fields. We created a Use Case(s) custom table that we turned into a one-to-many relationship custom field as each feature could...
Lindsey L
about 4 years ago
in Features
3
Future consideration
as a user, I want to be able to view item history... when item history is long and cluttered, it would be helpful to see just a subset of events in the history log... when I am trying to find a particular event.
e.g. Filter to exclude API/inte...
Guest
over 6 years ago
in Features
2
Future consideration
As a PO my view of the work has a farther horizon than the dev team. To sketch a plan, using the capacity tools, I need a way to put in an initial estimate of the work. This is a tactic I've used for years and call a PO Estimate, and after a certa...
Aaron Kremin
almost 6 years ago
in Features
2
Future consideration
Allows much easier to iterate, more standard, and simpler to follow along version of diagrams/charts within documentation. GitHub and Notion have recently adopted the same library (mermaid) allowing for standardization across tooling.
Barnett Klane
over 2 years ago
in Development
0
Future consideration
Automation Rules are incredibly powerful but are limited to a very small subset of standard fields per item (ideas, epics, features, initiatives, etc.). We're constantly finding ourselves wish that a standard field would exist so that we can creat...
Conner Helton
over 1 year ago
in Epic
1
Future consideration