Account settings
Sort by:
Recent
Status:
Future consideration
Showing 404
1
VOTE
Override Workspace Template Automations
What is the challenge? We have standard automations needed across a majority of the account with a few exceptions. We would like to disable those that we do not want to be used in certain workspaces. What is the impact? 99% of the time we want wor...
0
Future consideration
1
VOTE
Improve user experience of Idea Category type custom field
We promote Ideas to Epics and automatically populate the Idea Categories field into an Epic field, which calls from the idea categories of our product line. When we try to modify or add categories using the Epic field, we are encountering some iss...
0
Future consideration
2
VOTE
User management: filter for date user was created
What is the challenge? To comply with company policy, user accounts created more than 90 days ago, and never used, need to be disabled. What is the impact? Non-compliance with company policy Describe your idea Add a filter to the Settings > Acc...
0
Future consideration
0
VOTE
Create tags from the bulk edit screen
The Bulk edit screen only allows you to select from existing tags when applying tags to a group of records. When a user wants to add a new tag to multiple records, they first have to edit one of the records individually to create the new tag and t...
0
Future consideration
2
VOTE
Support worksheet custom fields in automated scorecard metrics when an idea is promoted
What is the challenge? I have a worksheet that is used on multiple record types. I want to use that worksheet in an automated metric in a scorecard that is shared across those record types. This is not possible today. When you select multiple reco...
0
Future consideration
2
VOTE
Surface error details when importing users via CSV
What is the challenge? If certain entries in a user import CSV are invalid, Aha! does not process those as part of the import and shows an "Alert" with the failures. It does not identify which line(s) or record(s) in the CSV have the error. What i...
0
Future consideration
1
VOTE
Allow automation rules based on Feature name
What is the challenge? Automation rule triggers are limited, not enough customization. Feature name is a particular use case that would open up a lot of possibilities, especially for teams that use naming standards and conventions. What is the imp...
0
Future consideration
2
VOTE
Customize the term for feature "Type"
What is the challenge? The custom types configured in the features status/workflow configuration display with the field name "Type" on the feature layouts. The "Type" term cannot be customized. What is the impact? The term "Type" doesn't align wit...
0
Future consideration
2
VOTE
Enable custom feature types to apply other records
What is the challenge? The custom types (configured in the features status/workflow) are only available for features. This type categorization is needed for other record types, including epics. What is the impact? The current workaround is to use ...
0
Future consideration
2
VOTE
© 2024 Aha! Labs Inc.•All rights reserved