Workflows

Plan work on a board

Every project has a board: its tasks as cards, in columns its managers choose. The team moves the cards as the work moves, and talks about each one on the card. The cards are the same tasks people book their hours to, so the board and the week never disagree. Tasks can also be brought in from Azure DevOps, Jira, Trello or Notion.

Who does what

Who can open a board, and what they can do on it, depends on how they stand on the project, not on the menu: everybody has Boards. A project's manager here is an administrator, or a Manager or Finance user whose grant gives them Manager access to the project (see Grants and project teams). A member is someone ticked on the project's team.

On the boardThe project's managersA member with Can create tasksAny other member
Open itYesYesYes
See the cardsEvery cardThe cards they can book time toThe cards they can book time to
Move cardsYesThe cards they seeThe cards they see
Add cards, rename and describe themYesThe cards they seeNo
Comment on a cardYesThe cards they seeThe cards they see
Set dates, estimate, owner and who sees a task; delete itYes, on the project's pageNoNo
Add, rename, recategorize, reorder and delete columnsYesNoNo
Link the project to a source and import tasksOn the Team plan and up, and during the trialNoNo

Managing a board takes the role as well as the grant: a User who has been given Manager access to a project is still a member on its board. Adding a connection to another tool, which every project can then import from, is for administrators alone. An administrator turns on Can create tasks on a person's page under Settings → People (Permissions for one person). Client guests do not see boards.

1. Open a project's board

  1. Choose Boards in the menu, under Collaborate. The page lists, by client, the projects you are on and, if you are a manager or an administrator, the active projects you manage.
  2. Choose the project. Its board opens with a column for each stage and a card for each task you can see. A manager can also open it with Board on the project's page.

Above the columns, Discussion opens the project's own conversation in Messages, and the project's managers have Project details and Import tasks. If the list says You aren't on any projects yet. A project's board appears here once you are added to it., ask whoever runs the project to put you on its team. Boards describes each part of the screen.

2. Set up the columns

A new project's board has four columns: Not started, In progress, Blocked and Done. A copied project keeps the columns of the one it was copied from. You can name the columns anything and have as many as you like, but each has a category, one of those four, and a card's status is always its column's category. A card in a column whose category is Done counts as done on timesheets and in every count of open tasks.

The Add a column dialog over the board of Grid Telemetry Platform, with In review typed under Column name, Category set to In progress, the hint Cards in a Done column count as done on timesheets, and Cancel and Add column.
Adding a column, as the project's manager.
  1. To add one, choose + Add column at the end of the row. In Add a column, type the Column name, pick its Category, and choose Add column. It is added at the right-hand end.
  2. To change one, open the ⋯ menu in its head: Rename…, Change category… (every card in it takes the new category as its status), Move left or Move right. You can also drag a column by the dotted handle in its head.
  3. To delete one, choose Delete… in its menu. If it has cards, pick where they go under Move the cards to; they land at the bottom of that column and take its category. Then choose Delete column.

A column name can be up to 60 characters and has to be unique on the board, ignoring capitals. A board always keeps at least one column, and at least one Done column.

3. Add cards

A card is a task. Either way of adding one makes the same task:

Only the project's managers, and members an administrator has let create tasks, have + Add card. Others can ask a manager, or suggest the task in the card's or the project's discussion.

4. Open a card and talk about it

The card Load testing open in a panel down the right of its board. It shows Stage Not started, Owner Nobody, Dates Oct 26, 2026 to Dec 11, 2026, Hours 0 h logged of 180 h estimated, Description No description, the buttons Edit name and description and Edit dates, estimate and owner, and under Comments, No messages yet, a box to write a message with the hint Type # to reference a task, or @ to mention somebody, and Send.
A card's panel, for the project's manager.

Choose a card's name. Its panel opens down the right, with the board still in view. It shows the card's Stage, Owner, Dates and Hours logged against the estimate, and its Description. Then:

Close, or Esc, closes the panel. A card that has a conversation says how many comments it has on its face.

5. Move cards as the work moves

  1. Drag the card by the dotted handle on its left into another column, or to another place in its own column.
  2. Or, from the keyboard, open the card's Move to… menu and choose Top or Bottom under the column it goes to.

The card moves at once and takes the new column's category as its status: dropped into a Done column, the task is done. Moving a card changes nothing else about it, and it is never blocked by hours being submitted, approved or invoiced, because it changes no hours. If someone else changed the board at the same moment and the move cannot be made, the card goes back to where it was and the board is read again.

From the board to the week

A card is a task, so there is nothing to copy across:

Renaming a card renames the task on the board, in the lines already on people's weeks and in reports. An invoice already drawn up keeps the name the task had when it was made, so a customer is never sent a changed copy. Record and submit your week covers booking the time.

