Search Jira history with WAS and CHANGED

Published 2026-09-28 by Sidecar Tools. Every JQL query and error message below was run against a Jira Cloud site on 2026-09-28. Automation steps use Jira's current "work item" wording; older sites say "issue".

Short answer

Use WAS to ask "was this field ever this value" and CHANGED to ask "did this field change". For example, everything that has ever been In Review:

status WAS "In Review"

And everything moved to Done in the last seven days:

status CHANGED TO Done AFTER -7d

Queries you can paste

You wantJQL
Was in a status at any point this weekstatus WAS "In Progress" DURING (startOfWeek(), now())
Moved from one status to another recentlystatus CHANGED FROM "In Progress" TO Done AFTER -7d
Status changes you made this weekstatus CHANGED BY currentUser() AFTER startOfWeek()
Work you were ever assignedassignee WAS currentUser()
Reassigned away from youassignee WAS currentUser() AND assignee != currentUser()
Priority raised to High or Highestpriority CHANGED TO (High, Highest) AFTER -30d
Reopened after being resolvedresolution CHANGED FROM Done
Never went through reviewstatusCategory = Done AND NOT status WAS "In Review"

Predicates you can add

Which fields have history search

Only a few fields keep searchable history: assignee, fix version, priority, reporter, resolution and status. Other fields are rejected. For example:

labels WAS urgent

fails with "History searches do not support the 'labels' field." The same applies to custom fields and to CHANGED.

Notes

Want the rest? The Jira Cloud JQL Cookbook has 66 copy-paste queries for triage, sprints, releases, SLAs and reporting, each one validated on Jira Cloud. Get it on Gumroad, pay what you want from $12.