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

Merging of issues



    • 6
    • 85
    • 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.


      Atlassian Update: 5th of July 2023

      Hi Everyone,

      Thank you for taking the time to share your feature request with us. Your input is greatly appreciated, and we understand the effort and dedication it takes to provide us with your thoughts and ideas.

      We have considered this request, we regret to inform you that we will not build merge functionality into Jira. We understand that this may be disappointing news, and we want to assure you that we take all customer feedback seriously. This feature would be highly complex to implement and due to the existence of low-friction workarounds (see below), we regret to inform you that we will not build merge functionality into Jira in the foreseeable future.

      Instead, there are a few possible workarounds that can be used:

      • Link the issues: You can link the two issues together using a specific link type, such as "duplicate" and close one of them out, or "related" and continue to track the issues together.
      • Move the data: You can manually move the data from one issue to another by copying and pasting the relevant information, such as comments and attachments.

      I will be closing this feature request out. If you have any feedback feel free to email me at aauleear@atlassian.com


      Atlassian Update: 29th January 2018

      Hi all,

      Thank you for your continued interest in this feature suggestion. At Atlassian, we draw customer feedback from many channels and jira.atlassian.com is an invaluable part of the process. Your input is crucial in driving the most value to all our customers in Jira .

      The power of Jira allows issues to be more than simple tasks with a description and summary. Custom fields allow issues to hold distinct values, often with many restrictions and conditions that exist both inside the Jira application and externally via our Atlassian Connect framework. Considering custom fields introduces many complex use cases that must be considered before commencing work on this kind of feature.

      Merging issues would be a significant investment from the Jira team which would require it to be explicitly set on a roadmap. It is currently not on any Jira team’s roadmap. Any updates on this will be promptly reflected in this feature request.

      Please remember that jira.atlassian.com is one of many inputs for the Jira roadmap. You can learn more about our process here.

      I understand that some many not agree with our current decision, so please don't hesitate to contact me if you have any questions.

      Kerrod Williams
      Kerrod (dot) Williams (at) atlassian (dot) com
      Product Manager, Jira

      Original request description:

      Sometimes it is necessary to delete certain issues that are part of another issue without loosing the comments and attachments.

      Therefore it would be helpful to merge these issues in such a way that description and comments are merged with the comments of the 'target' issue attachments are added to the 'target' issue


        Issue Links



              Unassigned Unassigned
              730cb303d20f Oliver Müller
              494 Vote for this issue
              248 Start watching this issue