JQL: Find Jira Issues Where Someone Outside Your Team Commented Last

Short answer: Native JQL has no "last commented by" clause, so comment ~ and updated can't tell you whose turn it is. In Jira Service Management, use the built-in Waiting for support / Waiting for customer statuses and SLAs. Everywhere else, maintain a Last commented by user field (Automation or an app) and query it with membersOf().

1. Jira Service Management (native)

The default service workflow plus the built-in automation Transition on comment moves a request to Waiting for support when the customer comments and to Waiting for customer when an agent replies publicly. Query: project = HELP AND status = "Waiting for support".
SLAs such as Time to first response and Time to resolution highlight the oldest waiting requests in queues.
Limit: it's status-based, so it breaks when agents transition manually or a customer replies by email to a resolved request. JSDCLOUD-4271 asked for a "last commented by customer" field.

2. Any project: an Automation-filled "Last commented by"

Create a user picker (single user) field Last commented by and a date-time field Last comment date, and add them to the edit screen.
Rule: trigger Work item commented > Edit work item: Last commented by = {{comment.author.accountId}}, Last comment date = {{now}}. In JSM, add a condition {{comment.internal}} equals false if internal notes shouldn't count.
Create a group for your team (for example support-team).

Then:

Waiting on your team: "Last commented by" not in membersOf("support-team") AND statusCategory != Done
Waiting on the customer: "Last commented by" in membersOf("support-team") AND statusCategory != Done
Waiting on you personally: assignee = currentUser() AND "Last commented by" != currentUser() AND statusCategory != Done
Oldest first: add ORDER BY "Last comment date" ASC

Caveats: issues commented before the rule existed stay empty until the next comment; deleted comments aren't handled; every comment uses an Automation run; and a plain rule doesn't know about restricted comments, so an internal comment can make it look like your team replied.

3. Save it as a queue for the team

Save the "waiting on your team" query as a filter, add it to a dashboard (Filter results gadget, sorted by Last comment date) and create a daily filter subscription so the list comes to you.

4. Keep the fields filled automatically

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 who commented last? Not in native Jira Cloud. Scripting apps add JQL functions, or you can maintain a "Last commented by" field with Automation or a last-comment app.

Does membersOf() work with custom user fields? Yes. "Last commented by" in membersOf("group") works for user picker custom fields.

How do I exclude JSM internal notes? In Automation, add the condition {{comment.internal}} equals false. Loomwise Last Comment Fields skips internal notes by default.

Can I see the last comment text in the list too? Yes, with a "Last comment" text field. See our guide to showing the last comment as a column.

Related guides

Disclosure: Loomwise makes the apps mentioned in the cards above and wrote this guide. Not affiliated with Atlassian. Vote counts and ticket statuses 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