Ablility to make custom fields mandatory or optional with visibility contraints for a better User experience

it's all about the user experience and would be nice to indicate which fields are mandatory or optional versus only optional. we have to indicate in the help text whether it is mandatory or optional and also use * to indicate mandatory beside the field name

  • Dan Pouliot
  • Sep 7 2017
  • Shipped
Release time frame
  • Sep 12, 2019

    Admin Response

    You can now set required fields when adding new records — so you can bring consistency to how your teams enter data in Aha!

  • Attach files
  • John Seifert commented
    13 Sep 11:49

    I appreciate this new feature.  It is similar to another feature at creation time.  

     

    I think Aha! is missing the point of these types of requests.  Making a field mandatory or optional is not something you want at only create time.   You want this field mandatory when someone goes back to update the record with the custom field.

     

    Consider the following use case.  

     

    Product Managers are now required to add custom data to initiative records.  There are already 40-50 initiatives defines.  So, the new required custom field is added to initiatives.  When The product manager goes to update one of the 40-50 existing initiative, product manager should be  required to update the new required custom field. 

     

    This solution does not address that use case.