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

Need a "Transition Issue" permission


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

      Didn't log this as a bug, but some might consider it as such. We gave some external users read-only perms to our JIRA (like jira-users). Discovered shortly thereafter that they were able to transition issues through their workflows. After going through the docs, we began to worry that the only way to prevent this was to put conditions on all of the workflow steps (we have quite a few custom workflows). We confirmed this after talking to support.

      This is onerous in our particular case, as we now need to go thru the process of manually updating all of our workflows to preclude this from happening. However, we think it illustrates an omission in the permission model. We understand that from a technical perspective workflows are managed separately via OSWorkflow. However, from a user/admin use case standpoint. A 'read-only' issue should be just that and there should be a more global way to enforce this (i.e. a "Transition Issues" permission), as saying that 'read-only' users can't do this on every transition step is redundant. The workflow conditions are more appropriate for 'fine-grained' checks like only 'testing' can move through this particular transition.

            Unassigned Unassigned
            3f3652a126e8 Erich Oliphant
            61 Vote for this issue
            47 Start watching this issue