Paid seat groups are useful for managing the assignment of seats to Roadmaps users. It would be great if this could be extended to support the assignment of Develop seats as well.
What is the challenge? There is no visibility in Aha! what issue type the Requirement is in Aha!. In addition, we'd like to create Design tasks in Aha! which don't require sync to Jira, whereas we'd like to sync Backlog Items, Activities, and Bugs...
Manuel Froehlich
about 1 year ago
in Account settingsFuture consideration
What is the challenge?
Currently, a field cannot be required based on the value of another field. A few example use cases:
If field A is selecting a Category from a dropdown menu: "User Experience", "Performance", or "Security," then field B w...
Enable automatic workflow syncing for custom status categories
What is the challenge?
Currently, automatic workflow syncing between records only works with the built-in status categories.
Teams that create custom status categories to better reflect their workflow stages cannot leverage automatic status sync...
Krysta Boyer
5 months ago
in Account settingsFuture consideration
Delivery Risks - Ability to Inherent to Child Workspace
What is the challenge? If one product line (parent workspace) wants to implement Delivery Risks, we would need to individually go through the settings on each child workspace to configure. What is the impact? It is very time consuming for large pr...
Manny Pannu
almost 2 years ago
in Account settingsFuture consideration
What is the challenge?
As an admin I would like to disable notifications for a batch of users which I am importing via CSV.
What is the impact?
Because I cannot filter by created date there is no way for me to filter to just these users.
...
When working with Aha! customers, one part that slows down users as they set up their account is figuring out how to navigate through to the page they need. Let's say I am helping a customer add a custom layout and statuses to their ideas and idea...
Max Robbins
almost 2 years ago
in Account settingsFuture consideration
Allow to define the scope of tags/choice list custom field values (account vs. workspace)
It should be possible to define whether the values of choice list and tags custom fields (predefined or editable) are shared at account level (current behavior) or limited to workspace level such that workspaces can share a configuration but have ...
Thierry Loones
about 3 years ago
in Account settingsFuture consideration
What is the challenge?
When you have multiple approvers depending on different conditions everyone received the same message
What is the impact?
Multiple users receive approval requests that might not apply to them. It causes confusion and...
Edgar Holguin
10 months ago
in Account settingsFuture consideration