Skip to content

Handle existing required custom fields #2

@sol1-matt

Description

@sol1-matt

Need to look into how existing custom fields are handled for the following use cases

  • custom fields could need a default value that doesn't come from the source
  • custom fields default value could be a date value that is relative.
  • custom fields could have a existing value that shouldn't be overridden
  • custom fields could be required

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions