For licensed Collaborators with permission for this task. Check the selected organisation; feature availability and record access still apply.
What you will achieve
Create a project, group related work and record tasks that people can act on. The reviewed epic editor calls these groups Swimlanes; use the label you see in the interface.
Before you start
Agree the project's outcome, boundaries, responsible team and target date. Identify who can change the plan and what evidence will establish completion. Check for an existing project before creating another.
Set up the project
- Open the project catalogue and choose Create Project.
- Enter the name, code and description. Explain the outcome and exclusions, not just the activity.
- Choose the supported status and priority, then set start and target dates.
- Select Project Owner Team where appropriate and add useful tags.
- Review compliance, strategic and public-visibility options deliberately. Do not make a project public simply to make it easier for colleagues to find.
- Create the project and reopen it. Confirm ownership/accountability through its available team and RACI controls.
Structure actionable work
Open Tasks. Where grouping is useful, create a Swimlane with a clear title, description, status, priority and dates. The underlying epic groups related tasks; it is not proof that any of them are complete.
Use Create Task in the project context. Write an action-oriented title and a description explaining the expected result and completion evidence. Review priority, status, start/due dates and effort size.
Assign responsibility through the available task controls. If using recurrence, review the recurrence pattern and end conditions. Check milestone and completion-notification options before saving.
Move or group tasks only when the resulting organisation makes sense to the people doing the work.
Check it worked
Reload the project and open a saved task. Confirm its parent project, grouping, dates and responsibility. Ask the intended person to find it in their own work view.
Check that the project outcome still has a verification plan; a board full of completed tasks is not automatically an achieved outcome.
If something goes wrong
| Problem | Next action |
|---|---|
| A task is in the wrong context | Correct its supported relationship before others act on it |
| A person cannot find the task | Check assignment, organisation, filters and access |
| A date is unrealistic | Agree the change with the owner and update dependent work |
| Recurrence creates unexpected work | Review the recurrence settings before creating more copies |
Human judgement matters
Status changes communicate progress but do not establish acceptance. Agree who checks the result and keep that evidence with the work.
What next?
For the wider context, see Manage projects, goals, assets and knowledge.
Use the time-recording guide where required and review the project's risks, dependencies and success measures.
Get help
Ask your Organisation Administrator about access or the task owner about the content. For a platform error, include this guide reference, the affected page and a sanitised message, not confidential evidence or session details.