All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5666
2
VOTE
When cloning, please provide ability to clear values in custom fields before saving in Domain Epics/Epics
What is the challenge? User clone records, without cleaning the existing data that is not applicable for the new record. What is the impact? Data consistency and re-work Describe your idea Have an option, when cloning to reset all the other attrib...
0
Future consideration
6
VOTE
Easily share relevant research documents on features through integration
What is the challenge? With the Research tab, many teams are creating documents to contain their research, technical requirements, and wireframes. But once I send a feature into Jira, I cannot pass along the relevant documents I want my engineerin...
0
Future consideration
30
VOTE
Allow automations to run on any custom field
Not just the fields present in your epic/release/feature/idea template. I have flows for each of these record types that add new fields for input later on and would like to run automations on them, but can't unless I add them to the template used ...
1
Future consideration
50
VOTE
Support "NULL" checks for calculated columns
When you are using calculated columns, and want to check if a 'value type' field such as a date is null, there isn't a clean way of comparing the value to null. For example: If a date is blank, return "Not set", else return the date formatted as a...
3
Future consideration
75
VOTE
Unique field layout based on feature type
As we continue to expand our use of Aha, one issue that has come up is that within a given product, there are different types of work/requirements that require different types of information. We're adding more and more custom fields, and it's star...
8
Future consideration
29
VOTE
Require completion of certain fields with promoted ideas
Epic, feature and initiative layouts allow you to require certain inputs when these records are created in the platform. But if they are promoted from an ideas, portal, individuals are able to bypass the completion of these 'required' fields.
4
Future consideration
5
VOTE
Knowledge base page publishes automatically once approved
What is the challenge? We want KB pages to be approved before they are published. What is the impact? It is a manual process right now and we have to trust users that they will not publish a page before all the approvals have been given. Describe ...
2
Future consideration
2
VOTE
Keep formatting from a Jira table
What is the challenge? The Jira integration does not currently support the table markdown syntax What is the impact? The result is a formatting issues when a record including a table within the description is synced to Aha! via the integration Des...
0
Future consideration
3
VOTE
45
VOTE
Risk identification and tracking
I appreciate the recent release of the Project workspace. However, a big part of Project Management is Risk Tracking and Mitigation. I would like to be able to identify risks at a Project or Product line level and tag those risks on Release and Fe...
5
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved