Update as of 2018, July 25th

      Hi everyone,

      This is an update to inform you that this ticket is invalid.

      The key used here, jira.permission.create.clone, is invalid. Using the right key, jira.permission.createclone.denied, with the right value, true, the problem shouldn't happen.

      JRASERVER-67652 is about a similar, valid bug when using the right key, and there is a Workaround. Please watch it for more details.

      Original Description

      Summary

      Setting jira.permission.create.clone = disabled on a specific step on JIRA will still allow users to clone issues on that status, unless the property is also set on the first status of the workflow

      Steps to Reproduce

      For this example, I'm using the following workflow as reference: To Do -> In Progress -> Done

      1. Add the following property to the In Progress status: jira.permission.create.clone with the denied value and publish the workflow changes;
      2. Navigate to an issue on the In Progress status and try cloning a ticket on More > Clone

      Expected Results

      The current user won't be allowed to clone the ticket.

      Actual Results

      The current user can normally clone the ticket.

      Workaround

      Set the property on the first status of the workflow as well.

            [JRASERVER-62200] jira.permission.create.clone not working properly

            Just a note that this still occurs even with the correct key - the property must be applied not only at the step desired but also at the Create step.

            Deleted Account (Inactive) added a comment - Just a note that this still occurs even with the correct key - the property must be applied not only at the step desired but also at the Create step.

             

            Any update on this ? i'm on 7.7 and it still doesn't work ....

            Infrastructure added a comment -   Any update on this ? i'm on 7.7 and it still doesn't work ....

            doesn't work in 7.3.8

            Gregory Shulov added a comment - doesn't work in 7.3.8

            scherbank added a comment -

            also affects 7.2.7

            workaround doesn't work as well

            scherbank added a comment - also affects 7.2.7 workaround doesn't work as well

              Unassigned Unassigned
              rrosa@atlassian.com Rodrigo Rosa
              Affected customers:
              4 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: