JQL: How to Find Jira Issues With No Comment in the Last X Days

Q: Is there a JQL function for last comment date in Jira Cloud?

Not natively. Scripting apps add JQL functions, or you can maintain a custom date field with Automation or a last-comment app.

Q: Why does updated <= -7d miss stale issues?

updated changes on any edit (labels, links, automation), so an issue can look active even when no one has replied.

Q: Can I find issues where the last comment was from a customer?

In JSM, use the queues and SLAs. Elsewhere, compare a "Last commented by" field against your team group.

Q: Does comment ~ search only the latest comment?

No, it searches every comment on the issue.

Short answer: Native JQL has no "last comment date" or "last commented by" field, so you can't directly ask Jira for "issues nobody has replied to in 7 days". The closest native queries use updated, which counts any change, not just comments. To query comments properly you need a last-comment field, filled by Automation or by an app.

1. Closest native JQL

No activity at all in 7 days: statusCategory != Done AND updated <= -7d. Any field change resets it, so a bot editing a label hides a stale conversation.
Comment contains a word: comment ~ "blocked" searches all comments, not just the latest.
Waiting on the customer (JSM): Jira Service Management's SLA and "Waiting for customer" status queues cover this for service projects.

2. Add a "Last comment date" field with Automation

Create a date-time custom field "Last comment date" and a user field "Last commented by", then an Automation rule on Work item commented that sets them to {{now}} and {{comment.author.accountId}}. After that:

"Last comment date" <= -7d AND statusCategory != Done finds stale conversations.
"Last commented by" = currentUser() finds issues where you spoke last (waiting on others).
"Last commented by" != currentUser() AND assignee = currentUser() finds issues waiting on you.

Caveats: existing issues are empty until the next comment, deleted comments aren't handled, and each comment uses an Automation run.

3. Saved filters and subscriptions

Save any of the queries as a filter and add a filter subscription (daily email) so stale issues come to you instead of you hunting for them.

4. An app that keeps the fields up to date

Last Comment Fields for Jira (by Loomwise, coming soon) adds three read-only fields, Last comment, Last commented by and Last comment date, that work as list columns, in JQL, filters, dashboards and CSV export. Restricted comments are never copied into the fields, and JSM internal notes are skipped by default. Free for up to 10 users, about $0.35 per user per month above that, billed through Atlassian.

See Last Comment Fields Email us to try it early

FAQ

Is there a JQL function for last comment date in Jira Cloud? Not natively. Scripting apps add JQL functions, or you can maintain a custom date field with Automation or a last-comment app.

Why does updated <= -7d miss stale issues? updated changes on any edit (labels, links, automation), so an issue can look active even when no one has replied.

Can I find issues where the last comment was from a customer? In JSM, use the queues and SLAs. Elsewhere, compare a "Last commented by" field against your team group.

Does comment ~ search only the latest comment? No, it searches every comment on the issue.

Related guides

Disclosure: Loomwise makes the apps mentioned in the cards above and wrote this guide. Not affiliated with Atlassian. Vote counts are from jira.atlassian.com as of October 2026. Last checked October 2026; Jira menus and features change, so verify in your site. Contact: hello@loomwise.app