Skip to Main Content
Status Future consideration
Categories Application
Created by Rich Baldry
Created on Aug 26, 2021

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 template for the Description field of information that individual PMs should be thinking about as they write up the feature.

To help the engineering team understand the parameters, we also have an ‘Acceptance criteria’ custom note-type field that is meant to include functional and non-functional requirements around which the overall feature should be designed, build and tested. Again, we would really like to be able to include a template for this field as a prompt to ensure that teams are considering all the possible areas in which acceptance criteria need to be stated – e.g. Performance, Documentation, Behaviour in different deployment modes, etc.

Finally, for idea submissions we want to prompt our sales teams, and others who are submitting ideas, to provide details on the problem the customer has, how it impacts them, as well as the suggested implementation.

At the moment, it seems the only options are:

  • Placeholder text, which disappears as soon as you start entering text in a field - we need something that stays there as a reminder while they type

  • Breaking out the information into more specific fields, each with their own prompts, which tends to make the data harder to manage, harder to synchronize with JIRA and clutters the forms unnecessarily

A general ability to create a template for any note field, as is already possible for the text area in Note documents, would be really valuable and help us keep some consistency in our descriptions on Features, Initiatives and other areas. This in turn will make it much easier for us to communicate out to other stakeholders.

  • Attach files
  • Jon-Paul Ciambra
    Reply
    |
    Oct 26, 2023

    I agree with this feedback.

    In my situation, distinct fields will not work because I am trying to collect sets of data for reporting requests. For example, when the idea is submitted, users have to indicate 3 pieces of information for each field they are requesting:

    1. Field name
    2. Field description
    3. Field source / location

    If they were only allowed to submit one field at a time, distinct fields would work but would require the end user submit one idea per field which is not a very efficient user experience.

    Thank you for the consideration!