Copied on the Task, Not Assigned to It
A manager who needs to know when a task moves is usually made its owner, because owning is the only relationship most tools know how to notify. That gives the task two owners and the team twice the noise. Watching is a different relationship, and it is worth being precise about who hears what.
A supplier disputes a delivery, and somebody has to recount bay fourteen before the credit note can be agreed. The task goes to the warehouse supervisor, because she has the keys and the count sheet. The procurement lead does not need to do anything, but she cannot answer the supplier until the count is done, and she does not want to ask twice a day. So she asks to be put on the task. In most tools that means one of two things: she becomes a co-assignee, and now the task has two owners and nobody quite knows whose it is; or somebody promises to “keep her in the loop”, which means a message she will have to chase.
The short version, first
Owning a task and following it are different relationships, and a system should notify them differently. In AWRA OpsHub anyone who can see tasks can watch one, from the task page or the mobile app. A watcher hears when the task changes status and when someone comments on it, and holds no responsibility for the work. The assignee hears when the task is assigned to them, when its status changes and when it falls due. Nobody is ever notified about their own action. Each kind of notice has its own row in the workspace’s notification settings. The parts still to build are mostly at the edges: the assignee is not told about comments unless mentioned, a bulk status change does not reach watchers, and a watcher who leaves stays on the list.
Three relationships that get collapsed into one
Work-tracking tools tend to start with one relationship, the assignee, and then bend it to cover everything else. If you want to hear about a task, get yourself assigned. If two people need to hear, assign two people. The result is familiar to anyone who has tried to run a weekly review off a task list. Half the open items have a manager listed beside the person actually doing the work, nobody can say who is accountable for the overdue ones, and the manager’s “my tasks” list is full of work she is not doing.
Underneath that, there are at least three separate things a person can be to a task, and they call for different notices.
Owning it
- You are the person the work is waiting on.
- You need to know when it is given to you, when it moves and when it is due.
- The task appears in your own list of work, and its deadline is yours.
- There should be exactly one of you.
Following it
- Something you are responsible for depends on this task finishing.
- You need to know when it moves and when somebody says something about it.
- You have no deadline on it and should not appear as doing it.
- There can be as many of you as the work affects.
The third relationship is narrower: being asked. Somebody writes a comment, puts your name in it, and wants an answer from you on this one point. That is neither owning nor following, and you should hear about that comment and nothing else on the task.
Who hears what, event by event
The useful way to describe a notification design is as a table: for each thing that can happen to a task, who gets told. This is that table for the product as it stands, read from the code rather than from the settings screen.
| What happens | The assignee | Watchers | Someone @mentioned |
|---|---|---|---|
| The task is created with an assignee, or reassigned | Told it was assigned to them | Not told | Not applicable |
| The status is changed on the board, the task page or the app | Told it moved, and to which column | Told it moved, and to which column | Not applicable |
| Someone comments | Not told, unless mentioned | Told there is a new comment | Told they were mentioned |
| The due date approaches or passes | Told it is due soon, or overdue | Not told | Not applicable |
| Several tasks are moved at once from the task list | Told it moved | Not told | Not applicable |
Three rules sit underneath the table. First, the person who did the thing is never told about it. If the supervisor moves the recount to Done, she gets no notice saying so. The same goes for a watcher who comments on a task, or someone who mentions themselves. Second, a watcher who is also the assignee hears only as the assignee, so nobody gets two notices for one change. Third, every task notice is addressed to one person. It lands in that person’s bell and nobody else’s, so a message that says “your task is overdue” is never shown to a colleague who cannot open the task.
In the opening scene, then, the procurement lead presses Watch on the recount. When the supervisor moves it to In Progress, the procurement lead gets “A task you’re watching, ‘Recount bay 14’, was moved to In Progress”. When the supervisor adds a comment saying two pallets were double-stacked, the procurement lead hears that too. The supervisor is still the only owner, the deadline is still hers, and the procurement lead’s own list of work has not grown by one.
If assigning someone is the only way to keep them informed, every interested person becomes an owner, and then the task effectively has no owner.
Following is chosen by the follower
Watching is something you do for yourself. The Watch button adds or removes the person who pressed it. Nowhere in the product, on the web or in the app, can you subscribe somebody else. That is a deliberate restriction. Allowing people to subscribe colleagues is how a task ends up with eleven followers, nine of whom never asked to be there and have learned to ignore it. If you want somebody else to see a particular comment, the tool for that is a mention, which reaches them once, about that one comment.
Watching is also visible to everyone. The task page shows a count on the Watch button and a card listing each watcher by name, to anyone who can open the task. The supervisor can see that procurement is following the recount. That matters more than it sounds: being followed by someone who has said nothing is uncomfortable, and showing the list is what makes following read as the courtesy it is meant to be.
Watching gives you no right to change the task. In the mobile app, a watcher can open the task, comment on it and stop watching it, but adding a checklist item or otherwise changing the work stays with the assignee, even for someone who holds broader edit rights on the web. That rule is tested directly. Watching is a way to be informed and to join the conversation, not a second route to editing.
How a mention finds a person
A mention is written as @ followed by a first name, and it matches every person in your workspace with a login whose first name is that word, ignoring case. That keeps it quick to type and means nobody has to remember a username. It also means that in a workspace with two people called Grace, writing @Grace notifies both of them. Until mentions can match a full name or a pick from a list, the practical habit is to mention people whose first name is unique, and to put anything that must reach one specific person in a status change or an assignment.
The noise problem, and who controls it
Every notification system ends up in the same place. The more people you notify, the less any one of them reads. Notifying everyone produces silence just as reliably as notifying nobody, only more slowly. The defence is not a smarter filter applied later. It is to work out, when the notice is sent, which relationship each recipient has to the task, and to send each of them only what that relationship needs.
In the workspace’s notification settings, under Projects & tasks, each of the five kinds of task notice has its own row: assigned to you, status changed, due soon or overdue, mentioned, and updates on tasks you watch. Each row has an in-app switch and a push switch. In-app means the bell on the web and in the app. Push goes only to the recipient’s own registered staff devices, never to everyone’s. If your workspace has connected a chat channel and enabled it for this module, the notice is also forwarded there. Task notices are not sent by email.
Those switches apply to the whole workspace. An administrator can turn off push for watched-task updates for everyone, but an individual cannot turn off one kind of task notice just for themselves. A person’s own control is the relationship: if a task you are watching has stopped mattering to you, you unwatch it. That is the right control for most cases, because “stop telling me about this task” is a far more common wish than “stop telling me about every comment, everywhere”.
You need to hear when it moves, but the work is not yours
Watch it
Status changes and comments reach you, and you stay out of the task’s ownership and out of the owner’s list of work.
You need one answer from one person on one point
Mention them in a comment
They hear once, about that comment, and can open the task from the notice to reply, even in the app.
The work is genuinely theirs to do
Assign it
They hear about assignment, every status change and the due date. Keep it to one assignee, so it is clear who the work is waiting on.
A watched task has stopped mattering to you
Unwatch it
Press the same button again. Nobody else is affected, and the task’s watcher card updates for everyone.
Where the design is still thin
Three of the rules above follow from decisions that are reasonable but incomplete, and you should know them before relying on watching to keep a manager informed.
The assignee is not told about comments. The code assumes the person doing the work is watching the task anyway. Sometimes that is true. Often it is not: a supervisor on the warehouse floor does not refresh a task page. Watching your own task does not change this, because watcher notices skip the assignee to avoid sending two. In practice, a question for the assignee needs to mention them by name.
Some status changes do not reach watchers. A status change from the board, from the task page or from the app is sent to watchers. A status change made to several tasks at once from the task list tells each assignee, but not the watchers. And an edit that reassigns a task and changes its status in the same save sends only the assignment notice, so neither the new owner nor the watchers hear that it moved. Both are ways a careful follower ends up missing exactly the change they were watching for.
The creator is not a watcher by default. A task records who created it, and that person may well be the one who most wants to know when it finishes. But they are not added as a watcher unless they press the button themselves. Whether creators should follow automatically is a matter of preference, and it should be a workspace setting rather than something built in.
What follows a person when they move on
A watcher is recorded against a login, and the record stays until that person unwatches or the task is deleted. Nothing removes it when someone changes role, loses permission to view tasks, or leaves. In the app, being a watcher is itself enough to open the task. That was deliberate: people tapped a notice about a task they watched and got “Couldn’t load task”. The side effect is that someone who started watching while they had broad access keeps reading that task on their phone after the broader access is removed.
For most workspaces this barely matters, because a departing person’s login is deactivated and that is the end of it. It matters for the case it is easiest to overlook: someone who moves to another department and keeps their login. A review of who is watching what should be part of every role change, and until the product does that review itself it is a manual step worth adding to your role-change checklist. There is also no screen listing the tasks you are watching. My Tasks and its saved views show tasks assigned to you, so a person cannot easily see everything they are following either. Both are covered on the task management feature page in their current form, and both are on the list below.
Five changes that make following as reliable as owning
Listed roughly in order of how often each one would have changed what someone heard about a task.
Comment notices for the assignee
The person doing the work hears when somebody comments on their task, under its own row in the settings so a workspace that prefers quiet assignees can switch it off.
Watcher notices on every status path
A bulk status change and an edit that reassigns and moves in one save both reach watchers, worded the same as a move on the board.
A watcher review on a change of access
When someone loses permission to view tasks or is deactivated, their watcher rows are listed for an administrator to confirm or clear, and the mobile read grant follows the decision.
A list of the tasks you watch
A tab beside My Tasks, with the same filters and saved views, so following is something you can review and prune from one place.
Per-person preferences and creator auto-watch
Each person can quieten one kind of task notice for themselves within what the workspace allows, and the workspace can choose to have creators follow the tasks they raise.
The first two are small and change what reaches people on the day they ship. The third is a policy decision as much as a feature, which is why it puts the choice in front of an administrator rather than clearing watchers automatically. The fourth and fifth are what make following manageable for someone who follows forty tasks.
Tell us how your team follows workFour questions for any tool that promises to keep people informed
Can someone hear about a task without being assigned to it?
What you will probably hear
Yes, you can add them to the task.
How to read it
Ask whether “added” means assigned. If the only way to be informed is to appear as an owner, accountability blurs as soon as more than one person cares about the work.
Who exactly is told when someone comments?
What you will probably hear
Everyone on the task.
How to read it
Ask whether the person commenting is excluded, and whether owners and followers are told differently. “Everyone” is how people learn to ignore the bell.
Can I subscribe a colleague to a task?
What you will probably hear
Yes, from the task page.
How to read it
Convenient, and the usual source of followers who never chose to follow. Ask whether a one-off mention would do the job instead.
What happens to followers when someone changes role?
What you will probably hear
Permissions are handled centrally.
How to read it
Ask whether following is checked against permissions when each notice is sent, or only when the person started following. In many tools, including this one today, it is checked only at the start.
What AWRA OpsHub does today
- A Watch button on every task, on the web and in the mobile app, that adds or removes only the person who pressed it.
- Watcher notices on status changes and comments, never sent to the person who acted and never duplicated for a watcher who is also the assignee.
- Assignee notices on assignment, on a status change, and when the task is due soon or overdue.
- Mention notices for anyone named in a comment by first name, which also let that person open the task in the app.
- One recipient per notice, so a personal task notice appears in its addressee’s bell alone.
- Five settings rows under Projects & tasks, each with its own in-app and push switch for the workspace, with push sent only to the recipient’s own devices.
- A watcher card on the task page, naming everyone following the task to anyone who can open it.
- Watchers can read and comment but not change the work, enforced in the app and covered by a test.
More we can add to your workspace
- Comment notices for the assignee, so the person doing the work hears when someone asks them something without having to be mentioned.
- Watcher notices on bulk status changes, and on an edit that reassigns and moves a task in one save.
- Creators following their own tasks automatically, as a workspace choice.
- Per-person notification preferences for task notices, within the limits the workspace sets.
- A list of the tasks you are watching, with the filters and saved views My Tasks already has.
- A review of a person’s watched tasks when their access changes, with the mobile read grant following the outcome.
- Mentions by full name or from a pick list, so two colleagues who share a first name can be told apart.
- An email digest of watched-task activity, for followers who do not keep the app open.
Where we point you to a specialist
- We will not let one person subscribe another to a task. Following is a choice the follower makes, and a mention already exists for the case where somebody needs to see one particular comment.
- We will not notify a person about their own action on any channel. The notice exists to tell you what someone else did, and a copy of your own work in your bell teaches you to ignore the bell.
The first two items are small and change what reaches people the day they ship. The access review is the one we would scope first for an organization where staff move between departments, because it closes the one path by which a task stays readable after the access behind it has gone. The watching list and per-person preferences go together, and the digest makes sense once those two exist.
Tell us who needs to hear about your work
Most notification complaints come down to one relationship being stretched over three. If your managers are listed as assignees on work they only need to follow, or your teams have stopped reading the bell, we would like to hear how you would want each relationship notified.
Talk to us about your workspaceFrequently asked questions
What is the difference between watching a task and being assigned to it?
The assignee owns the work. They are told when it is assigned to them, when its status changes and when it falls due, and the task appears in their own list. A watcher owns nothing. They are told when the status changes and when someone comments, and the task does not appear in their list of work.
Can I add a colleague as a watcher?
No. The Watch button only adds or removes the person who presses it, on the web and in the mobile app. To bring a colleague into a particular conversation, mention them by first name in a comment, and they will be told about that comment.
Am I notified about changes I make myself?
No. Every kind of task notice skips the person who made the change, whether they are the assignee, a watcher or someone who mentioned themselves.
Can a watcher change the task?
Watching gives no right to change anything. In the mobile app a watcher can open the task, comment on it and stop watching it, while changes to the work itself stay with the assignee.
How do I stop task notifications?
For a single task, unwatch it. For a whole kind of notice, an administrator can switch its in-app or push channel off in the workspace notification settings under Projects and tasks. Those switches apply to everyone in the workspace.
Does the assignee hear about new comments?
Only when they are mentioned in the comment. Watchers are told about every new comment, but the assignee is not, so mention the assignee by first name when you need an answer from them. Telling the assignee about every comment is on the list of things we can add.
