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.