How to can you clone tickets to release board without losing attachments and comments.

Taffy Muzinda Muzinda March 11, 2024

Currently we have a separate release board where tickets from several boards are cloned into in order to manage and consolidate our releases in one place. With this solution, when tickets are cloned into the release board, attachments and comments are lost. Is there a way to retain this? 

2 answers

1 accepted

1 vote
Answer accepted
Rebekka Heilmann _viadee_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 11, 2024

Hi @Taffy Muzinda Muzinda 

cloning is not the best way to achieve that.

Boards are merely a view on a Set of issues. The Board's filter will distinguish which issues are shown on the board.

It sounds like you want the exact same issue shown on the release board so Comments, Attachments, Status and such are reflected.

Therefore I would suggest including the issues from the other boards in the Board's filter. This is a good starting point if you're new to Boards and Filters: What are board filters? | Jira Software Cloud | Atlassian Support

Taffy Muzinda Muzinda April 16, 2024

Thank you Rebekka, that does seem like a good idea. I suppose the road block would be having to create a whole new workflow that accommodates deployment, previously UAT and deploy where only on the cloned release board.

Rebekka Heilmann _viadee_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 19, 2024

@Taffy Muzinda Muzinda 

Why would you need a new workflow? A board doesn't have its own workflow but only represents the workflow(s) of the board's issues. You can map any status onto the Board's column. You'll have all status from all workflows from all issues in the Board's filter available for mapping.

So if one project is using (To Do - In Progress - Done) and a second one has (In Developement - In Review - Deployed - ...) You could have a column "In Progress" with the Statuses (In Progress - In Developement - In Review) mapped.

0 votes
Luka Hummel - codefortynine
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
March 14, 2024

Hi @Taffy Muzinda Muzinda

If you are willing to use a third-party app, our Deep Clone for Jira could help you. Deep Clone allows you to clone tickets across different projects and boards while retaining key information, including attachments and comments, ensuring a smooth transition and comprehensive data retention for your release management.

Here’s a step-by-step guide on how to use Deep Clone for Jira to clone tickets to your release board without losing attachments and comments:

  1. Install Deep Clone for Jira: First, make sure you have Deep Clone for Jira installed in your Jira instance.
  2. Select Tickets to Clone: Navigate to the tickets you want to clone to your release board. You can select single or multiple issues directly from your issue search.
  3. Initiate the Clone Process: After navigating to the issue view, look for the Actions menu ···. With Deep Clone, you should see an option to perform a Deep Clone. If you selected multiple issues via the issue search, you can look for the Deep Clone icon in the top right. Select this to begin the cloning process.2024-03-14 15-59.png
  4. Configure Clone Options: Deep Clone for Jira offers a range of configuration options. Here, you can specify that you want to clone attachments and comments. Ensure these options are checked to retain all necessary information during the cloning process.2024-03-14 16-01.png
  5. Select the Target Project and Board: As part of the cloning configuration, you'll specify the target project and, implicitly, the release board within that project where you want the cloned tickets to appear.
  6. Execute the Clone: Once you've configured all the settings, proceed to clone the tickets. Deep Clone for Jira will create the clones in your specified location, complete with all the selected elements, including attachments and comments.
  7. Verify the Cloned Tickets: After the cloning process is complete, navigate to your release board to ensure that the cloned tickets appear as expected, with all their details intact.

Deep Clone for Jira not only simplifies the cloning process but also ensures that no critical information is lost during the transition. This can be particularly useful for release management, where having a comprehensive view of each issue, including all discussions and attached documents, is crucial for tracking and coordination.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events