Skip to Main Content

Share your product feedback

Status Future consideration
Categories Features
Created by Lindsey L
Created on Sep 23, 2020

Support One-to-Many relationship custom field on create screen

Part of our process for writing features is to essentially create a living document using the feature layout and custom fields. We created a Use Case(s) custom table that we turned into a one-to-many relationship custom field as each feature could have many use cases and the custom table allows us to create a running list in each individual feature. This custom table has multiple columns to be filled out per Use Case to ensure all the details have been captured and documented. In our previous process, this was a required field. Due to the type of this custom field, we are not able to add it to our create screen and make it required. We need the ability for this field to be a required field on our create screen as this is really the "beef" of why this feature is needed. Lastly, Use Cases is not the only one-to-many relationship we have, so there is a need for multiple one-to-many relationships to be available on the create screen as required fields.

  • Attach files
  • Stephen Wingert
    Reply
    |
    Dec 18, 2020

    We have a similar need with Goals. Our teams are moving towards an OKR framework and we'd like to track multiple key results to a single goal (i.e. objective). I'd also like to add the field to the overview of a Goal, so it is front and center to users.

  • Pamela Stephens
    Reply
    |
    Dec 14, 2020

    I agree that this would be a useful feature for our team. We would like to track release dates (we have several different release dates that act as gates for formal rollout) and it'd be handy to track this as a custom table but only if it can be added to the release record layout and set to "required."

  • Jon Ragsdale
    Reply
    |
    Sep 23, 2020

    In order to ensure our requirements/features meet the needs of stakeholders and development teams, we need to ensure required fields are completed. Enabling one to many field types to be required would help accomplish that need.