The journeys
Eleven walkthroughs. Each one is a job you actually want to do, start to finish, with the screen to look at when you want to know it worked.
They are in order. If you have never opened Projects, do the first three in one sitting and you will have a board with work on it and a week running.
An organisation, a project, its key, its people, and the first items on a board.
Drag, keyboard, a refused drop, and who moved it.
Pull work in, run it, close it, carry the rest.
The gate, who may open it, and why the author cannot.
Type @, they hear it once, and it clears when they read it.
Draft, review, decide, sign off, and the epics it mints.
Bars, deadlines, arrows, and dragging a date.
One row, two boards, and the label a linked issue is given.
Ready, claim, move, and why everything it finishes waits.
One import, run by an administrator, safe to run twice.
A year, a quarter, a week — and the one piece that is missing.
How to read a journey
Each one has the same four parts.
What you will have done opens the page, so you can tell in one line whether this is the journey you want.
The walkthrough is numbered steps, each with the screen it happens on.
A worked example follows Meridian Supply through the same steps, so you can compare what you see against what the page says you should see.
What can go wrong closes the page: the sentence the screen puts in front of you, and what to do about it.
Last updated on