Clone the issue and transition it the next board but do not create a ticket in backlog

[Hizkeel Khan]

Hi,

I hope you are well. I am currently in the position where I have to manage two different boards for two separate environments. 

I have two boards: Development board and Staging Environment. I am attaching the screenshot for reference. Below is the screenshot for Development board. 

When ticket moves to Done on Demo, I want to create a clone and move that ticket to Pending staging deployment but keep the original ticket in Done on Demo so I can track the velocity. 

Below is the screenshot for Staging Environment


So, the ticket should move from Done on Demo to Pending Staging Deployment. 

I want to keep the ticket in Done on Demo as well so I can track velocity so when the sprint closes. Also, I don't want to create the tickets in backlog as well. It should be the same in 2 boards. When the sprint ends, the ticket in the Development Env should be completed which makes sense but it should reflect on the staging Env. 

Please let me know how I can achieve this. 
 

[Anahit Sukiasyan]

Hi @Hizkeel Khan

I hope the following steps may be helpful to achieve this scenario using Jira Automation:

1. Create an Automation Rule for the Development Board:

   • Go to Project Settings > Automation (for the Development board).
   • Click Create Rule.
   • Choose the Trigger: Issue transitioned (from any status to Done on Demo).

2. Add an Action to Clone the Issue:

   • Add an Action: Clone issue.
   • Configure the clone to be created in the Staging Environment board.

3. Add Action to Transition the Cloned Ticket:

   • After cloning, you need to transition the cloned issue to Pending Staging Deployment.
   • Add another Action: Transition issue and choose Pending Staging Deployment as the status for the cloned ticket.

4. Add Condition to Ensure No Tickets Go to Backlog:

   • Use a Condition: Issue matches to specify that the new cloned issue should not go to the Backlog (e.g., only transition issues to the specific Staging status).

5. Ensure the Original Ticket in the Development Board Stays in Done on Demo:

   • Jira does not modify the original ticket in the Development board. The ticket will stay in Done on Demo, which will allow you to track velocity, and the clone will go to the Staging board.

6. Handle Sprint Closure for Both Boards:

   • When the sprint ends on the Development board, ensure the Done on Demo ticket is marked as Completed, which is already set for velocity tracking.
   • For the Staging board, the cloned ticket will reflect the Pending Staging Deployment status.

Key Automation Actions Summary:

• Trigger: Issue transitioned from any status to Done on Demo (Development board).
• Action: Clone issue to the Staging Environment board.
• Action: Transition the cloned issue to Pending Staging Deployment (Staging board).
• Condition: Ensure no new tickets are created in the Backlog.

This will allow you to track the velocity on the Development board while the cloned issue in the Staging board progresses through its own workflow.

[Hizkeel Khan]

@Anahit Sukiasyan - Thank you for such a detailed answer. I'll try to implement all these steps and will let you know. 

[Nacho Moreno Ortega]

Hello Hizkeel Khan,

I am Nacho and I am part of Decadis.

I would like to recommend our app Jira Workflow Toolbox for Jira Cloud.

Specifically, with our Create issue post function, you can create a copy of the initial issue and move it to the desired status.

If you are interested in using our app and need further assistance, I encourage you to create a ticket on our support portal and we will gladly assist you.

Best regards,
Nacho

[Clara Belin-Brosseau_Elements]

Hello @Hizkeel Khan

 If I understand correctly, you’re trying to clone an issue into another instance and map the workflow status of the two issues so that the original one doesn't transition, right?

In that case, I can suggest trying our app Elements Copy & Sync. It will allow you to:

- clone your issue to another instance based on a status transition 

- map the workflow status between the two projects 

Don't hesitate to check the documentation, it’s really quick and easy to set up.

The app is for free during 30 days (and it stays free under 10 users).

[sanam malleswari]

Hi @Hizkeel Khan

Add a post function called Create issues in the transition of Done on Demo.
It will give the necessary configuration to setup required features. 
By using JMWE plugin, these post function will be available. 
I have tested, this post function cloning the issues and scripting template is available to set required status for cloned issues.

[sanam malleswari]

When any issue is moved to Done on Demo and it's cloning issue. Keeping the original issue in the Done on Demo status.