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

Permissions per workflow step / state

XMLWordPrintable

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

      In many situations it would be useful if permissions could vary based on the state an issue is in. The most obvious example is making Closed issues non-editable. Ideally any permission (edit, delete, link, assign etc) should be variable by step, and for some, by transition (eg. assignees).

            [JRASERVER-6381] Permissions per workflow step / state

            Eduardo Santos made changes -
            Link New: This issue was cloned as JRASERVER-78223 [ JRASERVER-78223 ]
            Giles B made changes -
            Remote Link Original: This issue links to "Page (Atlassian Documentation)" [ 344120 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3054816 ] New: JAC Suggestion Workflow 3 [ 3691820 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2606084 ] New: JAC Suggestion Workflow [ 3054816 ]
            Giles B made changes -
            Remote Link New: This issue links to "Page (Atlassian Documentation)" [ 382233 ]

            Dimitar I. Dimitrov added a comment -

            I was happy initially to find this post, but now sad that it was closed as Resolved with actually providing no meaningful resolution to so many of customers demands. In general, one more vote up that you should re-consider this and add to your product roadmaps some flexible and actually effective way to manage user/group relationships. Such a trivial thing should most definitely be part of your core offering, it's not professional to state partial solutions by third party vendors. This is core. If you really are after ITSM markets to challenge leaders like ServiceNow (where this feature has been existing in the core functionalities for years now), you need to make sure the capabilities match.

            Dimitar I. Dimitrov added a comment - I was happy initially to find this post, but now sad that it was closed as Resolved with actually providing no meaningful resolution to so many of customers demands. In general, one more vote up that you should re-consider this and add to your product roadmaps some flexible and actually effective way to manage user/group relationships. Such a trivial thing should most definitely be part of your core offering, it's not professional to state partial solutions by third party vendors. This is core. If you really are after ITSM markets to challenge leaders like ServiceNow (where this feature has been existing in the core functionalities for years now), you need to make sure the capabilities match.
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2590888 ] New: Confluence Workflow - Public Facing v4 [ 2606084 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2352809 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2590888 ]
            Giles B made changes -
            Remote Link New: This issue links to "Page (Atlassian Documentation)" [ 344120 ]
            Giles B made changes -
            Remote Link New: This issue links to "Page (Atlassian Documentation)" [ 343948 ]

              Unassigned Unassigned
              7ee5c68a815f Jeff Turner
              Votes:
              376 Vote for this issue
              Watchers:
              215 Start watching this issue

                Created:
                Updated:
                Resolved: