Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-59540

Make Clone Issue Configurable

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • 0
    • 11
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Problem Definition

      We would like to disable or limit the use of the "Clone" issue in JIRA. The problem is that the cloning issues makes our issues less manageable. It would carry over too much information from the old issue such as assignee, due dates, fix versions, sprint, etc. while the new cloned issue hasn't been worked on. What the user really wants to do is just copy over the summary, description, etc.

      Suggested Solution

      Simpler way: just the ability to disable "Clone" function, either globally, or based on users, groups, or project role.

      Alternatively, allow us to specify which fields will be included/excluded when copying over information from the cloned issue to the new issue.

              Unassigned Unassigned
              namir Nursihah Amir (Inactive)
              Votes:
              10 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: