Watchers
Retrieves the list of users watching specific issues for updates or changes.
Select
The server will use the Jira APIs to process filters based on IssueId or IssueKey. One of these is required to retrieve results. IssueId and IssueKey can be used only with the equal (=) operator.
The server will execute other filters client-side within itself.
For example, the following query is processed server side:
SELECT * FROM Watchers WHERE IssueId = '10100' SELECT * FROM Watchers WHERE IssueKey = 'PRJ-1'
Columns
| Name | Type | References | SupportedOperators | Platform | Description |
| DisplayName | String | Common | The full display name of the user who is watching the issue. This name appears in the Jira UI wherever watchers are listed. | ||
| EmailAddress | String | Common | The email address associated with the user's Atlassian account. Used for notification purposes when changes occur on the watched issue. | ||
| AccountId [KEY] | String | Cloud | The globally unique identifier for the user watching the issue. This ID is consistent across all Atlassian cloud products and replaces legacy identifiers. | ||
| Key [KEY] | String | Server | The legacy key of the user who is watching the issue. Included for backward compatibility in older Jira versions. | ||
| Name | String | Server | The legacy username of the watcher. This can be used in Jira Server environments but is no longer supported in Jira Cloud. | ||
| IssueId | String | = | Common | The internal numeric ID of the issue being watched. Primarily used in backend processes and integrations. | |
| IssueKey | String | = | Common | The human-readable key of the issue being watched (such as 'PROJ-101'). This is what users typically see in the Jira interface. |