Your team's entire workflow, in one app.

Kanban or Scrum? Both. Switch between a drag-and-drop board, a sprint backlog and a customizable list view in one click. WIP limits and workflow transition rules exactly the way you want them. Once your setup is right, you start the next board from an existing one: workflow, custom fields, issue types and roles arrive ready.

Track work grouped by epic as bars on a date axis. Progress fills, a 'today' line and release milestones make it instantly clear how the plan matches reality. Export the timeline as PDF.

Enter who works in the sprint, each person's daily capacity and their days off; the planning calendar lays the team out row by row against the sprint days. Capacity lost and remaining work are computed at the top; remaining work turns red once more work is planned than the team can carry. Drag a task's bar to shift its dates or hand it to someone else.

No separate wiki tool needed. Wiki-style page hierarchy, version history, approval chains, tables and code blocks right inside the same product. Decide who sees what with page-level permissions.

A quality document is referred to by its number and discussed by its version. You define a code series in board settings (prefix, separator, digits); every document created from a template bound to that series receives the next code automatically: MAN.4-TL.01. The version number tells you how mature it is: 0.1 draft, 1.0 once published, 1.1 when editing starts, 2.0 when published again. A deleted code is never reissued, so no two documents can share a code in an audit.

An approval is a single signature. A quality process asks for more: comments are collected, each one is dispositioned with a reason, the document is revised, then approved again. Review breaks that loop into rounds and puts every step on record. The question an audit asks is not “was a review done” but “who said what, and on what grounds was it decided”.

Create your own statuses, assign them to categories (To Do / In Progress / Done) and colors, set WIP limits. Tie a transition to a role, to people you pick, or to a person field on the task; when work enters a status it can be auto-assigned to the reporter, to whoever is named in that field, or to a fixed member. The process follows your team's rules.

Connect to GitLab over OAuth and add the projects you need to the board; they can come from different groups, and a whole group can be added at once. See branches, commits and merge requests inside the task; every row names the project it came from. Branches and MRs are opened under each person’s own GitLab account. Best of all: map GitLab events to workflow statuses so a merged MR advances the task, and "Closes CJ-123" in the MR description does the same.

Will the sprint make its goal, how long does work take, what is due in the next two weeks: three answers on one dashboard. The sprint goal card shows working days left, scope added after the start and the risk; the cycle time card shows the average, the median and the change against the previous period; the calendar card gathers work from several boards in month, week or day view; the Status aging card shows which work has overstayed its target in which status. Burndown, velocity, CFD and distribution cards sit alongside; drill from a pie straight into a filtered list.

Description, sub-tasks with progress, linked issues ('blocks / blocked by'), attachments and the full field set on one screen. Keep the conversation in context with @mention comments; watchers stay in the loop on every change. No tab-switching to hunt for context.

Assignments, comments that mention you, status changes, due dates, approval and review requests gather in the notification bell. Read/unread tracking, one-click 'mark all read', and a click takes you straight to the task or page. Connect your own SMTP server and the same events arrive by email too.

See due dates, sprint start and end, and release dates on a color-coded month calendar. Source it from the board's own date fields and see public holidays in place. Spot overloaded days at a glance; drag a task to another day to reschedule.