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

Go to "Edit" screen before creating cloned issue

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.

      What is the reason to clone issues? When you are too lazy to copy&paste strings from already created issue to the new one. Or when you have same task for various developers.
      But you won't need to clone issue to have same person have 2 completely same issues.
      So - I want to tell that you always edit issue after cloning. So why not to do following workflow:
      istead of

      1. click "Clone"
      2. create new issue
      3. edit new issue
        do
      4. click "Clone"
      5. edit new issue
      6. create new issue

      Currently it is possible only to change issue title - why not to allow to edit all issue fields.
      Another reason to do this - if you clone issue 5 times and then reassign clones to different developers - original issue owner will receive 5 email notifications that he has 5 new issues.

              Unassigned Unassigned
              d94f58271e8f Andrew Kulinich
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: