Projects: a defined delivery
Create or open a project from the project directory. Maintain its description, lead, associated teams and dates. Add related issues and use milestones to define stages. Projects do not replace workspace boundaries, and projects spanning teams preserve each team’s visibility rules.
Project updates communicate progress and risk; comments support discussion. Project health and issue completion percentages describe different things. Half the issues being complete does not by itself prove a project is on track.
Team Projects lists projects associated with the current team that you can read. It supports list, board and timeline layouts, plus status, priority and lead filters. Multi-team projects appear once in that directory. Projects created here by an administrator start with the current team selected; it must remain selected, while other teams can be added. The workspace project directory continues to offer cross-team browsing and the roadmap.
Project directory filters live in the Filter menu, with grouping and layout in Display. Applied conditions remain individually removable. The list uses aligned columns; wide tables scroll inside the directory.
Cycles: a team planning window
Cycles belong to teams and organize work within a time window. Open a team’s cycle area to inspect current and upcoming cycles, then assign issues. Admins can choose the team’s schedule time zone; saving other settings will not overwrite it. Admins can turn off moving unfinished issues into the next cycle (on by default), or enable adding unassigned issues when work starts (off by default). The latter takes effect only while cycles are enabled and a current cycle exists. Explicit cycle selection, including clearing it, takes priority. These switches do not move issues retroactively. Do not move an entire cycle just to change one issue’s schedule.
Click a team name in the sidebar to expand or collapse Issues, Triage, enabled Cycles, Projects, and Views. The separate team menu offers Copy team link and, for administrators, Settings. You can open Cycles before they are enabled; admins can go directly from that empty state to cycle settings. The current cycle shows only actual historical burndown and status counts; insufficient history does not produce an estimated line. Completed counts and estimates include only completed issues; cancelled and duplicate issues remain in total scope.
Use All teams in the sidebar to find a team by name or identifier. Show more favorites reveals the rest of your favorites in place. On desktop, use the button at the top of the sidebar to collapse or expand it. On narrow screens, use the close button in the drawer to return to the page.
An issue’s start and due dates are stored separately from its cycle membership. An unscheduled issue does not acquire an invented interval because its dates are missing.
Initiatives and roadmaps
Initiatives connect longer-term goals with projects and can include one level of child initiatives. The project roadmap groups projects by their actual direct initiative relationships. A project associated with several initiatives may appear in several groups; visible rows are not a deduplicated project count.
Timelines use real dates. Adjusting project dates changes that project, not its initiative’s target date or a team cycle. Use the provided keyboard date controls when dragging is unsuitable.
Project, initiative, milestone, release and cycle date fields offer a calendar and a YYYY-MM-DD entry. Choose a day or confirm a valid date; optional dates can be cleared. A date does not set a time of day.
Insights and reflection
Insights provides current distributions and historical completion, velocity and duration measures supported by real events. Insufficient history stays unknown. Cancelled and duplicate work does not count as completed. Check range, time zone and count-versus-estimate settings before comparing trends; unknown values are not zero.
Use Project releases to record delivery scope and publication snapshots. Releases do not deploy code. For communicating weekly progress, continue with Collaboration and notifications.