Source: https://taska.be/en/features/processes
Updated: 2026-10-23

# Tasks don't get lost between teams

Development hands a task to testing, testing to support, support back to development. In Taska this is easy to set up in a dedicated process editor.

[Start for free](https://taska.be/app/auth/signup) [See the plans](https://taska.be/en/pricing)

Updated Oct. 22, 2026

## What it is

A project can have several boards, one per team. The statuses of these boards are connected by links. When a task reaches "Ready for testing" on the development board, it appears by itself in "Testing" on the QA board. Nobody moves it by hand or posts "handed over" in a chat.

All boards, statuses and links of a project are visible on one canvas. A link is drawn with the mouse from status to status, like an arrow in a graphics editor. A large process can be arranged into groups: "Development", "Sales", "Support".

## How to set it up

1. Create a board for each team, each with its own statuses.
2. Open the project's process canvas and drag a link from a status on one board to a status on another.
3. If the task should change assignee on the way, set it right on the link: for example, moving to review hands the task to the team lead.
4. Add status automations where you need rules: a tag, a deadline, a timer, a condition check before leaving.

## What else works with processes

### Status automations

On entering a column, a task gets an assignee, tags, a priority, a deadline or a running timer. Entry conditions won't let it in without an assignee, a checklist or required fields, and exit conditions won't let it out without logged time. Available on the Business plan.

### Blockers

"Impediment" and "Stop" right on the card: you can see the task is stuck and why, and the assignee is notified immediately.

### Task chains

Next and parallel tasks: the board shows who is waiting for whom and the step number in the chain.

## Who it's for

### A good fit if

- several teams take part in the work and tasks pass between them;
- the process changes, and a team lead rather than a programmer should be able to adjust it;
- a manager needs to see the whole path of a task, not just one board.

### You can do without it if

- the team is small and works on a single board: start with it, processes will connect when you need them;
- you need formal BPM with regulations and signatures: Taska is about the live work of teams, not document management.

## Frequently asked questions

Do I need an administrator to set up a process?

No. Board links and automations are set up with the mouse by whoever runs the process: a team lead, a department head, a product manager.

How is this different from automations in other trackers?

In most trackers a rule lives inside a single board. In Taska, statuses of different boards are connected and the whole process is visible on one canvas, so it is clear where a task goes next.

What if teams work in different projects?

That is what [connectors](https://taska.be/en/features/connectors) are for: they pass tasks between projects without opening each team's project to the others.

## Bring your entire workflow into one place

Sign up in a minute. Free forever, with every Pro capability unlocked for 14 days without a card. No need to migrate your whole team — start with a single project.

[Start for free](https://taska.be/app/auth/signup) [See the plans](https://taska.be/en/pricing)

No card required Data hosted in Russia Russian-language support