Connectors: passing tasks between projects
A connector in Fluo passes tasks to another project: a task leaves a board column, goes through the connector, and lands in a column of another project. At the exit, it can change its type.
How a connector works
Links between columns work inside one project. When tasks need to go to another project, for example from support to development, you put a connector between the projects. It appears on the workflow map of both projects.
- Input. In the project where the connector was created (its home project), the connector has a point on the left. You draw links to it from the columns that tasks will leave.
- Home project. Under the connector name there is a house badge with the name of that project. Click it to open that project's workflow map.
- Counters. Up to three badges with numbers in the bottom-right corner. They open lists of the projects that use the connector, the columns on the other end, and the service desks whose requests go through the connector.
In a receiving project, the same connector has an output point on the right. From it, you draw links to the columns where tasks should arrive. Each project keeps its own position of the connector on its map.
A connector passes tasks one way: from the home project to the receiving projects. For the way back, create a second connector in the receiving project. You can't connect two connectors to each other.
Each route has its own connector links
Each task type has its own route, that is, its own set of links (see “Project workflow: task routes and task types”). Connector links follow the same rule:
- a link from a column to the connector is drawn on the home project's map in the selected route, and it only carries tasks of that type;
- a link from the connector to a column is drawn on the receiving project's map, also in one of its routes;
- other routes don't show these links, and tasks of other types don't use them.
You can send a task of any type into a connector if the route of its type has a link from its column to the connector. Tasks with “No type” use the links of the “No type” route.
Which type a task gets at the exit
Each project has its own task types, so at the exit Fluo picks a type using the “Task types at the exit” table in the connector settings. The rule:
- if the table has a match for the task's type and the project it exits to, the task gets the type from that row;
- a row with “No type” on the exit side resets the type, but only in the project selected in that row;
- if there is no match, the task arrives with “No type”.
After that, the task follows the links from the connector to columns in the route of its new type. So draw the exit link in the receiving project's route whose type the task will get. If a support “Bug” becomes a development “Bug” but the link from the connector exists only in the “No type” route, the development columns won't appear in the move menu.
A type change at the exit is recorded in the task history. To fill in the table, see “How to set up a connector”.
How a task goes through a connector
You send a task the same way as along a regular link: with the arrow on the card. The receiving project's columns appear in the move menu if the connector's exit exists in the route of the type the task will get. For more on moving tasks, see “How a task moves along its route”.
If “The task moves on by itself” is on for the link from a column to the connector, the task goes through the connector without you as soon as nothing holds it. The conditions of the column where it will land in the receiving project can hold it too. The task lands in the column that the connector's exit leads to in the route of its new type. If there's no such exit, the task stays in its column. “Undo” in the notification after such a move returns the task to the home project with its old type and undoes what the receiving project's rules did, see “How a task moves along its route”.
The whole task moves to the receiving project, with its checklist and chat. Custom field values go to fields with the same name and type; the rest are lost. If the task needs a new assignee, set up a rule on the receiving column (see “Status automations: actions on entry and exit”).
The board the task left, by hand or by itself, keeps track of it until it's closed: the “N tasks handed off” button shows where the task is now. For details, see “‘Handed off’: where tasks that left the board are now”.
If you don't have access to the receiving project, the task disappears from your view after the move.
What you can connect
- Projects in the same space.
- Projects in different spaces with the same owner. For example, your personal space and a team space you created. The second space's plan must include connectors too.
- Only an extended project can receive tasks. Templates and archived projects don't appear in the list.
You can't connect spaces with different owners.
The API and MCP can also send a task through a connector, but only within one space: an access key is tied to one space.
If the plan has ended
Connectors created earlier stay on the map, faded and locked. Tasks still go through them, but you can't change their settings, delete them, or draw new links to them until the space is back on a paid plan.
Example
The Aurora team has a Support project with a Requests board and the types Bug, Question, and Wish. The Aurora project has its own types, among them Bug and Improvement. In Support, the team creates a connector called Bugs to development. In the Bug route, they draw a link from the Bug confirmed column to the connector. In the connector's table, they add a match: Support and Bug at the entrance, Aurora and Bug at the exit. In Aurora, in the Bug route, they draw a link from the connector to Backlog on the Development board.
Now a confirmed bug goes to development in one click and continues along Aurora's Bug route.
Related articles
On the website: Cross-team processes in Fluo: linked boards without code