Projects lists every project you can open: the Public ones, your team's, and the Private ones you're listed on. Organisation Owners and Admins see every project, and they also get the Archived and Deleted tabs; everyone else sees the active list only.

Find a project

1. Type in Search by name or key, or narrow the list to one pod (All pods).
2. On a wide screen, switch between Cards and List. Flow remembers your choice; a phone always shows compact cards.
3. Each project's ⋯ menu has Open board and Backlog, plus Project settings for the project's leads (Product Owner, Scrum Masters, Owners and Admins).

Create a project

1. Click New project. It's there for Owners and Admins, and for a Member given the Create projects permission for the whole organisation through a custom role — in organisations that have the built-in Agile coach role, it includes this. A Stakeholder never creates projects.
2. Fill in the dialog as in Step 10 · Create a project.

Archive, delete and restore (Owners and Admins)

1. ⋯ › Archive project…: the project becomes read-only, leaves the active list and stops counting against your plan's project limit. It still opens from the Archived tab.
2. ⋯ › Delete project…: the project moves to Deleted. It can be restored for 90 days, then it's removed for good with its sprints, work items and comments.
3. On the Archived or Deleted tab, Restore brings a project back. From Archived it returns to the active list (and counts against the limit again); from Deleted it returns too — but a project that was archived when it was deleted comes back archived. The Deleted tab shows how long each project has left under Removed for good in.

Delete a project for good (Owner only)

1. On the Deleted tab, click Delete forever… next to the project.
2. Type the project's key to confirm, then click Delete forever. Every sprint, work item, comment and attachment in it is deleted at once — this can't be undone.

The backlog is the project's list of work waiting to be done. Its shape follows the project's board type.

Read the list

1. Scrum: one section for each open sprint (marked Active or Planning), then the Backlog section for everything not planned yet. Completed sprints stay out of the way until you click Show N completed sprints.
2. Kanban: one ordered list — the top is pulled next. Show switches between Not started (the default), In progress and Finished.
3. The Product Goal card at the top shows the project's longer-term aim — see Product Goal.

Filter and save views

1. Type in Search by title or key, or open Filters: Type, Priority, Assignee, Label, Size, Track, Fix version, Component (for people who can edit work items) and Flagged. Each active filter shows as a chip under the toolbar; its × removes it.
2. Open View › Save current filters as a view… and name it. Your views — and any shared with the project — are listed under Views; pick one to apply it, or All work items to clear it.
3. The Product Owner, Scrum Masters and Admins can share a view with the whole project (tick Share with the project when saving, or choose it from the View menu); Developers and Stakeholders keep their views private. The same menu has Rename, Stop sharing and Delete view.

Order the backlog

1. Drag a row by its grip to a new place in its section — or use the row's ⋯ › Move to top, Move up one, Move down one or Move to bottom.
2. From the keyboard: Space on the grip lifts the row, ↑/↓ move it, Space drops it and Esc cancels.
3. To move an item into a sprint (or back), use the row's ⋯ › Move to and pick a sprint or Backlog.

Change several items at once

1. Tick the box on each row (or the box at the top of the list to select them all). A bar appears at the bottom.
2. Use Move to (a sprint or the Backlog — Scrum projects), Assign, Priority or Type. Subtask isn't offered as a type, because a subtask needs its own parent.
3. The × on the bar clears the selection. The boxes are there for people who can edit work items.

Work breaks down in three levels. Flow checks these rules every time a parent or type changes, so the structure always stays tidy.

Break an epic down

1. Open the epic. Under Child work items, click Add child work item: the create dialog opens with the epic as parent and the type set to Story (change it to Task, Bug or Spike if you like).
2. Or open an existing story, task, bug or spike and pick the epic in its Parent field.
3. The children list shows how many of them are done.

Add subtasks

1. Open a story, task, bug or spike. Under Subtasks, click Add subtask.
2. A subtask always needs a parent: it can't lose its parent, and it can't be bulk-set as a type or imported from our CSV template.

