WorkTeam Task Board

Teams

Connecting…

You are

Signed in as

Download workbook

Open classic view

All tasks

Every open item across your teams

/

New task

Title

Description

Team

Owner

Type

Sprint

Parent (Epic or Story)

Priority

Due date

Due in

Pod

Program

Module

Built by (external vendor)

Labels

Release date

Mark as done

Completed date

Release date

Upcoming releases

Register a person

Full name

Work email

Team

Role

Phone (for on-call)

Status Active

Renaming updates this person's tasks and on-call entries.

New organisation

Organisation name

Description

Head

Status Archived

New team

Team name

Organisation

Task ID prefix

Lead

Description

Archived (hidden from the sidebar and New task; its tasks stay)

New pod

Name

Description

Lead

Status Archived (hidden from pickers)

New sprint

Name

Start date

End date

Length

Goal

Once the start date arrives, moving a ticket in this sprint (status, owner, pod, program or sprint) needs the admin password.

Close sprint

Open tickets

Management summary

To

Subject

Personal note (optional, shown above the summary)

Admin password

This needs the board's admin password

New release

Name

Release dateSeveral releases can share a day.

Summary (optional)

Versions

Known limitations and bugs

Anything this release goes out with that isn't fixed. Each becomes its own Bug ticket on the board, labelled known-issue, release: plus the release name, and the versions above, so it can be prioritised later.

Under epicTeam (when there is no epic)

Freeze

Freezing says the requirements are settled from your side. Once every owner has frozen, edits to the requirement are logged as iterations.

The day you froze

Your ETAWhat you commit to. Moving it later is recorded as slip.

This requirement is frozen

You're changing . Every owner has frozen, so this is logged on the ticket as iteration .

Charge it to

Why (optional)

Found something new?

Cut scope into a new version

Creates the next version of this story (v1, v2 …) as a ticket of its own, with the same team, type, parent, pod, program and module, and the same owners (not yet frozen). This ticket stays as it is.

Title (optional)

What the new version adds

Why it was cut (optional)

Add a tool

Name

Category

Status

Owning team

Link

Start date

End date

Billing period

Renews automatically

Contract terms

SPOC name

SPOC email

Monthly cost (₹, ballpark)

Unit

Number of units

What we use it for

Credentials

Archived (hidden from the register and from spend)

Credentials

This reveal was logged. It hides itself after a minute.

Link to a Google account

Google Workspace account

Upload users CSV

Download the full user list from the Google Admin console (Directory → Users → Download users) and upload it here. Each upload replaces the directory: everyone in the file is added or updated, and anyone from an earlier upload who is not in the file becomes inactive. People added by hand as External are not touched.

CSV file

Import workbook

Choose an .xlsx file or drag it here · a Team Tasks workbook: one sheet per team, plus optional “OnCall Roster” and “Users” sheets

How to import MergeUpdate tasks with matching IDs and add new ones. People and on-call entries are merged. Nothing is removed. Replace everythingThe board becomes exactly what's in the file. Tasks, people and on-call entries not in the file are removed.

Admin password

A backup of the current data is saved on the server before anything changes.

Team Task Board

This board is password protected. Enter the team password to continue.

That password didn't work. Try again.