Skip to Main Content
104 VOTE
Status Shipped
Categories Features
Created by Guest
Created on Sep 12, 2015

Set default field values for custom fields at the product level

We have a standard set of custom fields that we are inheriting across all products.  This ensure data consistency on how we describe features.  However for some products the field can be defaulted; For example we may have a product that has a feature that we have contractually committed to; so we have a field YES/NO.  However for another product it's less important and can always be NO.  Rather than set up custom fields for each product we love the inheritance but we want different default behavior so we can drive consistency of information to help reporting... Blanks are pains... 

  • ADMIN RESPONSE
    Jul 22, 2022

    We are excited to announce a new automation capability for Enterprise+ customers.

    Automation rules are configured per product and can be used to streamline a variety of tasks in Aha!, including setting field values when a record is created.

    Learn more and get started!

  • Attach files
  • Patrick Taylor
    Reply
    |
    Jan 24, 2020

    Still being considered?  This shouldn't be a big development task for what some would call 'table-stakes'... (not me, hate that phrase).  But would be / should be a quick win.

  • Dan Jeffery
    Reply
    |
    Nov 8, 2019

    Any news on this please? We are integrating with Azure DevOps (ADO) and have a number of custom fields set to receive information from ADO. We want to make these read only in Aha so they cannot be changed.

  • Guest
    Reply
    |
    Aug 27, 2019

    Hi Folks!

     

    My Team's Request

    • Eliminate or mitigate the need to manually set a certain field for every aha card on every roadmap

     

    Details:

    • My team uses many Aha Products / Roadmaps - these all connect to a Jira Project (around 20 at the moment)
    • We have a field that is used across all cards / tickets that sends / syncs between Aha and Jira (two way sync in Jira 2.0 with "Tags" type field)
      • Every Card that originates from Aha Product / Roadmap A has field=[tag1]
      • Every Card that originates from Aha Product Roadmap B has field=[tag2],[tag3]
      • ...
      • Every Card that originates from Aha Product Roadmap N has field=[tag3]  and so on
    • Other considerations:
      • Each Card could support additional tags as needed
      • Each Card could need to exclude a tag for extenuating circumstances (rare)
      • Each Card could need to create a new tag for new reasons

     

    Current Solution paths:

    1. Manually set this field for every new card created on a given Aha Product / Roadmap
    2. Bulk set this field for all historical cards / any missed cards (have not tested, but expecting this to be the case)
    3. Manually check once a week / once a month that no tags on a given Product are missing - if they are, use item 1 or 2 above.

     

    Ideal Solution path:

    • For a given Product, allow a definition of preset custom field values as needed
    • Allow a toggle for "editable" or "not editable" (nice to have, but at a minimum, would need it to be editable)

    Note - we would not be able to support this on a layout level - we have a layout shared across products, but the products need the separate defaults defined.

     

    Thanks so much!

  • Deanne Branham
    Reply
    |
    Aug 2, 2019

    Need the ability to set the default fields especially in integration with Jira.. We have a user field that Jira sets to None if it is not filled in.  We need to do the same in Aha so that if that field is not intentionally set, we can all be in alignment.

  • Hannah Jackson
    Reply
    |
    Jul 12, 2019

    This would be super helpful in idea portal/forms as well.  

  • Guest
    Reply
    |
    Nov 26, 2018

    This is really important for syncing between JIRA & Aha as well because you can set the requirement in JIRA. It then rejects it bc Aha has no default value but JIRA needs the default.

  • Guest
    Reply
    |
    Oct 14, 2018

    Not sure if I am the original Michael Anderson or not, but I still really really really want/need this feature. Blanks are terrible!

  • Tom Gimpel
    Reply
    |
    Sep 7, 2018

    adding my vote. A default field value seems pretty obvious

  • Guest
    Reply
    |
    Aug 17, 2018

    Can't believe this isn't in the product

  • Brian Cunningham
    Reply
    |
    Aug 16, 2018

    The inability to be able to set the default value to any value other than blank/null, is causing us to create a non-intuitive setup for our global community of users. This design is creating extra work for us with training and will almost certainly lead to some confusion, misunderstandings, etc. Adding the ability to choose a default value, blank or some other value, will not only make data entry more intuitive but it will also make the filtering of the data simpler, and more intuitive, within Aha.

  • Lindsay Hanrahan
    Reply
    |
    Jun 19, 2018

    We really need this.  It is driving our teams crazy, especially with certain fields we are trying to "set and forget" before they go over to VSTS.  We are having to build in additional layers of admin staff checking to confirm that these values are populated.

  • Kai Schröder
    Reply
    |
    Apr 11, 2018

    This would really help!

  • Shri Iyer
    Reply
    |
    Jan 31, 2017

    Setting default values for custom fields at both the feature and requirement level is extremely important. We have to manually go and assign the value currently which is painful. Sometimes people forget and this then shows up in reports with no value. Please prioritize this.

  • Guest
    Reply
    |
    May 30, 2016

    Agreed - especially helpful in integrating with JIRA... certain fields in JIRA that are required, but from a product point of view need never change. 

  • Joe Carpenter
    Reply
    |
    Mar 16, 2016

    Voting this one up.  It's SUPER important especially given the inability for the report filtering to pick up on null values.  
    For us, we also are marking certain Products with 'Yes' and the assumption is that if it isn't marked 'YES' then it means no.  From an Aha perspective though, I can't set up a report to filter on the field such that is follows the logic "Show All records where (field) is NOT 'Yes'

    Thus, I need to go back to all the records, create a specific 'No' entry for that custom field, and edit ALL of the products.  Going forward, the field should always DEFAULTto NO, unless someone specifically changes it.
    Capeche?

  • Marissa Melnick
    Reply
    |
    Feb 18, 2016

    Agree with Michael Anderson!  Just need the option to set a default value for custom fields!

  • Guest
    Reply
    |
    Jan 18, 2016

    The sheer abaility to just set a default value on a custom field is what I need.  Blanks are really a buzz kill!!

  • +4
44 MERGED

Allow selection of a controlled list entry (within custom fields) to populate as default

Merged
For each product line, I need to input a GTM owner, Platform owner etc...I want this to pre-populate based upon the respective product.
Guest over 9 years ago in Releases 0 Shipped
35 MERGED

Ability to initialize a custom field with a default value

Merged
No description provided
Guest almost 7 years ago in Account settings 0 Shipped
32 MERGED

As a user, I need to have a provision to set a default value to any custom field created

Merged
Custom fields are generally created to accommodate value coming in from different application (mainly through integration). However, nobody can be certain about when will get updated. So, if this field is already referred in reports, it will help ...
Guest over 6 years ago in Features 0 Shipped