All ideas
Sort by:
Trending
Status:
Showing 9092
93
VOTE
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
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
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
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
56
VOTE
Expand/Collapse Release View to include Requirements
It's critical for our teams to see Features AND Requirements on the Release (Overview/Details View). You should be able to continue expanding down the hierarchy from Epic > Release > Feature > Requirement all within the Gantt.
7
Future consideration
3
VOTE
© 2024 Aha! Labs Inc.•All rights reserved