Every project stays independent
Its own members, permissions, boards and statuses. The receiving team doesn't see the other project, only the tasks that arrive.
A bridge between teams, not a merger
Support found a bug, but development has to fix it. One team doesn't have to let another into its project: the connector passes the task on once it reaches the right status.
Updated
What it is
A connector links boards of different projects in the same space. When a task in the support project reaches "To development", the connector sends it to the backlog of the development project. From there it follows the development process, and support can see what is happening with it.
This is one level above board links within a project: there, one team organizes work across its own boards; here, different teams pass tasks to each other without mixing projects.
One connector, any number of projects
A connector collects tasks in one project and distributes them to several: for example, support requests go both to development and to implementation.
Visible on the process canvas
The connector sits on the same canvas as boards and links, so the path of a task between teams is visible end to end.
When it helps
- A company with several departments, each with its own project and way of working.
- A holding where subsidiary teams must not see each other's projects.
- An agency passing tasks between internal teams and client projects.
Frequently asked questions
Do I need a paid plan?
Yes, connectors between projects are part of the paid plans. What each plan includes is shown on the Pricing page.
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.
No card required
Data hosted in Russia
Russian-language support