Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-10847

Fields marked required are required on screens that don't provide them

      When a custom field which is not present on the create issue screen is marked required, new defects cannot be created. When attempting to create the defect, it is rejected with the message "<your custom field> is required"

      I have created a custom field, called reviewer, which is only present on the resolve screen. In the field configuration, the reviewer is marked required. Now when attempting to create a defect, the defect is rejected because the reviewer is not present, but the reviewer field is not present on the create screen. The check for the field being required should only happen on screens that contain the custom field.

            [JRASERVER-10847] Fields marked required are required on screens that don't provide them

            tracking this on validation is a lot of maintenance for a admin as you have to set this on each workflow.  Why is it that the field is required on a screen where the field is not on?  Why can't you only require it if it is on that screen?  When we are trying to do this at an enterprise level while allowing teams to have different workflows, this is a lot to set up and maintain.  So if we want a bug and a story to have the same workflow within a project (but workflows are different for each team or project), but we want field A to be required on the bug when it is configured for a screen, we have to update each workflow even though it isn't on the Story screen.  Why can't we just make it required and it will be requried for a bug because it is on that screen but not a story because it is not on that screen?

            Stacie Smith added a comment - tracking this on validation is a lot of maintenance for a admin as you have to set this on each workflow.  Why is it that the field is required on a screen where the field is not on?  Why can't you only require it if it is on that screen?  When we are trying to do this at an enterprise level while allowing teams to have different workflows, this is a lot to set up and maintain.  So if we want a bug and a story to have the same workflow within a project (but workflows are different for each team or project), but we want field A to be required on the bug when it is configured for a screen, we have to update each workflow even though it isn't on the Story screen.  Why can't we just make it required and it will be requried for a bug because it is on that screen but not a story because it is not on that screen?

            Hi Allen,

            We are tracking this at JRA-5783.
            The current workaround is to make the field not required and have a custom Workflow Validator that checks to see if the value is on that screen.

            Cheers,
            Nick

            Nick Menere [Atlassian] (Inactive) added a comment - Hi Allen, We are tracking this at JRA-5783 . The current workaround is to make the field not required and have a custom Workflow Validator that checks to see if the value is on that screen. Cheers, Nick

              Unassigned Unassigned
              b123315b970f Allen Rohner
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: