Option to make custom fields mandatory / required

  • Guest
  • Nov 20 2014
  • Shipped
Release time frame 3 months
  • Jun 19, 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
  • Guest commented
    November 26, 2014 13:42

    This would be particularly helpful when trying to drive behaviours in larger organisations with multiple product managers. 

  • Andrew Shopsowitz commented
    August 24, 2015 13:10

    I agree 100% with Howard's comment. This is a massive gap for product management organizations trying to gather feedback as it stops us from making sure we gather the necessary data to make good decisions when deciding what feedback to implement.

  • Michal Anderson commented
    January 28, 2016 19:16

    Is there any update on when this might be implemented?  This is something that is currently driving me crazy with our users entering data.  Not having required fields makes data entry the wild wild west!

  • Guest commented
    March 05, 2016 21:43

    I really need this feature. E.g. I've added a custom field called "Rationale" to Features and I need to make it impossible for anyone to create a new Feature without entering something in the Rationale field. I need to do the same for Ideas.

  • Marissa Melnick commented
    April 05, 2016 05:36

    +1 on wanting to know when this is planned.  it's a huge gap.

  • Guest commented
    May 16, 2016 18:27


  • Andrew Mackles commented
    January 04, 2017 15:44

    Any updates on when this will be implemented? We love the flexibility of Aha and rely heavily on meta data driven reports. For example, we list names of customers when adding user stories. Making the user name field mandatory would ensure the roadmap reports are always accurate. 

  • Srinivasaraju Vysyaraju commented
    March 02, 2017 02:48

    Its extermely important to have this feature to make sure we data filled in by users

  • Guest Guest commented
    April 25, 2017 14:12

    +100. Very important feature.

  • Marco Cara commented
    May 10, 2017 14:42

    Already there for ideas, but missing for the other groups.

  • Smita Dhingra commented
    July 05, 2017 22:37

    +1, Really need this feature.

  • kirk sadler commented
    July 13, 2017 23:32

    +1 --- Wanting to do this now

  • Ruchi Shah commented
    September 21, 2017 06:56

    This feature is very much required, as adding a custom field and not making it mandatory means no one will bother to update the fields.

  • Guest commented
    October 17, 2017 09:02

    We really need this field within Aha, as this would help tackle the issue of Data Integrity!!! At the moment because fields are not mandatory we have individuals who are not filling in certain fields that are a business requirement and due to this we have a high level of data missing. 90% of our time is chasing on missing data!!!

  • Karen Wittenberg commented
    November 27, 2017 17:41

    Definitely needed! Go one step further...be able to designate a field as mandatory/required based on another field. For example, when feature status changes from A to B, then make the Priority field required. Also don't limit this to custom fields.

  • Guest commented
    January 19, 2018 13:15

    Compulsory fields should be a standard function, it forces users to populate areas which are important to a business function, a lack of data from badly populated or unpopulated fields makes it more difficult for teams to plan ahead. Gathering important data from such fields is crucial nowadays.

  • Andrew Barber commented
    February 01, 2018 13:17

    I cant understand why this has not been developed sooner. This will be required by at least 90% of the Aha user base. Would love some feedback on a possible due date.

  • Chris Horne commented
    February 02, 2018 20:54

    Not being able to enforce required fields is adding great complexity to our Jira integration... while introducing the need for heavier process control and data quality checking after the fact. Please support required fields to let your customers decide when they are appropriate to use. As this idea is over three years old, it would be great to get a sense if this is on the roadmap for 2018. Thanks

  • Rebecca Harwood commented
    February 02, 2018 21:20

    Seems like a basic and common functionality. Would really be helpful, especially with large groups. 

  • Alan Valentine commented
    May 15, 2018 10:33

    I need this also!

  • Alan Valentine commented
    May 15, 2018 10:35

    for integrations with JIRA, often send to jira can fail because a custom field may be mandatory in jira, but not in aha, so people may try sending to jira without Aha being able to first ensure that mandatory fields are completed

  • Stuart Jones commented
    May 24, 2018 08:11

    Gimme Gimme Gimme

  • Julie Edwards commented
    July 10, 2018 13:07

    Very much needed.  We use custom fields quite heavily and need to ensure certain key custom fields are populated.

  • Amanda Grant commented
    July 11, 2018 11:13

    We are really keen for this to be implemented - any update on timescales?  there is a request for an update back in 2014 so it seems to have been around a long time?

  • Agnes Muller commented
    July 18, 2018 13:58

    this is critical for us, especially due to the integration with jira which fails because this 

  • Guest commented
    30 Jan 20:31

    Is there an update on this idea?

  • Steve Malpiedi commented
    07 Feb 16:53

    Do we have any update on this?

  • Deepesh Garg commented
    08 Feb 06:23

    This is a must feature Aha should have it ASAP.

  • Charlene Brennan commented
    21 Mar 17:01

    We could definitely make use of this feature to achieve consistent data reporting with over 20 product managers.

  • Julie Edwards commented
    28 Mar 16:30

    Any approximate timescales for this? We desparately need it to help drive data quality and reduce the number of exception reports we need to manage.

  • Jason Trent commented
    02 Apr 22:51

    I have the same Idea as shared with other commenters prevoiusly.  I'm new(ish) to Aha but am REALLY surprised that with all this feedback over a significant period for something that seems to be assumed capability by many Aha users isn't in the Product.

  • Guest commented
    17 Apr 20:38

    @AHA PMs - given how much support there is for this feature and how long people have been asking for it, would be great if you could make this happen soon and if you could give us an ETA.

  • Guest commented
    29 Apr 21:57

    @AHA PMs - Thanks for hearing your users' feedback and the change in status to "Planning to implement". Could you please share a timeline - even which quarter would be helpful. Thanks.

  • Ankar Sawir commented
    29 Apr 22:13

    Surprised this isn't already a feature of Aha! Please provide timeline as this is crucial to using Aha! at scale.

  • Admin
    Nathaniel Collum commented
    30 Apr 14:21

    Thank you for your consistent feedback on this idea! We are actively developing this feature and plan to release it this quarter (next couple of months).

  • Daniel Pokrývka commented
    03 May 10:36

    Absolutely necessary. Will prevent lots of synchronization errors with JIRA when you have mandatory fields. E.g. Country.

  • Donncha Daly commented
    13 May 09:45

    I agree with all that is said here. This is particularly important if, like us, you are planning to integrate with Jira. It would make dealing Jira mandatory fields much easier and less susceptible to error. 

  • Guest commented
    21 May 16:45

    This is effectively a bug. Please fix ASAP.

  • Maciej Kaminski commented
    06 Jun 14:37

    It is very important issue for my team, implementation should happen ASAP.

  • Amanda Grant commented
    19 Jun 14:10

    This it not great if you have been using Aha for a while and created lots of custom fields that we still cant make mandatory....  :-(  - really disappointed.

  • Julie Edwards commented
    19 Jun 14:14

    Our implementation is pretty sophisticated and established. We have a lot of existing custom fields and are unlikely to add (many) new custom fields.  The key requirement for us wasto be able to make existing custom field mandatory - this is the problem we needed solving.

  • Admin
    Nathaniel Collum commented
    19 Jun 15:33

    Thank you for the follow up comments. I believe both comments describe similar use cases, but I would like to confirm. Is the use case that you want to make custom and standard fields on existing records mandatory (i.e. features that have already been created)?

  • Charlene Brennan commented
    19 Jun 15:43

    Yes, we need a way to make the existing custom fields mandatory on all feature records new and existing.

    How soon can you deliver this?


  • Julie Edwards commented
    19 Jun 16:21

    We have existing custom layouts that use a mixture of standard fields and custom fields. We want to make some of the existing custom fields (which are already used on existing custom layouts) mandatory.

    So far it looks as though we need to work around this by creating a new custom layout, re-add all our custom fields, apply mandatory and then request all Product Managers update their product configurations to use the new custom layouts. We have custom layouts for Products, Personas, Competitors, Initiatives, Releases, Master Features, and Features.

    If I have misunderstood anything, please let me know.

  • John Seifert commented
    19 Jun 18:43

    I am echoing others people comments.  I would have expected to be able to flag existing custom fields on a layout as required for existing record types (release, feature...).  I see you can set a custom field as required when a new record type is created.  

    That is ok, but the real need is to have the user update the record with the required fields.   



  • Deepesh Garg commented
    20 Jun 05:36

    This is half implementation only, it's implemented only on create screen but later anyone can remove that mandatory field from feature. Ideally all mandatory fields should only have option to edit but not to remove.

  • Admin
    Nathaniel Collum commented
    20 Jun 19:42

    Thank you for the follow up and clarification here.

    This week’s release introduced required fields for record creation. As you move forward and collect key data, this allows you set required fields and to create more consistency to how your teams enter data in Aha! moving forward.

    Some recent comments asked for the ability to make these fields required in the viewing and editing experience — particularly for existing records. This was not an area of focus for this release. While we see the benefit of capturing this data in this view, this would have a very negative impact on usability in the application.

    That said, we would like to continue to monitor feedback in this area. We have created a new idea to track this request here: https://big.ideas.aha.io/ideas/A-I-7817. Please vote on that idea and comment with any specific use case (or user flow) that you’d like to be considered.

  • Mark Taylor commented
    20 Jun 20:28

    Hang on. So to confirm, fields are now mandatory (if you set them to be) on creation but on edit you can remove data and they not mandatory anymore? That’s ridiculous, that’s very non standard behaviour.