6. Connect a source (administrators)

Importing tasks is on the Team and Enterprise plans and during the trial. On Free and Starter, Integrations is not in the menu and the board has no Import tasks; see Plans and your trial. An administrator connects each tool once, and the project's managers import from it.

  1. Choose Settings → Integrations, then New connection.
  2. Pick the Source, and give the connection a Name: it is what managers see when they choose where to import from.
  3. Fill in what the source asks for (below). The help under each field says where to find it in that tool.
  4. Choose Add connection. The app says … added. Test it to check the address and key.
  5. Choose Test connection on its row. A test that works says whom the key reaches, such as Connected as …; one that fails says why.
SourceWhat the form asks forWhat a project links to
Azure DevOps ServicesOrganization URL (https://dev.azure.com/your-organization, without a project), and a Personal access token with the Work Items (Read) scope. Where your deployment offers it, Authentication can be Sign in with Microsoft instead of a token.A team of a project, or a shared query that returns a flat list.
Azure DevOps Server (TFS)Collection URL, reachable from the internet over https with a publicly trusted certificate; a Personal access token with Work Items (Read); and, optionally, the API version. Azure DevOps Server 2019 and later.A team of a project, or a shared query.
Jira CloudSite URL (https://your-site.atlassian.net), the Account email the token belongs to, an API token, and, optionally, the Start date field.A project, or a project narrowed by one of the token owner's starred filters.
Jira Data CenterBase URL, https and reachable from the internet; a Personal access token (Jira 8.14 and later); and, optionally, the Start date field.A project, or a project narrowed by a starred filter.
TrelloAn API key and a Token, from a Power-Up you create in Trello. Whoever allows the token has to be a member of the boards you import from.A board.
NotionAn Internal integration secret. Then share each database you import from with the integration, in Notion.A database.

The account behind the key needs to see what your projects import, and nothing is ever written back to the source. Keys are stored encrypted and never shown again. Integrations covers editing, turning off and deleting connections.

The project's manager links it once, to one board or project in one source.

  1. On the project's board, or its page, choose Import tasks. The first time, it opens Link a source.
  2. Under 1. Connection, pick one of the connections your administrator added. If there are none, the dialog says No sources are set up. Ask an administrator to add one under Admin → Integrations.
  3. Under 2. Board or project, type to search, and pick what this project's tasks come from.
  4. Under 3. Mapping, check what it suggests:
    • Columns: for each column or state in the source, the column of this board its items land in, or Skip. Items in a skipped column are not offered for import.
    • People: for each person in the source, the project member who owns the tasks made from their items, or No owner. People are matched by email where the source shares one; Trello almost never does, so map them by hand. Only members of the project's team can own a task.
    • Fields (Notion): which property of the database is the column, owner, start date, end date and estimate.
    • Default filter (optional): what the list of items opens with, such as one state or one sprint.
  5. Choose Save link. The app says Saved the import link. and opens the list of items to import.

A project links to one place at a time. Two projects can link to the same board in a source.

8. Pick what to import

Once the project is linked, Import tasks opens the list of the source's items. Its header names the source and the board, with Change link and Unlink, and when the last import was made.

  1. On Available, narrow the list with the filters the source offers (state, type, sprint, label, assignee, changed since, text…). Show more reads the next page.
  2. Tick the items you want, or Tick all shown. Each one shows its column and assignee in the source, its estimate, and Open in source. An item already imported into another project is marked Also in …, and can still be imported here.
  3. A ticked item opens its Column, Owner and Estimate (h), as the mapping set them. Change them for this item if you like. Ticks are kept when you change the filter, so one import can gather items from several filters.
  4. Choose Import … tasks. The app says Imported … tasks onto the board., and lists anything it skipped and why, and any warnings, such as No member of this project matches …, so the task has no owner.

Items that should never become tasks can be ticked and marked with Mark … as not for timesheets instead, so they stop being offered. Show dismissed lists them again, each with Restore. Up to 200 items can be imported or marked at a time. The Imported tab lists what has been imported, each linked to its card.

Each imported item becomes a task, named after its title (up to 200 characters), with its start and due dates and its estimate where the source has them, and the owner the mapping or your choice gave it. It is open to every member of the project, and lands at the bottom of its column, in the order the list showed, with the column's category as its status. The description, comments, attachments and history stay in the source.

Importing again, and changes at the source

Run Import tasks as often as new work arrives in the source. An import copies the item as it is at that moment, and never updates it later:

When Boards is turned off

An administrator can turn Boards off for the whole organization, when it only tracks time. While they are off:

Nothing is deleted. When Boards is turned on again, every card is in the column and place it was in, a task added meanwhile is at the bottom of the first column of its status, and every comment is back.

When something goes wrong