Key Takeaways
- In ticketing and issue tools, a watcher gets notified about an item without owning it.
- The assignee does the work; watchers follow along.
- In code, a watcher is a process or function that runs when files or data change.
- Webhooks are the cross-system version: another system 'watches' for an event and gets a call.
What Is a Watcher?
A watcher is anyone - or anything - that follows an item and is told when it changes. The word has two common meanings:
- In support and project tools (Jira, help desks, ticketing systems): a person subscribed to a ticket or issue who receives updates but is not responsible for it.
- In software: a process or function that monitors files, data or state and runs code when it changes, such as a file watcher that rebuilds an app on save.
Watcher vs Assignee vs Requester
| Role | Responsibility |
|---|---|
| Requester | Raised the ticket and is kept informed |
| Assignee | Owns the work and resolves the item |
| Watcher | Follows updates, can comment, owns nothing |
Adding a manager or a colleague as a watcher keeps them informed without changing who is accountable. It is common when a chatbot hands a conversation to a person and a team lead wants visibility.
Watchers in Code
File watchers (for example Node's fs.watch or tools like nodemon) restart or rebuild an app when source files change. Front-end frameworks such as Vue offer watchers that run a function when a reactive value changes. Between systems, a webhook plays the same role: instead of checking repeatedly, your server is called when the event happens.
Frequently Asked Questions
What is a watcher in Jira?
What is the difference between a watcher and an assignee?
What is a file watcher?
How is a watcher different from a webhook?
Free plan, no credit card required.