Automatically Close Stale Jira Issues with a Scheduled Automation Rule

The problem: stale work clutters boards

Teams often leave issues in "In Progress" for weeks without updates. These stale items hide real blockers, inflate velocity metrics, and make it harder to spot work that actually needs attention.

Thesis: a simple scheduled automation can move stale issues to Done

By using Jira Automation’s schedule trigger, a JQL query, and a transition action, you can automatically close issues that have not been updated for a defined period, while adding a comment that explains the change.

Setting up the rule

1. Navigate to Jira Settings → System → Automation (global) or Project Settings → Automation for a project‑scoped rule.
2. Click Create rule and choose the Scheduled trigger.
3. Configure the schedule: Daily at 02:00 (adjust time to low‑usage window).
4. Add a JQL condition block. Example JQL:

   project = PROJECT_KEY AND status = "In Progress" AND updated <= -14d

   Replace PROJECT_KEY with your project and adjust -14d to the stale threshold you want.
5. Add an Action → Transition issue. Choose the target status (e.g., Done).
6. Add another action: Add comment. Use a comment like:

   This issue was transitioned to Done automatically because it had no updates for 14 days.

7. Optionally add a Condition to exclude certain users or components:
• Condition → User field → Reporter ≠ automation
• Condition → Component → not in ExcludeList
8. Name the rule (e.g., "Close stale In Progress issues"), enable it, and save.

Worked example

Suppose you have a project TEST and you want to close issues that have sat in In Progress for more than 10 days.

• Schedule: Daily at 03:00.
• JQL: project = TEST AND status = "In Progress" AND updated <= -10d
• Action: Transition to Done.
• Comment: Automatically closed due to 10+ days of inactivity.

After saving, you can test immediately:

1. Create a test issue in TEST, set status to In Progress, and back‑date its Updated field (via issue edit or API) to 12 days ago.
2. Use the Run rule button on the automation rule page.
3. Check the issue: it should now be in Done with the expected comment.
4. Open Audit log from the rule details to confirm the execution succeeded and no errors appeared.

Trade‑offs and limitations

• Execution limits: each Jira plan caps the number of automation runs per month. A daily rule that matches many issues can consume a large share of that quota. Monitor usage via Automation → Usage.
• Over‑broad JQL or a very short stale threshold may transition work that is legitimately pending (e.g., waiting on external approval). Start with a conservative threshold and widen only after reviewing audit logs.
• Because the rule changes issue status automatically, communicate the policy to teams. Consider adding a transition screen that prompts for a reason before moving to Done, or keep a manual approval step for high‑risk projects.

Actionable closing

Start small: create a rule for a single pilot project with a 14‑day stale threshold and a low‑frequency schedule (e.g., weekly). Verify the results in the audit log, gather team feedback, then adjust JQL, schedule, or scope before rolling out to additional projects. This approach gives you visibility into automation consumption while keeping board hygiene under control.