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

Need a "Transition Issue" permission

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.

      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.

            [JRASERVER-11564] Need a "Transition Issue" permission

            Oswaldo Hernandez (Inactive) added a comment -

            No I haven't heard anything like this before mlassau :/

            jmroth Could you please raise a support ticket at https://support.atlassian.com as suggested by Mark so we can investigate further?

            Thanks in advance.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - No I haven't heard anything like this before mlassau :/ jmroth Could you please raise a support ticket at https://support.atlassian.com as suggested by Mark so we can investigate further? Thanks in advance. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            Mark Lassau (Inactive) added a comment -

            jmroth
            Please raise a support ticket if this is continuing to give you trouble.

            ohernandez@atlassian.com - have you heard any other reports of this?
            If not, I would guess it may be something specific to the customer ...

            Mark Lassau (Inactive) added a comment - jmroth Please raise a support ticket if this is continuing to give you trouble. ohernandez@atlassian.com - have you heard any other reports of this? If not, I would guess it may be something specific to the customer ...

            JM R. added a comment -

            It seems that when upgrading from Jira 5 to 6.4, permissions were not copied as described above, hence users could no longer resolve, close, ... any issues. Is this a known bug?

            JM R. added a comment - It seems that when upgrading from Jira 5 to 6.4, permissions were not copied as described above, hence users could no longer resolve, close, ... any issues. Is this a known bug?

            Mark Lassau (Inactive) added a comment -

            The default assignment for "Transititon issues" in my OnDemand instance was "Project Role (Users)" and "Project Role (Developers)".

            Upon upgrade to JIRA 6.3, the system will initially be configured to give you exactly the same behaviour you were seeing on 6.2 (or earlier).
            That is, it will copy the permission settings from "Browse Project" into the new "Transition Issue" permission.

            You can then adjust this to suit.

            Mark Lassau (Inactive) added a comment - The default assignment for "Transititon issues" in my OnDemand instance was "Project Role (Users)" and "Project Role (Developers)". Upon upgrade to JIRA 6.3, the system will initially be configured to give you exactly the same behaviour you were seeing on 6.2 (or earlier). That is, it will copy the permission settings from "Browse Project" into the new "Transition Issue" permission. You can then adjust this to suit.

            sladey added a comment -

            pmondor, Jens has the right of it. We will be releasing JIRA 6.3 to our download customers soon and it will include this change. There are early access versions of 6.3 available if you are interested - https://www.atlassian.com/software/jira/download-eap

            sladey added a comment - pmondor , Jens has the right of it. We will be releasing JIRA 6.3 to our download customers soon and it will include this change. There are early access versions of 6.3 available if you are interested - https://www.atlassian.com/software/jira/download-eap

            Patrice Mondor added a comment -

            thank you @Jens Bannmann . I'll keep looking at the release notes.

            Patrice Mondor added a comment - thank you @Jens Bannmann . I'll keep looking at the release notes.

            Jens Bannmann added a comment -

            pmondor: as a customer using Atlassian OnDemand, I can tell you that they simply added a "Transition issues" project permission. Just as the existing permissions, by editing the permission scheme, this permission can be assigned to groups, users etc. The default assignment for "Transititon issues" in my OnDemand instance was "Project Role (Users)" and "Project Role (Developers)". When I noticed the new feature, I simply deleted the "Project Role (Users)" assignment from that permission and then went on to remove all the conditions in the individual transitions.

            Way to go, Atlassian! Thank you very much.

            As to when it will be available for download customers: it went live for 6.3-OD, so according to Atlassian docs you guys should get it as part of 6.3. Don't take my word, though, I'm just a customer.

            Jens Bannmann added a comment - pmondor : as a customer using Atlassian OnDemand, I can tell you that they simply added a "Transition issues" project permission. Just as the existing permissions, by editing the permission scheme, this permission can be assigned to groups, users etc. The default assignment for "Transititon issues" in my OnDemand instance was "Project Role (Users)" and "Project Role (Developers)". When I noticed the new feature, I simply deleted the "Project Role (Users)" assignment from that permission and then went on to remove all the conditions in the individual transitions. Way to go, Atlassian! Thank you very much. As to when it will be available for download customers: it went live for 6.3-OD, so according to Atlassian docs you guys should get it as part of 6.3. Don't take my word, though, I'm just a customer.

            Patrice Mondor added a comment -

            @Adam, you have Resolved the this ticket a week ago. Could you please explain here what solution you guys went for? Also when should we expect it?

            Patrice Mondor added a comment - @Adam, you have Resolved the this ticket a week ago. Could you please explain here what solution you guys went for? Also when should we expect it?

            Johan Ferner added a comment -

            Sweet What Jira version will this fix be visible for download customers? 6.3?

            Johan Ferner added a comment - Sweet What Jira version will this fix be visible for download customers? 6.3?

            Jens Bannmann added a comment -

            +1

            This is really annoying. I just had to add a condition to all my 20 transitions, and I, too, fear that when creating new transitions, we might forget to add the condition.

            Jens Bannmann added a comment - +1 This is really annoying. I just had to add a condition to all my 20 transitions, and I, too, fear that when creating new transitions, we might forget to add the condition.

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

                Created:
                Updated:
                Resolved: