IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
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.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            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

              • Icon: Bug Bug
              • Resolution: Duplicate
              • Icon: Medium Medium
              • None
              • 3.6.3
              • Issue - Fields
              • Standalone, Fedora Core 5, JDK 1.5

                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.

                        Unassigned Unassigned
                        b123315b970f Allen Rohner
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

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

                              Created:
                              Updated:
                              Resolved: