Custom Required Field for Features and Requirements

It seems that only custom fields for Ideas can be flagged as Required Fields.  I would like to be able to specify custom fields for features and requirements to also be required.  For example, I integrate requirements with TFS as backlog items.  (Features go as Features).  I want each requirement to include Type as Bug or Product Backlog Item because these are the two types of backlog items I have define in TFS.  I don't have many bugs start in Aha! but it happens and I want to push them into TFS as a bug work item.  If left blank, the TFS item will be a PBI.  

An alternative approach is to set a default value on a custom field.  That way, it at least defaults to something and is less likely to be left blanks.

  • Tom Beck
  • Mar 1 2018
  • Future consideration
Release time frame
  • Attach files
  • Charlene Brennan commented
    July 19, 2018 15:06

    This would really help with data standardization and reporting.

  • Larry Heminger commented
    October 01, 2018 22:33

    Really need this so I don't have orphaned features without my custom fields 

  • Sam commented
    December 03, 2018 17:52

    I would just like the ability to mark a custom field on a feature as required. It seems weird that I can mark a custom field on an Idea as required but not on a feature.

  • James Taylor commented
    December 20, 2018 17:29

    I'm piloting an integration with our Dev workflow tool and am having to get very creative using 'constant' field mappings ensure that synchs fail unnoticed. Would be super helpful to have A: Required fields and B: Default selections as Tom Suggests. 

  • James Taylor commented
    December 20, 2018 17:30

    sorry, *don't fail unnoticed...

  • Steve Podzamsky commented
    June 27, 2019 19:26

    Make sure the custom fields can be set in the new release when copying a release and all of it's features. right now that is not happening and it has caused me to not use the required fields in the release.