Option to make custom fields mandatory / required

  • Guest
  • Nov 20 2014
  • Future consideration
Release time frame
  • 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

    +1

  • 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
    19 Jan 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
    01 Feb 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
    02 Feb 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
    02 Feb 21:20

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

  • Alan Valentine commented
    15 May 10:33

    I need this also!

  • Alan Valentine commented
    15 May 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
    24 May 08:11

    Gimme Gimme Gimme

  • Julie Edwards commented
    10 Jul 13:07

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

  • Amanda Grant commented
    11 Jul 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
    18 Jul 13:58

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