Short definition
A watcher in Jira is a user who has subscribed to an issue and receives email notifications when it changes. Watchers can be added explicitly or auto-added by Jira (assignee, reporter, voters, depending on the project's notification scheme). Watchers don't gain any extra permissions; they just get notifications - and watching is the most common way users keep tabs on issues without being assigned to them.
Watchers vs. the notification scheme
Most teams treat watching as the only way they get Jira email, but it’s actually one row inside a bigger configuration:
- Notification Scheme - a per-project mapping of events to recipients. Examples: “Issue Created” notifies Reporter, Assignee, and All Watchers; “Issue Resolved” notifies the same plus the original reporter and the project lead.
- Watching - one specific recipient list within the scheme. A user on the watcher list gets every event that the scheme routes to All Watchers.
This is why removing yourself from the watcher list doesn’t always stop notifications - if the scheme also notifies the reporter and you’re the reporter, you’ll still get email. To stop notifications entirely, you have to either reassign the reporter (unusual) or filter the email client-side.
Adding watchers
Three ways:
- Click the watcher count on the issue - manually pick users.
- Via the REST API -
POST /rest/api/2/issue/{key}/watcherswith a username. Used heavily in automation rules. - Bulk - through a plugin like Watch It, which adds JQL-based bulk-watch and per-component watch lists, so an incident commander can subscribe a whole team to a P1 ticket in one click.
Default watchers and the surprise problem
Some projects’ notification schemes auto-add the reporter to the watcher list on issue creation. Others don’t. The user can be on the watcher list of issues they don’t remember subscribing to, or not on issues they thought they were following. Two practical tips:
- Document the project’s notification scheme behaviour somewhere the team can find it. Most teams don’t, and surprise stops trust in Jira email entirely.
- If notifications are noisy, audit the notification scheme first, then trim the watcher list. Most “Jira is spammy” complaints are about the scheme, not about watching.
Watching and permissions
Watching an issue does not grant access to see it. If a user is added as a watcher on an issue they don’t have permission to view, they won’t receive notifications (Jira silently filters them out). This is intentional: notifications shouldn’t be a back-channel for confidential issue content.
Watching for incident response
Incident response is the use case where bulk-watch matters most. When a P1 ticket opens, the on-call commander wants to subscribe the entire response team in seconds, not click through 15 add-watcher dialogs. The same pattern shows up in customer escalations, executive-visible bugs, and security incidents - any situation where a single ticket needs many eyes for a short time.
Common questions
What does watching a Jira issue do?
Watching an issue subscribes the user to notifications about it - new comments, status changes, field edits, attachments, work logs. Watchers don't get any extra permissions; they only see what they could see anyway. Watching is the lightest-weight way to follow an issue without being the assignee or reporter.
Who gets notifications about a Jira issue?
It depends on the project's Notification Scheme, which maps events (issue created, commented, transitioned, resolved) to recipients (reporter, assignee, watchers, current assignee, project lead, specific groups). Watching is just one entry in that scheme. Different events can notify different recipients.
How do I add multiple watchers to a Jira issue?
From the issue, click the watchers count -> Add watchers -> type each username. There's no bulk-watch UI in standard Jira, which is the gap watch-it apps fill. Most useful when many people need updates on a single high-impact issue (an incident, a customer escalation, a release-blocking bug).
Can I watch all issues in a project automatically?
Not directly. The Notification Scheme can send all events to a group or role, which is functionally similar (everyone in that group gets notified). For per-user 'watch the whole project,' Watch It adds bulk-watch via JQL and per-component watch lists.