Customer requests

What a customer asked for, logged where the team will see it.

Write down what somebody outside asked for, and attach it to the task that answers it.

The inbox, with requests not yet attached to any work
The inbox, with requests not yet attached to any work

Log a request

Say who asked and what they want. Mark it important if it is. New requests land in the inbox, newest first, with important ones lifted to the top.

There are two ways in, and they suit different moments. Writing from the inbox lets you name the customer as you type, inventing one if they are new. Opening a customer first and pressing Log a request settles who said it before you start, which is what you want when you are working through a call.

Attach it to work

Attach a request to an existing task, or create the task it needs. Attaching is what puts the count on the card: a task with eleven customers behind it looks different from one with none, and that difference makes a priority argument short.

Follow the demand

Once requests are attached, demand gathers them by epic so you can see what is being asked for most.

Common questions

Can one request point at more than one task?

No. One request answers one piece of work. Log a second if they truly differ.

What happens to a request when its task is deleted?

It returns to the inbox, untriaged, so it is not lost with the task.

What is the source for?

Where they said it: email, Slack, a call. The chips offered are the ones this workspace already uses, and you can type a new one.