Account settings
Sort by:
Trending
Filter by:
Status
Showing 682 of 9570
4
VOTE
Configure different Requirement types
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...
0
Future consideration
80
VOTE
Ability to change label names of Standard fields
In our org. we have 2 roles:
1. Product Manager - Who owns the Idea and is responsible for updating idea status.
2. Category Manager - Who should be informed when the idea is updated (Basically a watcher)
The above 2 roles are similar to what th...
9
Future consideration
13
VOTE
Sort the list of release templates to appear in alphabetical order or set manually
What is the challenge? Large lists of release templates can be difficult to manage and sort. Not having a set list and being able to sort the order alphabetically or manually increases the time it takes to find a release template. This is also the...
0
Future consideration
16
VOTE
Option for workspace template to not override all settings when first applied
What is the challenge? When applying a workspace template, even if the settings are marked as unlocked in the template, once applied to a workspace the existing workspace settings will still be changed. This is not always the desired experience. I...
1
Future consideration
3
VOTE
Support reporting across multiple Aha! accounts
What is the challenge? Large organizations with more than one Aha! account need to be able to report across instances. In some circumstances accounts cannot be easily merged. What is the impact? Ability to create cross account reporting while main...
0
Likely to implement
3
VOTE
Allow admins without a paid license to manage workspace hierarchy
What is the challenge? Some teams have central admins who do not manage work in Aha!, just help configure it for end users. These users have full admin permissions and help administrate the account. This is fine for most settings, but if a customi...
0
Future consideration
74
VOTE
Indicate required fields when editing a record
We need the ability to make standard and custom fields mandatory for existing records.
When a record is being edited, the UI should flag empty required fields so that the user is prompted to update them. This will help us ensure that critical inf...
14
Likely to implement
12
VOTE
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...
2
Future consideration
2
VOTE
2
VOTE
Custom tag values should get applied colors as they do with standard tag values
What is the challenge?
Currently when a user adds a new custom tag value, the color defaults to black for the tag, but for standard tags, they get auto-assigned a color
What is the impact?
An admin must go in and manage new tag values if y...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved