This screenshot captures an automation rule I created within Jira to automatically generate follow-up tickets in the DBA (Database Operations) project whenever certain conditions are met in the IT Change Request (ITCR) workflow. Here’s how I created it, and why it was so effective:

⸻

🧠 Purpose of the Automation

The goal was to reduce manual handoffs and ensure that the DBOps team was automatically notified and engaged as soon as a change request became deployment-ready, eliminating missed steps and delays in the deployment pipeline.

🛠️ How I Built It – Step-by-Step

1. Navigated to the ITCR project settings and selected the “Automation” tab in the left-hand menu.

2. Clicked “Create rule” to start building a new automation.

3. I named the rule “Create ticket on DBA Board 2.0” for clarity and versioning purposes.

4. Trigger: “When: Work item transitioned TO Deployment Ready”

• This sets the automation to run any time a Jira issue transitions into the Deployment Ready status.

• This aligns with my workflow rules, which ensure the ticket has passed all three required approvals (business, technical, and quality).

5. Condition: “Deployment Support Team contains any of: DBOps”

• I added a condition to check whether the ticket’s Deployment Support Team custom field included DBOps as a value.

• This filters the automation to only apply to tickets where database operations are involved, preventing unnecessary tickets for other teams.

6. Action: Create a new Jira Issue

• If both the trigger and condition are true, the rule automatically creates a new Story in the DBA (DBOPS) Jira project.

• I selected the Story issue type, as this is what the DBA team uses to track their work.

• Under the Summary field, I used smart values to format it clearly:

This helps the DBA team quickly identify which ITCR ticket this new story is tied to.

• The Description field pulls directly from the original issue using:

This ensures all context is carried over.

• I also enabled the “Copy Attachment from Current Work Item” option so that any relevant documents (like deployment steps or test evidence) get included automatically.

✅ Why This Matters

• Automates DBA Handoff: As soon as a change is approved and ready, the DBA team gets a clearly linked task—no one has to remember to create it manually.

• Eliminates Communication Gaps: It ensures no delays or confusion between IT and DBOps teams.

• Standardized Info Transfer: With consistent summaries, descriptions, and attachments, DBA engineers get all the details they need without asking for more info.

• Audit-Friendly: Every step is traceable and triggered based on logical, review-backed events.

This automation shows how I’ve used Jira’s native rule engine and smart values to create cross-team workflows that scale, reduce errors, and free up time for everyone involved.