Lab Exercise 1: Basic Issue Creation Automation
(Beginner Level - 6 months of experience)
Objective: Automate the creation of a follow-up task when an issue is resolved.
Steps:
Create an Automation Rule:
Go to “Project settings” and select “Automation”.
Click on “Create rule” and choose the “Issue transitioned” trigger.
Set the Trigger Details:
Specify the transition to be from any status to “Done”.
Define the Follow-Up Task Details:
Add an action to “Create issue”.
Set the issue type to “Task” and fill in the summary as “Follow-Up for {{issue.key}}”.
Test and Publish the Rule:
Name the rule “Create Follow-Up Task on Resolution”.
Enable the rule, resolve an issue, and verify that a follow-up task is created.
Deliverable: A screenshot of the automation rule configuration and the new follow-up task linked to the resolved issue.
Lab Exercise 2: Scheduled Backlog Grooming Notification
(Intermediate Level - 1 year of experience)
Objective: Create a scheduled reminder for backlog grooming sessions.
Steps:
Set Up Scheduled Trigger:
Navigate to “Project settings” > “Automation” and create a new rule with a “Scheduled” trigger.
Configure Schedule Details:
Set the schedule to trigger weekly at a specific time before the grooming session.
Set Up Notification:
Add an action to “Send email” to the team with details about the upcoming session.
Test and Activate the Rule:
Name the rule “Backlog Grooming Reminder”.
Activate the rule and ensure the email goes out at the scheduled time.
Deliverable: A screenshot of the automation rule configuration and a sample of the email reminder received.
Lab Exercise 3: Dynamic Priority Assignment Based on Issue Fields
(Skilled Level - 1.5 years of experience)
Objective: Automatically set the priority of new issues based on the impact and urgency fields.
Steps:
Create a New Rule for Issue Creation:
In “Project settings” > “Automation”, select “Create rule” with an “Issue created” trigger.
Configure Priority Logic:
Add conditions to check the “Impact” and “Urgency” fields of the issue.
Use these conditions to set the priority with an “Edit issue” action.
Enable and Test the Rule:
Name the rule “Automatic Priority Setting”.
Turn on the rule and create a new issue to test the priority assignment.
Deliverable: Screenshots of the automation rule and issues with priorities set by the rule.
Lab Exercise 4: Cross-Project Release Synchronization
(Advanced Level - 2 years of experience)
Objective: When a version is released in one project, create a corresponding version in another project.
Steps:
Initiate Version Release Trigger:
Go to the global “Automation” rules and create a rule with a “Version released” trigger.
Configure Cross-Project Action:
Add an action to “Create version” in the target project with the same name and description.
Test and Implement the Rule:
Name the rule “Synchronize Cross-Project Releases”.
Release a version in the primary project and verify that it is created in the secondary project.
Deliverable: Screenshots showing the version release triggering the creation of a corresponding version in another project.
Lab Exercise 5: Complex Issue Routing Based on Reporting Patterns
(Expert Level - 3 years of experience)
Objective: Route issues to different queues based on complex reporting patterns including customer tier, issue type, and report time.
Steps:
Identify Reporting Patterns:
Define JQL queries that capture various reporting patterns you want to route differently.
Set Up an Issue Updated Trigger:
Create a rule with an “Issue updated” trigger in the global “Automation” rules.
Create Advanced Logic for Routing:
Add advanced conditions to evaluate the issue against your JQL queries.
Use “Advanced branch” to route issues to different queues based on the results.
Define Actions for Each Pattern:
For each branch, set up the appropriate action, such as moving the issue to a specific queue or assigning it to a designated team.
Test and Refine the Automation:
Name the rule “Complex Issue Routing”.
Update issues to test each routing pattern and ensure they are moved to the correct queues.
Deliverable: Screenshots
of the automation rule with detailed conditions and actions, and examples of issues routed according to the patterns.