# What Are Jira Automations? | Atlassian Answered Source: https://www.youtube.com/watch?v=43LFvOBz1os Recap page: https://rapidrecap.app/video/43LFvOBz1os Generated: 2025-11-24T19:39:03.344+00:00 --- ## Quick Overview Jira Automations are rules set up in Jira that help projects run smoothly behind the scenes by handling repetitive tasks, thereby saving time and allowing teams to focus on important work, with creation simplified by using natural language prompts via Rovo AI. **Key Points:** - Jira Automations are rules configured in Jira to handle repetitive tasks, ensuring projects run smoothly without manual intervention (0:53). - Each automation consists of three main parts: a Trigger (what starts the rule, e.g., a task being marked 'Done'), a Condition (what filters when the rule applies), and an Action (what Jira executes, e.g., updating a status or sending a notification) (1:01). - Specific use cases include Project Cleanliness automations, such as marking a parent task 'Done' when all sub-tasks are completed (3:15), and sending daily reminders for past-due work (3:57). - Rovo AI allows users to create complex rules by describing the desired outcome in plain English, which Rovo then translates into the required automation structure (2:24, 4:43). - Examples of Rovo-generated rules include assigning issues based on labels (5:24) and automatically updating connected design tasks when a Figma file is updated (6:04). - Automations can integrate with external tools like Slack and GitHub, enabling actions such as sending Slack messages upon a GitHub pull request merge (3:51, 5:58). ![Screenshot at 2:04: The user clicks the Automation icon in the project settings sidebar, leading directly to the Automation configuration screen where templates and custom rule creation options are available.](https://ss.rapidrecap.app/screens/43LFvOBz1os/00-02-04.png) **Context:** This video, part of the Atlassian Answered series hosted by Kevin Lee from Atlassian Learning, provides a high-level overview of Jira Automations. Automations are presented as a powerful feature within Jira designed to eliminate tedious, manual project management tasks like tracking updates, assigning work, and managing task dependencies, ultimately improving project flow and team focus. ## Detailed Analysis The video explains that Jira Automations are rules designed to execute actions based on specific triggers and conditions, automating repetitive project management tasks. An automation rule is fundamentally built from three parts: a Trigger (the event that starts the rule, like an issue transitioning to 'Done' or a due date passing), a Condition (a filter that determines if the rule should proceed, such as checking if all sub-tasks are complete), and an Action (the task Jira performs, such as updating another issue's status or sending a notification) (1:01). The presenter highlights several practical use cases. Project Cleanliness automations ensure board accuracy by updating parent/child tasks automatically; for instance, an automation can transition a parent issue to 'Done' once all its sub-tasks are marked 'Done' (3:15). Another common use case is sending reminders for past-due work daily at 9 AM (3:57). Furthermore, automations facilitate cross-tool integration, such as notifying a team via Slack when a Jira issue updates or moving a related Jira issue to 'Done' when a GitHub pull request is merged (3:51, 5:58). The video emphasizes how Rovo AI simplifies complex rule creation by allowing users to describe the logic in plain English, which Rovo instantly translates into a functioning automation rule flow (2:24, 4:43). This feature is beneficial for large teams or workflows involving external tools like Figma, ensuring tasks are routed correctly based on labels or external updates (5:14, 5:24). ### Automation Fundamentals - Automations are rules built from a Trigger (what starts it) - a Condition (what filters it) - and an Action (what happens) - Examples of triggers include task transition or due date passing (1:01, 1:05, 1:20). ### Project Cleanliness Use Cases - Automations keep boards accurate by automatically updating parent/child tasks - Example: When all sub-tasks are 'Done', the parent moves to 'Done' (3:15, 6:26). ### Scheduling and Notifications - Automations can run on a schedule, like sending a daily reminder at 9 AM for past-due work (3:57). ### Integration Examples - Automations can trigger based on external tools like GitHub (pull request merged) or Figma (file updated) (5:58, 6:04). ### Creating Rules with Rovo AI - Users describe the desired automation in plain English in the Rovo prompt box - Rovo generates the full rule structure (Trigger, Condition, Action) instantly (2:24, 4:43). ### Routing and Assignment Rules - Automations ensure new work lands with the correct person instantly based on labels, such as assigning 'Design' issues to Taylor (5:27, 5:37). ![Screenshot at 0:04: Introduction slide featuring Kevin Lee from Atlassian Learning, setting the context for the 'Atlassian Answered' series.](https://ss.rapidrecap.app/screens/43LFvOBz1os/00-00-04.png) ![Screenshot at 0:53: A slide defining Jira Automations as rules set up in Jira to help projects run smoothly behind the scenes \(0:56\).](https://ss.rapidrecap.app/screens/43LFvOBz1os/00-00-53.png) ![Screenshot at 2:01: The Jira board view showing the user navigating to the Automation section via the project settings menu.](https://ss.rapidrecap.app/screens/43LFvOBz1os/00-02-01.png) ![Screenshot at 3:18: A visual representation of a complex automation rule generated by Rovo, showing the flow of Trigger \(Work item transitioned to Done\) -\> Branch \(For: Parent\) -\> Condition \(Status does not equal Done\) -\> Action \(Transition the work item to Done\).](https://ss.rapidrecap.app/screens/43LFvOBz1os/00-03-18.png) ![Screenshot at 4:44: The Rovo prompt box showing the natural language input: "If someone updates a work item with the label 'creative' send Daniel a Slack message" being processed to build the rule.](https://ss.rapidrecap.app/screens/43LFvOBz1os/00-04-44.png)