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

Allow different "Clone Issue" options

XMLWordPrintable

    • 118
    • 34
    • Hide
      Atlassian Update – 10 September 2018

      Hi everyone,

      Thanks for your interest in this issue.
      This request is considered a potential addition to our longer-term roadmap.

      We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

      For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including:

      • Performance and stability improvements
      • Improving performance of boards
      • Improving Jira notifications
      • Creating an email template editor
      • Mobile app for Jira Server

      You can learn more about our approach to highly voted server suggestions here.

      To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 10 September 2018 Hi everyone, Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Improving performance of boards Improving Jira notifications Creating an email template editor Mobile app for Jira Server You can learn more about our  approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our  updated workflow for server feature suggestions . Kind regards, Jira Server Product Management
    • 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.

      The new clone functionality is very useful. It would be really great if we could control what parts of an issue was cloned. For instance:

      • Clone entire issue (subtasks, comments, worklog, everything)
      • Clone with subtasks only
      • Clone with new reporter
      • Clone without subtasks
      • Clone linked issues
      • Etc.

      Hopefully you get the idea.

          Form Name

            [JRASERVER-5052] Allow different "Clone Issue" options

            Jeff Stack added a comment - - edited

            There is already a Clone ticket dialog already with the “Clone attachments” checkbox.  Is it possible to add “Clone Comments” checkbox here as well ?

             

            Jeff Stack added a comment - - edited There is already a Clone ticket dialog already with the “Clone attachments” checkbox.  Is it possible to add “Clone Comments” checkbox here as well ?  

            Dave Carlyle added a comment -

            would also like to see this implemented

            Dave Carlyle added a comment - would also like to see this implemented

            robert cortez added a comment -

            I am sure, just like any other issue with Jira taking forever to implement, that there is some 3rd party app on the marketplace that takes care of this. Jira getting money for work they arent willing to do, apparently. 

            robert cortez added a comment - I am sure, just like any other issue with Jira taking forever to implement, that there is some 3rd party app on the marketplace that takes care of this. Jira getting money for work they arent willing to do, apparently. 

            Grant Yarbrough added a comment -

            Adding that it would be nice when cloning an issue to have the option to link the original issue and cloned issue together as part of the cloning workflow. I can clone related links for the original story, but can't add the original story as a related link.

            Grant Yarbrough added a comment - Adding that it would be nice when cloning an issue to have the option to link the original issue and cloned issue together as part of the cloning workflow. I can clone related links for the original story, but can't add the original story as a related link.

            Libor Micko added a comment -

            Hello, in our company we also miss this feature. I don't understand how it is not considered a bug to keep old epic name when cloning an epic, with the only two options to edit are summary and include links

            Libor Micko added a comment - Hello, in our company we also miss this feature. I don't understand how it is not considered a bug to keep old epic name when cloning an epic, with the only two options to edit are summary and include links

            isoftzis added a comment - - edited

            Poor man's cloning by CSV export/import (must be administrator for that) will work but is laborious (mapping).

            isoftzis added a comment - - edited Poor man's cloning by CSV export/import (must be administrator for that) will work but is laborious (mapping).

            Alexander Tselishchev added a comment -

            Also waiting for this feature.  Need to clone task with new(current) user as a Reporter.

            Alexander Tselishchev added a comment - Also waiting for this feature.  Need to clone task with new(current) user as a Reporter.

            Pamela Switzer added a comment -

            Created in 2004 still in backlog- yikes. What is needed to move this workload into a sprint?

            Pamela Switzer added a comment - Created in 2004 still in backlog- yikes. What is needed to move this workload into a sprint?

            ahmad azfar masut added a comment -

            +1

            ahmad azfar masut added a comment - +1

            Satheesh Kumar (Wipro) added a comment -

            we want to set Epic Link to a particular issue while cloning only for a particular project. Is it possible? Any workaround? (in Post function, shall we create custom condition using ActionId for clone and set Epic Link conditionally?)

            Satheesh Kumar (Wipro) added a comment - we want to set Epic Link to a particular issue while cloning only for a particular project. Is it possible? Any workaround? (in Post function, shall we create custom condition using ActionId for clone and set Epic Link conditionally?)

              Unassigned Unassigned
              59beb99a3f88 Robert Christensen
              Votes:
              513 Vote for this issue
              Watchers:
              300 Start watching this issue

                Created:
                Updated: