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-9088

Create a workflow validator to require a field on workflow transition

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      A popular feature request is that JIRA should be able to require a field only on a specific transition (JRA-5783). Currently field required'ness is determined by field configurations which are scoped by project/issue type.

      An often suggested workaround is to create a validator which checks if a field is empty, and complains if so. There is even user-contributed code that does the job at:

      http://confluence.atlassian.com/display/JIRAEXT/Workflow+Validator+to+require+a+field+on+a+transition+screen

      Since it's so useful, we should package this properly as a plugin and distribute it with JIRA, as an 80% interim solution.

            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-9088

            Create a workflow validator to require a field on workflow transition

              • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

                A popular feature request is that JIRA should be able to require a field only on a specific transition (JRA-5783). Currently field required'ness is determined by field configurations which are scoped by project/issue type.

                An often suggested workaround is to create a validator which checks if a field is empty, and complains if so. There is even user-contributed code that does the job at:

                http://confluence.atlassian.com/display/JIRAEXT/Workflow+Validator+to+require+a+field+on+a+transition+screen

                Since it's so useful, we should package this properly as a plugin and distribute it with JIRA, as an 80% interim solution.

                        anton@atlassian.com AntonA
                        7ee5c68a815f Jeff Turner
                        Votes:
                        3 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            anton@atlassian.com AntonA
                            7ee5c68a815f Jeff Turner
                            Votes:
                            3 Vote for this issue
                            Watchers:
                            4 Start watching this issue

                              Created:
                              Updated:
                              Resolved: