RELATED IDEAS
Custom field templates rather than placeholders
We would like to see the ability to define a template for a custom field description rather than the placeholder which is there now (when editting the field, you see the placeholder, but it disappears once you start editting.
Since there are no templates for initiatives or master features, this would enable us to have a custom field where we could then ask for targetted inputs about the initiative in a requirements custom field, as an example. Asking the user to remember the 12 things that maybe in the placeholder is not sustainable or consistent enough.
4
MERGED
Template values for all (built-in and custom) note-type fields
As we’ve been adopting Aha we’ve also been trying to standardize on ways of expressing the problem that we’re trying to solve with a feature request and the parameters around that. To do this consistently we want to be able to provide a standard t...
1
Future consideration
1
MERGED
Allow Automation for Adding a Custom Template to a Field
What is the challenge? Must manually add custom templates to custom fields for each Epic/Feature created What is the impact? Extra unnecessary steps Describe your idea Allow automation for adding a custom template to a custom note field. For examp...
0
Future consideration
13
MERGED
Ability to create pre-populated custom fields
Our Use Case
We have a process that we've actually implemented as a product within Aha! that helps us track Change Requests. We set it up as a separate product within Aha! because this process has a different workflow that we wanted to capture, in...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved
We have the exact same "Acceptance criteria" field that Rich who submitted the Idea is looking to apply a template to for completion by the user. As we are rolling out a new standard process and configurations across all of our teams it would be extremely helpful to have this functionality.
We have a custom field called 'Acceptance criteria' where details about feature behaviour should be filled out. This avoids the 'Description' becoming too dense and detailed. We would like to put in some reminders about the kinds of criteria that should be considered - e.g. Performance, Telemetry, Licensing, Third-party software/code, etc. Not all headings are relevant to all features and creating a separate field for each area would be unwieldy. This simple solution would have a huge positive impact.