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?
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.