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.
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.
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.