Create a process
Define the phases and checks every contribution on your team moves through.
A process is the route every contribution on your team follows. You define the phases, and the checks inside each phase, so every component is held to the same bar.
Each team has its own processes. A component follows one process at a time.
Before you begin
You need the Admin or Editor role on the team. A Viewer can read processes but not create or change them.
Create the process
Open the team's processes
Go to your team and open Processes.
Choose a starting point
Open GET A HEAD START and pick one:
- Use Our Process — opens a ready-made process with four phases you can adapt. Choose USE TEMPLATE on the card. This is the quickest route, and the one the Quickstart follows.
- Create From Scratch — opens an empty editor.
Tips and Tricks on the same panel opens this documentation.
Name the process
Fill in Process name, and a Description if it helps the people who will follow it.
Write the phases
A phase is one stage of the work, such as Prepare Design or Docs and testing. Give each phase a name and, underneath it, a short paragraph saying what happens in it.
Phases run in the order you write them.
Write the checks
The editor is a document, so you write checks as checklist items under a phase. Each item is one thing somebody has to do.
Give a check a short name on its first line, and add a sentence underneath explaining what "done" means. That sentence is what a contributor reads in the widget, so write it for them, not for yourself.
Publish
Choose Publish.
While you are still writing, the editor shows draft saved and nobody else is affected. Publishing is what makes the process available to contributions.
Expected result
The process appears on your team's Processes page. When someone adds a component and picks this process, the component starts in the first phase, and the widget shows the phases and checks you wrote.
How a change reaches contributions that already exist
You can keep editing a process after publishing it. Changes reach existing contributions the next time somebody opens one, not instantly.
When a contribution is opened and its process has moved on, Compfeed rebuilds that contribution's document from the current process. Your phases and checks replace the old ones.
Notes written against a phase or a check that no longer exists are not thrown away. They are moved to the end of the document, under a heading reading Notes from deleted phases or tasks.
Once a process is published, only a team Admin can change it. An Editor can create a process and edit it while it is still a draft, but not change it afterwards.
If something doesn't work
- The cards on GET A HEAD START are greyed out: you have the Viewer role on this team. Ask a team admin for Editor.
- You cannot save a change to a published process: only admins can. See the note above.
- Anything else: see Troubleshooting.