Working hours and reachability | kanman documentation

kanman works like a predictable colleague: the team decides when it works, how soon it answers, and that it does not open pull requests or ping people in the evening. All of this lives in Team > Hours and rhythm (/<workspace>/teams/<team>/team/hours), together with the team’s rituals, the delivery review and the retrospective. Every change saves at once: Saved shows next to it, and Undo brings the previous value back.

Working hours

Under Working hours, choose Any time or Only during working hours and a time zone. A week strip shows the team’s week at a glance:

Working hours as a band on each day. Drag either end to change the times, or focus an end and use the arrow keys. Click a day to switch it on or off.
Quiet hours in chat as a hatched band. They are edited here as well and keep kanman from posting unprompted in the team’s Slack or Microsoft Teams places.
On-call hours of each of the team’s services as a dotted band, linked to the service, where you change them.

If you prefer to type the times, open Edit as times. kanman starts new runs only inside the working hours; runs in progress finish. Expedite stories and incidents start any time.

Response times

Under Reachability, set how soon the team can expect kanman’s first answer:

First answer to a mention, in working hours (default 4)
First review of a requested pull or merge request, in working hours (default 8)

Outside working hours

With Hold PRs/MRs (as drafts), reviews and pings until the hours start (the default), kanman stays quiet outside the working hours:

A pull or merge request it opens in the evening is opened as a draft. When the working hours start, kanman marks it ready for review, so reviewers are asked during the day.
A code review requested in the evening is posted when the working hours start.
Decisions are posted to Slack when the working hours start; in the app they are there at once. Decisions that cannot wait (production data, security, spending or budget stops, a red main branch, a revert, an incident, a check that stopped a running change, a paused team, a problem that holds up all of a team’s work) are posted at once.
In Slack and Microsoft Teams, kanman says nothing unprompted.

kanman always answers people who write to it directly, and urgent work never waits: expedite stories and incidents go out at once. Choose Reach out any time to switch the rule off. Without working hours, there is nothing to hold.

Pausing the team

A pause is not a setting you look for. In the team header, next to the team’s status line, a pause button stops kanman for the team at once: running work finishes, nothing new starts. The status line then reads Paused · Resume, and Undo in the message takes the pause back. You can also ask kanman in the chat, for example “pause the team until the token is rotated”. While the team is paused, Hours and rhythm says since when.

Handoffs

When a story waits on people, for example for an answer or for access, the story’s card in the chat carries one clear note: what is needed, from whom (you, the story’s owner, or the team) and since when, and that everything else is ready. The decision’s buttons are right below it. The note goes away when the question is answered, and the work goes on.

Daily update

Switch on Daily update to get one short message per working day: how many stories were merged, how many are in review, runs that stopped, decisions that wait and open incidents. Choose the time and where it goes:

Team chat: everyone who follows the team gets it in the team’s chat.
The team’s Slack channel: posted to the channel the team connected (see Slack and Microsoft Teams), inside the channel’s quiet hours.

On a day with nothing to say, there is no update. It never comes on a day outside the working hours.