All ideas
Sort by:
Trending
Status:
Showing 9092
1
VOTE
Keep history of record links being added and removed
What is the challenge? Today there is no history of linking between records. So if a record was linked it's not recorded in both records history. Further if someone removed a link there is no trail either. What is the impact? We use linking to con...
0
Future consideration
2
VOTE
In Ideas portal, flexibility to provide conditional logic wherein dependency exists with an Epic/feature. We are using Ideas for leveraging Dependencies.
What is the challenge? Users create ideas, without there is a proper dependency What is the impact? Data discrepancies, because users omit to include dependencies to other records Describe your idea Allow conditional logic, to make mandatory depen...
1
Already exists
2
VOTE
Epic/Feature boards using custom fields than versions
What is the challenge? Today we are not using Aha! out of box Releases and using a custom field for Release at Enterprise wide. So existing Aha! boards is forcing us to create versions at workspace but ideally we would like to use our custom field...
0
Future consideration
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
© 2024 Aha! Labs Inc.•All rights reserved