Skip to main content
Free plan, no cardStart free
Suites, runs and planning 9 min read Updated

Project Management: sprints, releases and test cycles

Project Management is the planning side of the workspace: projects with members, reporting lines and a budget; sprints that record capacity, committed points and a Definition of Done before work starts; stories, bugs, tasks and epics with comments, attachments and a work log; test plans, test cases and test cycles with a step-by-step runner; releases whose readiness is computed from open blockers and test coverage; and a traceability view from each requirement to the test that verifies it.

About this guide

Written for
Engineering managers · QA leads and test managers · Product owners

Projects and people

A project has a key, a client, a lead and members, and is created by the team owner; a member who is not on any project yet is told to ask the owner. Reporting lines (who reports to whom) drive approvals, timesheets and capacity. Finance (budget, billing profile, expenses pending approval, revenue entries marked sent or paid) is visible to the project's leads and managers only. A project can be put on hold, marked completed or cancelled, and the notifications page says who receives which event and from which mailbox. It uses the projects entitlement: Solo Pro and above, or the Projects & traceability tool on the Free plan.

Sprints, with the bar set first

A new sprint asks for the name, the goal, the dates, the team capacity in hours ("What the team can actually deliver"), the committed points (recorded now so the commitment cannot be rewritten later to match the outcome) and the Definition of Done, one line per item, because a bar that lives in someone's head is renegotiated whenever it is inconvenient. The board moves items from To Do through In Progress; the page warns as the sprint end nears and moves incomplete items to the backlog when it ends.

Capacity & leave sets hours per day per member and takes leave requests; the Drop-Plan places tasks per member per day with planned hours; the utilisation report shows logged against available hours with a forecast and a planned-versus-actual variance, and says in its own words that these are rollups of logged hours, not a performance rating.

Work items, search and documents

  • Stories carry acceptance criteria and story points; bugs carry steps to reproduce, the expected and the actual result; tasks and epics group them, and an epic shows its progress.
  • Every item has comments in threads (quote a passage, resolve or reopen, hide with an undo, edit history, reactions), attachments, a work log in hours and a change history.
  • The backlog lists what is in no sprint; All work lists everything; search takes a query such as `status = open AND priority in (high, critical)`, and a filter can be saved privately or shared with the project and handed to another member.
  • Documents live in folders with upload, grid, list and details views, check-out and check-in, and an activity log per document.

Test plans, cases and cycles

A test plan is a title and its cases, each with steps and an expected result. Test cases are written by hand or uploaded from an Excel file whose header row has a "Test Summary" column (Title, Name or Scenario also work), with Test Description, Expected Result, Components and Label read when present; the upload reports the rows and the errors before anything is created. A test cycle groups executions: add tests, set PASS, FAIL, WIP, BLOCKED or UNEXECUTED one at a time or in bulk, export the cycle as CSV, and run a test step by step with a timer. When the status you set and the steps you recorded disagree, the panel says so and keeps your status until you change it.

Releases and traceability

A release has a name, a version tag and a target date, and groups the stories, tasks and bugs that ship together. Its readiness is computed live: open blocker bugs, requirements with no verifying test, requirements whose tests fail or are blocked, and what has been completed. Health (on track, at risk, off track) is the lead's call, with a note. Mark it released when it ships; archive it when it leaves the active list.

Traceability reads each requirement (a story or an epic) and the test linked to it with the "verifies" relation, reports the percentage covered, lists the gaps (no verifying test; covered but nothing passing) and exports CSV. A link-health scan finds links whose target is gone and removes the ones you confirm.

Reports

A sprint report or a budget report takes a date range and the sections to include: work items by type, completion rates, team members, and the budget figures, which stay restricted to leads and managers. A report of an empty project says so instead of printing zeros as results. Reports are kept and downloadable.

Questions people ask about this

Who can see the budget?
The project's leads and managers. Everyone else sees the project without its finance tab, and the report hides budget figures from them too.
Can I bring test cases from a spreadsheet?
Yes. Upload an .xlsx or .xls file with a Test Summary column; the page shows the detected columns, the row count and any errors before it creates anything.
Does a sprint keep what we committed?
Yes. Capacity and committed points are recorded when the sprint is created, so the plan cannot be rewritten afterwards to match what happened.

Source: /documentation/project-management, updated 2026-11-16. Answers are checked against the shipped product on that date.

Found something out of date? The people who build the module answer the contact form on the home page, and corrections to this guide are dated above. Tell us.

This guide is about regression testing, the job that suites, runs and planning serve. Twenty tools, including ours, are compared by job.

Try it against your own app.

Record one flow and get four kinds of evidence back. Judge the results yourself.

  • Free plan, no card
  • 14-day Solo Pro trial
  • Demo replies within one business day
  • Data hosted in India