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

Ability to disable "Clone Issue" link per project

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • 3.7
    • None
    • 76
    • 14
    • 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.

      Problem Definition

      Currently JIRA allows all users to clone issues (which can optionally be disabled entirely - see workaround). As a JIRA Administrator, I'd like to restrict the ability to Clone issues to certain groups only.

      Suggested Solution

      Add a Clone Issues permission to Permission Schemes.

      Workaround

      (This will disable the Clone feature entirely)

      1. Navigate to Administration » Add-ons » Manage Add-ons;
      2. Select System (in the add-ons type box);
      3. Filter by "issue operation";
      4. Click on it, and select "XX Modules Enabled";
      5. Disable the View Issue Ops Bar Clone Link module.

      See KB: https://confluence.atlassian.com/jirakb/disable-clone-issue-in-jira-747836996.html

      Original Description

      The "Clone this issue" link doesn't mean anything to most of our users, so it would be nice to be able to remove this link. It should be another permission in the Permission Schemes screen (like the "Link Issues" permission)

            [JRASERVER-8497] Ability to disable "Clone Issue" link per project

            Jamie Gerace added a comment -

            also min bar, date/time specific fields should be cleared on "Clone" (or at least prompted to clear) ie. Sprint, Target Start, Target End, Due Date, FixVersion etc. And there is also no value in keeping "clone" in the issue link values or keeping the link itself.

            Jamie Gerace added a comment - also min bar, date/time specific fields should be cleared on "Clone" (or at least prompted to clear) ie. Sprint, Target Start, Target End, Due Date, FixVersion etc. And there is also no value in keeping "clone" in the issue link values or keeping the link itself.

            Keith Walters added a comment -

            Find the clone feature is resulting in poorly defined tickets, based on laziness of humans.  We definitely need the ability to control this at a project level in an enterprise setting - different projects will have different levels of human discipline, which dictates whether or not this feature should be allowed, at a per-project level

            Keith Walters added a comment - Find the clone feature is resulting in poorly defined tickets, based on laziness of humans.  We definitely need the ability to control this at a project level in an enterprise setting - different projects will have different levels of human discipline, which dictates whether or not this feature should be allowed, at a per-project level

            Thanh Ngo added a comment -

            +1

            Thanh Ngo added a comment - +1

            anja.sandadi added a comment -

            FYI: We restrict the Clone button permissions for individual project using workflow properties but this workaround not remove the option to see Clone but gave them an error when they tried to Clone

            https://community.atlassian.com/t5/Jira-questions/Can-I-prevent-users-from-cloning-issues-on-a-specific-project/qaq-p/686125

            anja.sandadi added a comment - FYI: We restrict the Clone button permissions for individual project using workflow properties but this workaround not remove the option to see Clone but gave them an error when they tried to Clone https://community.atlassian.com/t5/Jira-questions/Can-I-prevent-users-from-cloning-issues-on-a-specific-project/qaq-p/686125

            Diana C added a comment -

            +1

            Diana C added a comment - +1

            szacheilas added a comment -

            +1

            szacheilas added a comment - +1

            Valiantys Support added a comment -

            +1

            Valiantys Support added a comment - +1

            Andrei Stoica added a comment -

            We need this for our Jira instance.

            Andrei Stoica added a comment - We need this for our Jira instance.

            Dakota VanLoan added a comment -

            we need to get rid of clones but how?

             

             

            Dakota VanLoan added a comment - we need to get rid of clones but how?    

            Dakota VanLoan added a comment -

            we need to get rid of clones but how?

             

             

            Dakota VanLoan added a comment - we need to get rid of clones but how?    

              Unassigned Unassigned
              b54c559f7dfe David Demner
              Votes:
              278 Vote for this issue
              Watchers:
              131 Start watching this issue

                Created:
                Updated: