How to search Jira by watchers
Short answer
Jira Cloud has two watcher fields and they are not interchangeable. watcher (singular) takes a person and asks who is watching. watchers (plural) takes a number and asks how many people are watching. Using the wrong one is the most common mistake:
watcher = currentUser()
watchers > 5The first finds issues you are watching. The second finds issues with more than 5 watchers. watcher > 5 and watchers = currentUser() both fail, for the reason each field was built for a different kind of value.
Searching by who is watching: the watcher field
| Query | Result on Jira Cloud |
|---|---|
watcher = currentUser() | Valid. Issues the current user is watching. |
issue in watchedIssues() | Valid. Same result as above, as a function. |
watcher in membersOf("group-name") | Valid, if the group exists. Issues watched by anyone in that group. |
watcher = "712020:xxxxxxxx-xxxx..." | Valid. A literal Atlassian account ID works, not just currentUser(). |
watcher is EMPTY / watcher is not EMPTY | Valid. Whether an issue has any watchers at all. |
Searching by how many are watching: the watchers field
| Query | Result on Jira Cloud |
|---|---|
watchers = 0 | Valid. Nobody is watching. |
watchers > 0 | Valid. At least one watcher. |
watchers >= 5 ORDER BY watchers DESC | Valid and sortable, highest watcher count first. |
watcher > 5 | Invalid: "The operator '>' is not supported by the 'watcher' field." Comparison operators belong to watchers, not watcher. |
watchers = currentUser() | Invalid: "A value provided by the function 'currentUser' is invalid for the field 'watchers'. Watchers must be a positive whole number." |
watcherCount > 0 | Invalid: "Field 'watcherCount' does not exist or you do not have permission to view it." There is no field by this name; use watchers. |
hasWatchers = true | Invalid: "'true' is a reserved JQL word." There is no boolean has-watchers field either. |
A bug to know about: "not watching" queries
Finding issues a specific person is not watching looks like it should be watcher != currentUser() or watcher not in (currentUser()). Both parse without error, but Atlassian has had an open bug against this since 2017: JRACLOUD-64143, closed in 2020 as "Timed out" rather than fixed. Per Atlassian's own reproduction steps, watcher != someUser only matches issues that already have at least one watcher who isn't that user — it silently excludes issues with zero watchers, which are exactly the issues where "someUser is not watching" is also true.
To get issues the current user is not watching, including ones nobody is watching, OR in the empty case explicitly:
watcher is EMPTY OR watcher != currentUser()This is a case where the query that reads most naturally (watcher != currentUser() alone) silently returns an incomplete result set, with no error to flag it.
Common questions
Can I see who is watching an issue, as a list, from JQL?
No. JQL can filter and sort by watchers, but the people's names only show in the issue view's Watchers panel (if "Watchers and Voters" is enabled in your project) or via the REST API's watches field on an issue.
Does querying another person's watcher status need extra permission?
watcher = someoneElse is a normal field query and does not require the "Manage Watchers" permission; that permission controls adding or removing other people's watches, not searching by them.
Can an Automation rule notify me when someone starts or stops watching?
No. Jira Automation's trigger list has no "watcher added" or "watcher removed" event, unlike comments or field changes, so there is no native way to react to a watch change in real time; only the stored watchers count is queryable after the fact.