Is it possible to use Jira automation to transition a ops sub task to DEPLOYED IN PROD.

Vivek J

I want to create a Jira automation that automatically deploys an ops sub-task to push Bitbucket changes to production without manual intervention. This automation should run twice a week in scrum board. 

The steps for the automation are as follows:

1. Use the scheduler to create a Non-Development Work ticket.
2. Create an ops sub-task linked to the Non-Development Work ticket as the parent issue. Both the task and the ops sub-task need to be visible in the current sprint for visibility purposes.
3. Transition the ops sub-task to ‘Ready for Prod’ and then to ‘Deployed in Prod’ (if possible, directly transitioning to ‘Deployed in Prod’ to trigger deployment).
4. Once the ops sub-task is deployed to production, it should trigger the Bitbucket deployment.
5. Send an email to my team indicating that the automation has been triggered and requesting confirmation.
6. Transition the Non-Development Work ticket to ‘Done’.

The screenshot I provided is the automation I tired to make myself, it currently only creates the Non-Development work ticket only, rest of the automation fails. 

 

Manoj Kumar Gangwar

Hi @Vivek J Welcome to the community! 

To create this Jira automation for deploying a Bitbucket change, follow these steps. You will need both Jira automation rules and potentially integrations with Bitbucket pipelines or APIs.

 

Steps:

Create a scheduled trigger:

 

In Jira Automation, create a rule with the trigger "Scheduled" and set it to run twice a week (e.g., on specific days or intervals).

Create a Non-Development Work ticket:

 

After the trigger, use the "Create Issue" action to create a new ticket (Non-Development Work).

Set necessary fields like the project, issue type, summary, and any custom fields.

Create an ops sub-task linked to the parent issue:

 

Add another "Create Issue" action to create a sub-task. Link it to the previously created Non-Development Work ticket using the "Parent Issue" field.

Ensure that both tickets (task and sub-task) are assigned to the current sprint by using the “Edit Issue” action to update the sprint field.

Transition the ops sub-task:

 

Add a "Transition Issue" action to move the ops sub-task to ‘Ready for Prod.’

After this, add another transition to move the sub-task to 'Deployed in Prod.'

If your workflow supports direct transitions, you can combine these into one step. If not, use two transition actions.

Trigger Bitbucket deployment:

 

Use the "Send web request" action to trigger a Bitbucket deployment via its API or a webhook. Ensure the correct API token and endpoints are used to execute the deployment to production.

Send an email notification:

 

Add an action to "Send Email" to notify your team. Include key information, like which issue was moved to production and when. Optionally request confirmation from the team.

Transition the Non-Development Work ticket:

 

After the Bitbucket deployment, transition the Non-Development Work ticket to ‘Done’ using the "Transition Issue" action.