Projects
Plan and deliver a defined outcome with Projects.
Field inspection rollout
Give field teams one place to capture inspection photos, record findings, and review completed reports. Start with a pilot, then roll out the workflow across all sites.
Latest update
The pilot is underway at two sites. Teams are capturing photos and reviewing findings in the new workflow, with the first reports ready for review.
- Photo guidelines and the inspection checklist are ready.
- Next: collect pilot feedback and prepare the remaining teams.
Overview
Projects bring together the work needed to deliver a clear outcome, such as launching a service or improving an existing workflow. Use a Project to keep the description, responsible people, dates, Issues, and supporting Documents in one place.
A Project can involve several Teams and sit within an Initiative. Break delivery into Phases, follow progress through linked Issues, and use Activity to see what changed.
Field inspection rollout
Give field teams one place to capture inspection photos, record findings, and review completed reports. Start with a pilot, then roll out the workflow across all sites.
Latest update
The pilot is underway at two sites. Teams are capturing photos and reviewing findings in the new workflow, with the first reports ready for review.
- Photo guidelines and the inspection checklist are ready.
- Next: collect pilot feedback and prepare the remaining teams.
Project guides
Initiative and Project updates
Report health and discuss progress.
Project milestones
Plan and track delivery stages.
Project overview
Read the plan, properties, resources, and progress.
Documents
Keep supporting material with a Project.
Project graph
Explore Project and Initiative relationships.
Project status
Track a Project through its lifecycle.
Project labels
Categorize and filter Projects.
Project notifications
Follow Activity and update reminders.
Project priority
Compare the urgency of planned work.
Project dependencies
Show what blocks or depends on a Project.
Project templates (coming soon)
Reusable structures for new Projects.
Customer Requests (coming soon)
Customer feedback linked to Projects.
Sections marked (coming soon) describe unavailable features. They do not have a release date here.
Create a Project
Open Projects and select New project. Enter a title and choose a Team. Add a short description so other people can understand the intended outcome without opening the full plan.
Before selecting Create project, you can set the status, priority, lead, members, additional Teams, labels, dates, and Initiative. Leave an idea in a Backlog status and choose a Planned status only for work you have committed to; see Backlog or Planned. Use Dependencies to select Projects that block this work or depend on it. Those selections are saved when you create the Project.
A new Project starts with its primary Initiative's current icon color. Choose a color in the create dialog to override that default, including gray. Projects without an Initiative start gray. This is a creation-time default: changing the Initiative's color later does not recolor existing Projects.
You can change these properties later from the Project's Overview. To rename a Project from a table, right-click its row and choose More properties → Rename. Editing requires Project metadata edit access.
Delete a Project
Choose Delete from the Project's row or detail menu, then review the confirmation. You can also select several rows to delete Projects together. You need permission to edit the Projects you delete.
Deleted Projects can be restored for 30 days. On the workspace Projects page, open More Project actions → Archived projects and switch to the Deleted tab; on a Team's Projects page, open More Project actions → Recently deleted projects. Then select Restore. The restored Project keeps its identity and available content; relationships that are no longer valid may be removed. Restoring does not restart an old execution run.
Workspace owners and admins can permanently delete a Project after a further confirmation. This cannot be undone. Linked Issues remain independently managed and are not deleted with the Project.
Archived Projects
Archive is not a status. A status such as Completed or Canceled says how the work ended, and the Project stays active until it is archived. Archiving moves a closed Project out of active work and keeps it as a read-only record, with its status and Activity history unchanged.
Integrity archives Projects automatically; there is no Archive action. Auto-archive is on by default after 30 untouched days. A workspace owner or admin can change the delay or turn off Auto-archive Projects under Workspace Settings → Projects → Statuses → Automation. A Project in a Completed or Canceled category status is then archived once it has had no meaningful change, such as a status, property, or description edit, for that many days. Every Issue linked to it must already be archived or belong to an archived Team; work on those Issues does not restart the count. The archive runs once a day and handles a limited number of Projects each time, so a Project can stay active for a day or more after it qualifies.
Open … → Archived Projects from the workspace or a Team's Projects page. These lists end in /projects/archived. Open an archived Project to read its content without editing or commenting. Choose Restore in its banner, or Unarchive from its row menu; you need permission to edit Projects. See Archive and delete for the shared rules and release timing. The Project becomes active again with the same status (change Show closed projects in Display to see it in the table), its linked Issues keep their own state, and the count starts again, so it is not archived again straight away. If the work is starting again, change its status after you unarchive it. Deleting an archived Project and restoring it later returns it to the archived Projects.
View your Projects
The workspace Projects page shows the Projects you can access. Use Display to switch between List, Board, and Timeline. Each presentation uses the same filtered set of Projects.
Filter by properties such as status, priority, lead, Team, labels, or dates. Group the results to compare related work, and choose the fields you want to see. For example, group by lead for an ownership review or by target date to discuss upcoming delivery. Rows show each Project's name; turn on the Slug display property to show its stable slug too, which helps when two Projects share a name.
Completed and canceled Projects are hidden by default. Change Show closed projects in Display to bring them back. In Timeline, choose Year, Quarter, Month, or Week, and select Today to return to the current date.
Open a row, card, or Timeline bar to see the Project's description, properties, Resources, and Phases. Use Activity for its change history or Issues for the work linked to it.
Add Issues to a Project
Open the Project's Issues tab and create an Issue. The create dialog starts with that Project selected. Anywhere on a Project page you can also press C (or V for the full form): the new Issue starts in that Project. You can also assign an existing Issue through its Project property, or choose the property when creating an Issue elsewhere.
To move several Issues at once, select them in an Issue table, highlight one of the selected rows and press Shift+P, then choose the Project. The change applies to every selected Issue. The other property keys (S, P, A, L, E) work on the selection the same way.
An Issue has one primary Project at a time. Changing that selection moves it to the new Project's Issue list. The Project's Progress card summarizes the linked Issues you can access; private Issues you cannot read are not included.
Organize delivery
Keep the intended outcome in the Project description, use Phases for delivery stages, and create Issues for the work people will carry out. Supporting Documents can hold research, decisions, and longer notes.
Attach Issue views to a Project
Select Add view beside the Project's Overview, Activity, and Issues tabs. Choose filters and a layout, give the view a name, then save it. You need Project edit access to add a view.
The saved view becomes a tab for that Project. It can narrow the Project's Issues, but cannot include Issues from another Project or expose work you do not have permission to read. Canceling returns you to the Issue view you were using before creation.
For a daily check-in, save a view filtered to in-progress Issues. For a quality review, filter by a relevant label. These views stay with the Project; they do not appear automatically in Team or workspace Views.
Save views on the Projects page
Create a custom view on the main Projects page to return to a useful set of filters and display settings. Set its name, description, and color, then save. For example, keep a view of high-priority Projects or work owned by your Team.
Right-click a saved view to edit its name, description, or color, duplicate it, or delete it. A duplicate begins as a new draft; saving it creates a separate view. Deleting a shared view removes that view for other permitted users, so check its purpose before confirming.
Later filter or display edits remain private until you select Save changes. Use Discard to return to the saved settings. Switching between List, Board, and Timeline alone does not mark the view as changed.
Views belong to the surface where you create them. A main Projects view is separate from an Initiative's Project views and from the workspace Views directory. See Views for sharing and defaults.
Project details sidebar
Open a Project and use the properties-panel control, or press ⌘I (Ctrl+I on Windows and Linux), to show or hide its details. The key does nothing while you type in a field or an editor, where it keeps its usual meaning. Update status, priority, lead, members, Teams, dates, Initiative membership, and labels when you have edit access.
Use Blocked by and Blocks to describe delivery order, or Related for a connection without active blocking. Adding a relationship does not automatically change either Project's status or dates. Completing, canceling, or archiving a blocker converts its incoming dependencies to Related while leaving each dependent Project's status unchanged. Resources hold supporting links, private files, and Documents. The main Overview keeps the narrative and Phases alongside this context. See Project dependencies for the controls and table filters.
Multi-Team Projects
Select more than one Team while creating a Project, or edit its Teams property later. Use this when delivery needs contributions from several groups but should keep one shared description and plan.
Team ownership describes who is involved; it does not grant access to private Teams or their Issues. Each person sees only the work they are allowed to read. Use filters on the Project's Issues tab to focus on the relevant Team's work. Its create action opens the Issue create flow with the Project preselected when you can create Issues in at least one active Team; Project edit access alone does not grant that action.
Timeframes
Set start and target dates at the level of detail you know: a day, month, quarter, half-year, or year. Choose the dates from the Project's properties or its table controls, and refine them as plans become clearer.
Use date filters and grouping to review upcoming work. Timeline provides a calendar view of Project date windows; its granularity changes how you browse the schedule, rather than changing the dates themselves.