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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
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
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
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
© 2024 Aha! Labs Inc.•All rights reserved
We include a whiteboard template similar to the Product Positioning template as a custom field in our release record. Today, PMs need to go looking for the template, but it would be very helpful if the custom field just opened the designated template. The benefit of this is that we include the custom field in the information displayed on our external roadmap when the user clicks on a release, so she can get more details about the product strategy on a consistent, one-page overview.
This would be hugely beneficial and is a necessity for us to ensure we get good quality information from our various teams.
We want to ideally insert a grid within a custom field to help our team fill out the right level of information when creating a new issue type ticket or an idea.
This should be within a specific custom/existing field, and not need us to create multiple custom fields to capture that information.
Eg. One of our custom fields is: 'Why do you want to make this change?'
Within that field, we then want them to fill in details around the benefits to team/customers, current challenge, who it's for, what the cost/time saving it would bring etc.
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.