Jira Stale Ticket Reminder

Find open Jira tickets that have gone quiet and remind the team so nothing slips through the cracks.

Use case

Tickets often stall silently — the assignee gets pulled onto something else, or a blocker quietly lingers. Running this on a schedule (e.g. every weekday morning) surfaces aging work before it becomes a problem and keeps boards honest without anyone manually combing through Jira.

What it does each run

1. findStale — calls the jira connector with operation: search and a JQL filter for issues that are not Done and have had no update in the last 7 days, ordered oldest-first (maxResults: 50). The connector publishes two outputs: result (the raw Jira search JSON, whose issues array holds each ticket's key and fields) and status (the HTTP status).
2. notifyOwners — sends a message notification to the workflow's contacts. The body embeds {{findStale.result}} (the raw issues JSON) and {{findStale.status}} so owners can see exactly which tickets are stale and review, update, or reassign them.

Note: connector tools publish only result and status. This workflow reads the stale-ticket list straight out of {{findStale.result}}; it does not invent any per-field outputs like count or issues.

Required credentials

• Jira API key — the findStale task's apiKey property is set to the placeholder <set via credential>. Supply your real Jira credential by attaching a Jira credential to the task (or injecting it via a runtime environment variable). Jira Cloud authenticates over OAuth, so this workflow depends on a live authenticated connector. Never hardcode the key in the YAML.

Tuning

• Change updated <= -7d in the JQL to widen or narrow the staleness window.
• Scope it with AND project = ABC or AND assignee = currentUser().
• Raise/lower maxResults to cap how many tickets one reminder lists.
• Edit notifications[].userNames and the message task to route to the subscribers/channels you want.

Scheduling

Attach a schedule (e.g. weekdays at 9:00) so the reminder lands at the start of the day. With no schedule it runs on demand.