Atlassian Jira Automation Unleashed

In this lecture, we will explore the key elements of the Atlassian Automation user interface, giving you a clear understanding of how to navigate and interact with its various features. Whether you're just getting started or looking to improve your efficiency, this session will walk you through everything you need to know to get comfortable with the interface.

Here's what we'll cover:

• Automation Dashboard: Learn how to access and manage your automation rules, find existing rules, and understand the basic layout of the dashboard.

• Audit Logs: Discover where to find audit logs, how to read them, and what information they provide to help you track the performance of your automation rules.

• Templates and Usage: Get to know the templates available to you and how to utilize the usage tabs to see where rules are being applied across your projects.

• Performance Insights: Understand how to use performance insights to monitor the efficiency of your automation rules, helping you identify and resolve potential issues.

• Admin Settings: For those with administrative access, we’ll explore global settings, permissions, and how to manage automation rules at the organization level.

By the end of this lecture, you’ll have a solid foundation for navigating the automation user interface, enabling you to create, manage, and optimize your automation rules with confidence.

In this session, we will cover everything you need to know about managing automation rules in Jira. This is a critical skill for anyone looking to maintain a well-organized and efficient automation system. Here’s what you can expect to learn:

• How to create, edit, and activate automation rules within Jira.

• Techniques for managing rule execution and controlling when and where rules are applied.

• Best practices for organizing your automation rules, including naming conventions, documentation, and categorization for large-scale environments.

• Insights into monitoring rule performance, ensuring your automations run smoothly and identifying any potential issues.

• How to move automation rules between environments (from sandbox to production), and tips on maintaining consistency across multiple Jira sites.

By the end of this session, you’ll have the tools and knowledge needed to confidently manage and scale your Jira automation rules, ensuring your automations are both reliable and efficient.

In this lecture, we’ll explore how to navigate the Atlassian Developer site, a critical resource as you start building more complex automation rules. You’ll learn how to access key information on the site, focusing on the Jira Cloud platform and how to use Atlassian's REST APIs. We’ll walk through the interface, including how to toggle between different API versions (V2 and V3), and show you where to find essential documentation that will empower your automation efforts. This lecture provides a hands-on guide to leveraging the developer tools, focusing on how to extract the most value for your automation projects.

In this lecture, we will walk through the process of setting up basic authorization for accessing Jira REST API. You will learn how to generate an API token, combine it with your email, and create a base64-encoded authorization string. This string is essential for securely authenticating your API requests as we explore how to interact with Jira data throughout the course. By the end of this lesson, you’ll have a solid understanding of the steps required to set up and use basic authorization for Jira’s API.

What exactly is a trigger?

A trigger is what kicks off your automation rule. It waits for an event to happen and says, “Hey, it’s time to run the rule!” Imagine triggers as a race starter who fires the gun to signal the start of the race—when the right event occurs, your automation takes off.

For example, let’s say you want to automatically assign a task when an issue is created. The trigger here would be the creation of an issue, and that’s what prompts Jira Cloud to execute the rule. Triggers allow automation to listen for these specific events and react accordingly.

Quick Transcript Highlight:
As mentioned in the transcript, triggers "listen to events and inform your rules that it's time to jump into action." They are the "starter at a race"—a simple but powerful analogy to visualize the role of triggers.

Pro Tip: Always ensure you're using the right trigger for the right situation. If you're looking to automate issue assignments, the Issue Created trigger might be your go-to. But if you’re working on more complex workflows, there are other advanced options to consider.

Not all triggers are created equal!

Triggers in Jira Cloud are neatly categorized to help you find exactly what you need for your specific use case. Understanding these categories will make it easier for you to choose the appropriate trigger based on the type of project you're working on—whether it’s software development, service management, or security.

Here’s a breakdown of the six main trigger categories you’ll encounter:

1. General Triggers: These are the most common triggers and can be applied to nearly any Jira Cloud project. They help you automate basic tasks like when an issue is created, updated, or transitioned to a different state.

   • Example Trigger: Issue Created – Start automation whenever a new issue is created in a project.

2. Software Development Triggers: Specifically designed for teams that manage code repositories and workflows. These triggers respond to events like pull requests and code merges.

   • Example Trigger: Pull Request Merged – Automatically close Jira issues when a related pull request is merged.

3. DevOps Triggers: For teams working with continuous integration and deployment pipelines, these triggers help manage deployment tasks.

   • Example Trigger: Deployment Started – Notify teams when a new deployment begins.

4. Security Triggers: These are focused on governance and security, allowing you to respond automatically to changes in user access or group memberships.

   • Example Trigger: User Added to Group – Automatically create a Jira issue when a user is added to a high-privilege group.

5. Jira Service Management (JSM) Triggers: If you're managing customer support or internal service requests, these triggers are key for monitoring SLAs and automating ticket updates.

   • Example Trigger: SLA Threshold Breached – Escalate tickets automatically when an SLA is about to be breached.

6. Design Triggers: Tailored for creative teams, these triggers support workflows specific to design and content creation.

Pro Tip: The most useful triggers in this category are the Schedule and Incoming Webhook triggers, which allows you to run automation at specific times and create reusable modules.

For the more advanced users, there’s even more!

As you get comfortable with the basics, you’ll find that Jira Cloud offers more sophisticated triggers for automation developers. These triggers give you deeper control over your workflows and allow for more creative, tailored automation.

Here are some advanced triggers to explore:

1. Scheduled Triggers: These triggers are incredibly flexible, allowing you to run automation at predefined intervals. If you have tasks that need to be performed on a schedule, such as reporting or backlog cleanup, this is the go-to option.

   • Example Use Case: Run a rule every Monday morning to automatically close issues that have been resolved for more than 30 days.

2. Incoming Webhook Triggers: For those integrating Jira Cloud with external systems, webhook triggers allow your automation to react to events happening outside of Jira. Whether you’re responding to alerts from a monitoring tool or tracking customer activities, webhooks open a wide range of possibilities.

   • Example Use Case: Automatically create Jira issues when a critical system monitoring alert is triggered.

3. JQL-Based Triggers: This trigger allows you to run automation rules based on specific search queries using Jira Query Language (JQL). It’s great for highly customized automation based on particular issue properties or statuses.

   • Example Use Case: Create a trigger that escalates all unresolved critical issues that have been open for more than 72 hours.

Quick Highlight:
When testing an automation rule, you can use the Scheduled Trigger to debug it. By manually triggering the schedule, you can validate your automation rule before it’s live, ensuring everything runs smoothly.

Pro Tip: Use the Webhook Trigger if you're integrating with external systems like Slack or monitoring tools. This will help you automate cross-platform processes and keep everything connected.

In this session, you'll dive into the world of conditions in Jira automation. Conditions are a powerful way to control how and when your automation rules run, ensuring they only trigger when specific criteria are met. You'll learn:

• What conditions are and why they are essential in automating workflows.

• How to add and configure conditions to filter actions in your automation rules.

• Real-life examples of conditions at work, such as making sure an issue meets certain requirements before an action is taken.

• Best practices for using conditions efficiently to optimize your automation flows and avoid unnecessary actions.

By the end of this lesson, you'll be able to confidently apply conditions in Jira automation, giving you more control over how your rules behave. Whether you're looking to enhance your team's workflow or simply gain a better understanding of Jira automation, this session is designed to provide you with actionable insights and hands-on knowledge!

This session focuses on branching and advanced logic in Jira automation, a critical skill for anyone looking to take their automation rules to the next level. Here’s what you can expect to learn:

• An introduction to branching, which allows you to apply different automation paths within the same rule, enabling powerful, multi-step processes.

• How to set up if/else logic and other branching strategies to control workflows and decision-making within your automation.

• Real-life examples demonstrating how branching can help you automate complex workflows with ease, making your automation more dynamic and responsive to varying conditions.

• Tips and tricks for mastering advanced logic, ensuring that your rules are both flexible and efficient.

By the end of this session, you'll have the knowledge and confidence to implement branching and advanced logic in your Jira automation rules, unlocking a new level of functionality and customization for your team

In this session, we'll explore one of the most important parts of Atlassian Automation: actions. Actions are what make automation rules do the work, whether it's sending a notification, transitioning an issue, or making updates across your projects. Here’s what you can expect to learn:

• What actions are and how they fit into your automation rules.

• The different types of actions available in Jira Automation, including updating fields, sending notifications, creating issues, and more.

• How to configure actions to perform exactly what you need for your workflows.

• Real-world examples of how to use actions to automate repetitive tasks and streamline your team's work processes.

• Tips for optimizing your actions to improve the efficiency of your automation rules.

By the end of this session, you'll have a thorough understanding of how to set up and configure actions within your automation rules, empowering you to create smarter, more efficient workflows in Jira.

In this session, we’ll delve into smart values and variables in Atlassian Automation, which are key to unlocking advanced functionality in your rules. Here’s what you can expect to learn:

• What smart values and variables are and how they can be used to make your automation rules more powerful.

• How to apply smart values to dynamically pull data from issues, users, projects, and more, enabling more customized automation.

• Real-world examples of using smart values to perform complex calculations, access issue data, and create dynamic notifications.

• Best practices for working with variables, helping you to store, reuse, and pass information between actions within your rules

n the “Get Users from Group” session, I introduce the Extend Pattern for Atlassian automation—a powerful concept that will be a recurring theme throughout this course.

The Extend Pattern refers to automations that go beyond Jira’s or Confluence’s out-of-the-box capabilities by leveraging the Send Web Request action. This approach enables you to integrate external APIs and unlock advanced functionality within your automations.

In this class, we’ll tackle a practical example to highlight the following concepts:

• Using the Scheduled Trigger to run automations at specific intervals.

• Creating Smart Values and Smart Variables to store and manipulate data dynamically.

• Extending Jira’s capabilities by making API calls with the Send Web Request action to retrieve details about users in a specific Jira group.

• Iterating over API responses with Advanced Branching to process user data efficiently.

• Applying the Smart Value If Condition to identify unauthorized users in the group and flag them for action.

By the end of this session, you’ll understand how to create extend pattern automation.

In this session, we’ll be tackling a practical scenario: getting users from a group in Jira and filtering them based on specific criteria. Here’s what you can expect to learn:

• How to retrieve users from a group in Jira using automation rules and APIs.

• Techniques to filter and identify users who meet certain criteria, such as those who are not site administrators or belong to specific user roles.

• Step-by-step guidance on configuring this functionality in Jira automation, ensuring that your rules efficiently handle user groups.

• Practical applications of this knowledge, including improving governance and security by automatically managing user access and permissions.

By the end of this session, you’ll have a solid understanding of how to automate the process of retrieving and managing users from groups in Jira, empowering you to handle user roles and permissions more effectively within your organization.

In the “Check for Dormant Projects” session, we’ll build on the Extend Pattern, reinforcing how to go beyond the platform’s standard capabilities.

We’ll start by exploring how to locate the necessary API calls for your projects, using resources like developer.atlassian.com.

Specifically, we’ll dive into the Get Projects Paginated REST API and focus on using the expand query parameter to fetch enriched project details.

The session will guide you through:

• Reusing the Scheduled Trigger to automate regular checks.

• Making API calls with the Send Web Request action to retrieve project data.

• Working with web responses, including extracting key information for further processing.

• Using Advanced Branching to iterate through the data returned by the API.

• Leveraging Smart Values for date manipulation, such as {{now}} and {{diff()}}

• and highlight the importance of casting variables to their correct types.

• Using Smart Value Conditions and Logging automation outputs, to monitor and validate results.

By the end of this session, you’ll gain more experience with Smart Values, and how to navigate REST API documentation so you can extend your own automations.

In this session, we’ll be going on a mission to find dormant projects in Jira. This is an important skill for managing projects that have become inactive. Here’s what you can expect to learn:

• How to identify dormant projects in Jira that have not been updated or active for a certain period (e.g., 3 months).

• Step-by-step instructions on setting up Jira automation to automatically detect and flag inactive projects.

• Techniques to streamline governance by identifying projects that may need to be archived or closed based on inactivity.

• Real-world use cases of why identifying dormant projects is critical for maintaining a clean, organized Jira environment and optimizing resources.

By the end of this session, you’ll be equipped with the knowledge to automate the detection of dormant projects, ensuring that your Jira instance remains efficient, clutter-free, and well-governed.

In this session, we’ll explore how to comment and inform using Jira automation, a critical skill for ensuring clear communication in your projects. Here’s what you can expect to learn:

• How to use Jira automation to automatically comment on issues, ensuring that the right information reaches the right people at the right time.

• Strategies for informing stakeholders by sending notifications or updates when specific events occur in your Jira projects.

• Best practices for maintaining effective communication in your teams, ensuring transparency and clarity through automation.

• Real-world examples of how automated comments and notifications can help streamline processes, reducing manual updates and keeping everyone informed.

By the end of this session, you’ll have a strong understanding of how to set up automated comments and notifications, ensuring that your team stays connected and informed throughout the project lifecycle.

In this session, we will tackle the process of creating Jira components using automation. Components are a great way to organize and categorize work within Jira projects, and automating their creation can save you valuable time. Here’s what you can expect to learn:

• How to automate the creation of Jira components, simplifying the process of setting up new projects or maintaining existing ones.

• An introduction to what components are, why they are essential, and how they help structure your Jira projects.

• Step-by-step guidance on configuring Jira automation rules to automatically create components, based on specific triggers or criteria.

• Real-world applications of this automation to improve your project management and ensure consistency across projects.

By the end of this session, you’ll have the skills to efficiently automate the creation of components in Jira, allowing you to focus on higher-level tasks while automation takes care of the setup!

In this session, we’ll dive into the essential concept of persisting data in Jira automation, a technique that allows you to store and reuse data across multiple automation executions. Here’s what you can expect to learn:

• What persisting data means in the context of Jira automation, and why it’s important for maintaining state across different automation rules.

• How to set up entity properties and other techniques for storing data, enabling more complex workflows and automations.

• Practical examples of when and how to persist data, such as saving user inputs, storing task progress, or maintaining issue statuses across automation rules.

• Best practices for managing and accessing stored data, ensuring consistency and accuracy in your automation processes.

By the end of this session, you’ll understand how to persist data in Jira, empowering you to build more sophisticated, stateful automation rules that can handle multi-step processes with ease.

In this session, we’ll explore the concept of Round Robin Orchestration in Jira automation, a powerful method for distributing tasks and ensuring balanced workloads. Here’s what you can expect to learn:

• How Round Robin Orchestration works and why it’s beneficial for managing task assignments across teams or projects.

• Techniques for setting up Jira automation to rotate tasks or issues among team members, ensuring fair distribution of workload.

• Real-life examples of using this orchestration pattern to enhance team productivity and avoid bottlenecks.

• Best practices for monitoring and adjusting the orchestration to ensure it meets your team's specific needs and workflows.

By the end of this session, you’ll be able to implement Round Robin Orchestration in your Jira automation rules, enabling smoother task distribution and improved governance for your projects.

In this session, you will get introduced to confluence automation, and specifically to the "for each inactive pages" branch and "archive page" actions.

In this session, we’ll dive into vaulting and using secrets within Jira automation. Managing sensitive information like API tokens or passwords securely is crucial for any automation. Here’s what you can expect to learn:

• How to vault secrets using secure storage solutions, ensuring sensitive information is not exposed within your automation rules.

• Techniques for retrieving and using secrets securely in automation workflows, making sure your automation rules stay efficient while protecting data integrity.

• Best practices for managing and rotating secrets to minimize security risks while ensuring smooth automation processes.

• Real-world examples of how to integrate secret management in Jira automation to streamline workflows without compromising security.

By the end of this session, you’ll be equipped with the knowledge to securely manage and utilize secrets in your automation rules, ensuring that your workflows are both efficient and secure.

In this session, we will focus on how to maintain documentation in Confluence using Jira automation. Keeping your documentation up to date can be time-consuming, but automating the process makes it much more manageable. Here’s what you can expect to learn:

• How to automate the creation of Confluence pages based on information from Jira issues, ensuring documentation is generated automatically as work progresses.

• Best practices for linking Jira issues to Confluence pages, making it easy for your team to track and refer to the relevant documentation.

• Real-world examples of how automating documentation can streamline your workflows and ensure that key information is always captured without manual updates.

• Tips on organizing and maintaining a well-structured documentation system in Confluence, ensuring everything stays accessible and up-to-date.

By the end of this session, you’ll have the skills to set up Jira automation rules that create and maintain documentation in Confluence, freeing up your team to focus on more critical tasks while keeping everything documented automatically.

In this session, we’ll tackle the issue of intercepting unauthorized users in Jira, a critical security measure for protecting sensitive information. Here’s what you can expect to learn:

• How to set up Jira automation to detect and intercept unauthorized users in Jira groups, ensuring compliance with security policies.

• Techniques for automating alerts and actions when unauthorized users are found, including creating issues for tracking and notifying administrators.

• Real-world examples of how this automation can help maintain security and governance across large Jira environments.

• Best practices for managing user permissions and ensuring that only authorized users have access to sensitive data.

By the end of this session, you’ll be able to implement automated solutions to intercept and manage unauthorized users in Jira, enhancing your platform’s security and governance capabilities.

In this session, we will focus on archiving all dormant projects across an entire organization using Jira automation. Here’s what you can expect to learn:

• How to identify and automate the detection of dormant projects that have been inactive for a set period across multiple Jira sites.

• Step-by-step instructions on setting up Jira automation to archive these inactive projects efficiently, ensuring that only active and relevant projects remain accessible.

• Practical applications of this process to streamline governance and manage resources more effectively in large organizations.

• Best practices for maintaining clear communication with stakeholders during the archiving process, keeping everyone informed about project statuses and actions taken.

By the end of this session, you’ll be able to implement an organization-wide solution for archiving dormant projects, helping you keep your Jira instance clean and focused while enhancing governance processes.

In this session, we’ll explore monitoring the health of Atlassian automation to ensure your automation rules are running efficiently and without issues. Here’s what you can expect to learn:

• How to set up Jira automation to monitor the health of automation rules, ensuring that they perform as expected and identifying any issues promptly.

• Techniques for sending alerts and notifications to automation owners when an issue arises, helping to maintain operational transparency.

• Integration with http://Statuspage.io  to provide organization-wide updates on the status of automation, improving communication across teams.

• Best practices for proactively managing and maintaining automation rules to prevent failures and optimize performance.

By the end of this session, you’ll know how to keep your automation rules in top shape, ensuring that any potential issues are addressed quickly and efficiently while keeping your organization informed of automation health.

This document outlines changes made to the course over time.