Change a parent or a type

1. In Parent, pick another item — only items of a type that fits are offered — or remove the parent with its ×.
2. In Type, types that don't fit the current parent are shown but can't be picked. For example, a story under an epic can't become an epic or a subtask until you remove or change its parent.
3. If the item's children wouldn't fit the new type, Flow refuses the change and says why.

Product Owners, Scrum Masters, Developers and organisation Owners and Admins create work items. A Stakeholder can only if an admin gives them a custom role with Create work items (see Custom roles).

Create from the backlog

1. Click Create work item at the top right of the backlog (Create on a phone).
2. Pick the Type and write a Title — "What needs to be done?" Set the Priority, and for a bug its severity.
3. Check the Stage it starts in and, on a Scrum project, the Sprint (Backlog or an open sprint).
4. Choose the Assignee — required if you can choose who work is assigned to. Assign to me is one click.
5. Optional: Size, Track, Story points, Start and Due date, Components, Labels, Parent, Flag as impediment, Linked work items and Description. Then click Create work item.

Who it is assigned to

1. Everyone except Stakeholders can choose the assignee (a Stakeholder can with a custom role that includes Choose who a work item is assigned to). Without that choice the dialog says "You can't choose who it's assigned to".
2. Picking a component that has a lead fills in the lead as the assignee. If you can choose the assignee you can still change it; if you can't, the component's lead becomes the assignee.

Other places to create

1. On the board, a column's Add work item to … button creates the item straight into that stage (on a phone, the bar at the bottom).
2. On an open item, Add subtask or Add child work item creates the item with its parent already set — see Epics, stories & subtasks.

Clone a work item

1. Open the item. At the top, next to Copy link, click the Clone work item button (two overlapping squares).
2. Edit the Title if you like, and on a Scrum project choose the Sprint — the backlog or an open sprint. If the item has children, tick Include N child work items to copy them too.
3. Click Clone. The new item has the same details, starts in the first column and opens straight away. Comments, history, time logged and attachments are not copied.

Delete a work item

1. Open the item and click ⋯ (More actions) at the top, then Delete work item….
2. Confirm with Delete work item. The item leaves the board, the backlog, its sprint and the reports. There's no undo in the app.

Bring existing work into a project in one go, from a spreadsheet or from another tool's CSV export. Import CSV is in the backlog's ⋯ menu for people who can edit work items, and it offers two choices: a CSV export from another tool, or our CSV template.

Import with our CSV template

1. Choose the template option, then Download CSV template and fill it in.
2. Columns: title (required), type (EPIC, STORY, TASK, BUG or SPIKE — TASK if empty), priority, storyPoints, description, labels and dueDate (YYYY-MM-DD) — the downloaded template's header row, in that order. labels are separated by semicolons. You can add a components column yourself (optional; semicolon-separated names of this project's components). Subtasks can't be imported this way.
3. Drop the file in (up to 2 MB). Rows are imported straight away; any row imported with something left out (an unknown component name, say) is listed as a warning.

Import a CSV export from another tool

1. Choose the CSV-export option and upload a file with columns such as Summary, Issue Type, Status and Assignee (up to 10 MB). Summary is required: a row without one is skipped. Priority, description, labels, sprints, fix versions, due date, parent, story points and comments are read too.
2. Flow reads the file and shows a mapping. Match its Work item types, Priorities, Statuses → workflow stages and People → project members, and decide on sprints, comments and fix versions. Nothing is imported until you click Import.
3. Running the import is for the Product Owner, a Scrum Master or an Admin. Developers can upload a file and review the mapping.
4. The result counts what was imported, skipped as already imported or invalid, and the sprints, versions, comments and parent links created.

Export to a CSV file

1. Set the search and filters you want, then choose ⋯ › Export CSV. The file holds the work items that match.
2. Anyone who can open the project can export what they can see. If too many items match, Flow tells you how many it exported — narrow the filters to export the rest.