- The Agile Coach
- Agile Manifesto
Agile project management
- Overview
- Project management intro
- Workflow
- Epics, stories, themes
- Epics
- User Stories
- Estimation
- Metrics
- Gantt chart
- Program management vs. project management
- Project baseline
- Continuous improvement
- Lean principles
- 3 pillars of Scrum
- Scrum Board
- Waterfall Methodology
- Velocity in Scrum
- What is Definition of Ready
- Lean vs. agile
- Scrumban
- Lean Methodology
- Sprint backlog
- Burn up chart
- 4 kanban principles
- 4 kanban metrics
- Program vs. Project Manager
- Gantt chart examples
- Definition of done
- Backlog grooming
- Lean process improvement
- Backlog refinement meetings
- Scrum values
- Scope of work
- Scrum tools
- Tools
- Workflow automation software
- Templates
- Task tracker
- Workflow automation
- Status report
- Workflow chart
- Project roadmap
- Project schedule
- Tracking software
- Roadmap tools
- Technology roadmap
- Project scheduling software
- Backlog management tools
- Understanding workflow management strategies
- Workflow examples
- Create project roadmap
- Sprint planning tools
- Sprint demo
- Project Timeline Software
- Top task management tools
- Product backlog vs. sprint backlog
- Top workflow management tools
- Project dependencies
- Task dashboard guide
- Sprint cadence
- Fast tracking
Product Management
- Overview
- Product Roadmaps
- Product Manager
- Tips for new product managers
- Roadmaps
- Tips for presenting product roadmaps
- Requirements
- Product analytics
- Product development
- Remote product management
- Minimal viable product
- Product discovery
- Product specification
- Product development strategy
- Product development software
- New product development process
- Product management KPIs
- Net Promoter Score (NPS)
- Product critique
- Prioritization frameworks
- Product features
- Product management tools
- Product Lifecycle Management
- 9 best roadmap software for teams
- Product launch checklist
- Product strategy
- Product engineering
- Product operations
- Portfolio management
- AI and product management
- Growth product management
- Product metrics
- Product release
- Feature request
- Product launch
- Product planning
- Product launch event
- Value Stream Management
- DevOps
Agile tutorials
- Overview
- Jira and Confluence sprint refinement
- How to do scrum with Jira
- Learn kanban with Jira
- Learn how to use Epics in Jira
- Learn how to create an agile board in Jira
- Learn how to use sprints in Jira
- Learn Versions with Jira
- Learn Issues with Jira
- Learn burndown charts with Jira
- Auto-create sub-tasks and update fields in Jira
- How to automatically assign issues with Jira Automation
- How to sync epics stories with Jira Automation
- Automatically escalate overdue issues in Jira
About the Agile Coach
- All articles
Automatically escalate overdue issues in Jira

By Kev Zettler
By Kev Zettler
Kev is a lead full stack web developer and serial entrepreneur with over a decade of experience building products and teams with agile methodologies. He is a passionate contributor, author, and educator on emerging open source technologies like DevOps, cryptocurrency, and VR/AR. In his free time, he participates in indie game development jams.
This guide will detail how to create a new automation rule that searches for overdue issues once a day, sends a Slack reminder to the team, and adds a comment to the issue. You will need an active Jira project.
Step 1. Create a rule
Navigate to the Automation space in your project settings. In the Rule tab, click on the Create rule button in the top right corner of the screen. On the New Trigger screen search for and select the Scheduled trigger

Configure the Scheduled action to query for issues with a "blocked" status that haven't been updated for more than five days. This uses JQL to dynamically select a set of issues.

Step 2. Add component
Select Add component from the Rule details list on the left sidebar. Search for and select the Comment on issue component.

Use the Comment on issue screen to compose a comment message that the automation rule will automatically apply to transitioned issues. The comment acts as a template string and can interpolate data. The “How do I access issue data in my comment?” link provides examples of how to use the templating system.
Below the comment is configured to inject the reporter.displayName value. You can customize your comment to your liking. Click the Save button when completed.

Step 3. Add a Lookup issues action
Next, add New action and search for the Lookup issues action.

This action aggregates the queried issues into a list for batch actions. This is useful to avoid duplicate follow-up actions. Configure the Lookup issues action so it uses the same JQL query as the schedule trigger.

The following is another example of adding an action component to this rule. On the Add Action screen, search for and select the Send Slack message action.

Step 4. Add Slack message
To enable the Send Slack message action you will need the Webhook URL, which you can get from your Slack administrator. This allows you to specify the message, channel, or user to send the Slack message to. Once you configure the Send Slack message action, click the Save button.

The rule is fully configured now. When you check the Rule details on the left sidebar, it should look like the following:

If your rule details look similar, enter a name for the new rule and click the Turn It On button. Since this is a scheduled rule, you can manually trigger it. Click the Run rule button at the top right of the rule page to execute the rule.

Once you run the rule, visit the Audit Log to review the results and see if the rule executed successfully. If the rule encountered an error, the audit log will help debug the error.
If you would like to explore other examples of rules, head over to our rule template library.
- The Agile Coach
- Agile Manifesto
Agile project management
- Overview
- Project management intro
- Workflow
- Epics, stories, themes
- Epics
- User Stories
- Estimation
- Metrics
- Gantt chart
- Program management vs. project management
- Project baseline
- Continuous improvement
- Lean principles
- 3 pillars of Scrum
- Scrum Board
- Waterfall Methodology
- Velocity in Scrum
- What is Definition of Ready
- Lean vs. agile
- Scrumban
- Lean Methodology
- Sprint backlog
- Burn up chart
- 4 kanban principles
- 4 kanban metrics
- Program vs. Project Manager
- Gantt chart examples
- Definition of done
- Backlog grooming
- Lean process improvement
- Backlog refinement meetings
- Scrum values
- Scope of work
- Scrum tools
- Tools
- Workflow automation software
- Templates
- Task tracker
- Workflow automation
- Status report
- Workflow chart
- Project roadmap
- Project schedule
- Tracking software
- Roadmap tools
- Technology roadmap
- Project scheduling software
- Backlog management tools
- Understanding workflow management strategies
- Workflow examples
- Create project roadmap
- Sprint planning tools
- Sprint demo
- Project Timeline Software
- Top task management tools
- Product backlog vs. sprint backlog
- Top workflow management tools
- Project dependencies
- Task dashboard guide
- Sprint cadence
- Fast tracking
Product Management
- Overview
- Product Roadmaps
- Product Manager
- Tips for new product managers
- Roadmaps
- Tips for presenting product roadmaps
- Requirements
- Product analytics
- Product development
- Remote product management
- Minimal viable product
- Product discovery
- Product specification
- Product development strategy
- Product development software
- New product development process
- Product management KPIs
- Net Promoter Score (NPS)
- Product critique
- Prioritization frameworks
- Product features
- Product management tools
- Product Lifecycle Management
- 9 best roadmap software for teams
- Product launch checklist
- Product strategy
- Product engineering
- Product operations
- Portfolio management
- AI and product management
- Growth product management
- Product metrics
- Product release
- Feature request
- Product launch
- Product planning
- Product launch event
- Value Stream Management
- DevOps
Agile tutorials
- Overview
- Jira and Confluence sprint refinement
- How to do scrum with Jira
- Learn kanban with Jira
- Learn how to use Epics in Jira
- Learn how to create an agile board in Jira
- Learn how to use sprints in Jira
- Learn Versions with Jira
- Learn Issues with Jira
- Learn burndown charts with Jira
- Auto-create sub-tasks and update fields in Jira
- How to automatically assign issues with Jira Automation
- How to sync epics stories with Jira Automation
- Automatically escalate overdue issues in Jira
About the Agile Coach
- All articles
Automatically escalate overdue issues in Jira

By Kev Zettler
By Kev Zettler
Kev is a lead full stack web developer and serial entrepreneur with over a decade of experience building products and teams with agile methodologies. He is a passionate contributor, author, and educator on emerging open source technologies like DevOps, cryptocurrency, and VR/AR. In his free time, he participates in indie game development jams.
This guide will detail how to create a new automation rule that searches for overdue issues once a day, sends a Slack reminder to the team, and adds a comment to the issue. You will need an active Jira project.
Step 1. Create a rule
Navigate to the Automation space in your project settings. In the Rule tab, click on the Create rule button in the top right corner of the screen. On the New Trigger screen search for and select the Scheduled trigger

Configure the Scheduled action to query for issues with a "blocked" status that haven't been updated for more than five days. This uses JQL to dynamically select a set of issues.

Step 2. Add component
Select Add component from the Rule details list on the left sidebar. Search for and select the Comment on issue component.

Use the Comment on issue screen to compose a comment message that the automation rule will automatically apply to transitioned issues. The comment acts as a template string and can interpolate data. The “How do I access issue data in my comment?” link provides examples of how to use the templating system.
Below the comment is configured to inject the reporter.displayName value. You can customize your comment to your liking. Click the Save button when completed.

Step 3. Add a Lookup issues action
Next, add New action and search for the Lookup issues action.

This action aggregates the queried issues into a list for batch actions. This is useful to avoid duplicate follow-up actions. Configure the Lookup issues action so it uses the same JQL query as the schedule trigger.

The following is another example of adding an action component to this rule. On the Add Action screen, search for and select the Send Slack message action.

Step 4. Add Slack message
To enable the Send Slack message action you will need the Webhook URL, which you can get from your Slack administrator. This allows you to specify the message, channel, or user to send the Slack message to. Once you configure the Send Slack message action, click the Save button.

The rule is fully configured now. When you check the Rule details on the left sidebar, it should look like the following:

If your rule details look similar, enter a name for the new rule and click the Turn It On button. Since this is a scheduled rule, you can manually trigger it. Click the Run rule button at the top right of the rule page to execute the rule.

Once you run the rule, visit the Audit Log to review the results and see if the rule executed successfully. If the rule encountered an error, the audit log will help debug the error.
If you would like to explore other examples of rules, head over to our rule template library.
Recommended for you
Templates
Ready-made Jira templates
Browse our library of custom Jira templates for various teams, departments, and workflows.
Product guide
A comprehensive introduction to Jira
Use this step-by-step guide to discover essential features and the best practices to maximize your productivity.
Git Guide
Understanding the Basics of Git
From beginners to advanced experts, use this guide to Git to learn the basics with helpful tutorials and tips.