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

Transition end-point can be "Self" as well as a specific state

XMLWordPrintable

    • 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.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      In order to allow users to edit only a subset of fields without transitioning to another state, it is common to create a transition which has the same starting and ending state. This transition's purpose is primarily to provide a screen with exactly the fields which this particular user should be allowed to modify at this point (e.g. the reporter of an issue should be allowed to change the summary and priority of an issue at any time, but not the assignee or fix version)

      Without this feature, if the same functionality is desired at multiple states, individual transitions will have to be created. If there are any conditions, validations or post-functions those will have to be manually kept in synch.

      With this feature, a single common transition could be re-used across multiple states.

            [JRASERVER-26885] Transition end-point can be "Self" as well as a specific state

              Unassigned Unassigned
              6e097471c47b Doug Gray
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: