Connect 2 tasks from 2 separate projects so when one task's field or section changes (i.e moves through a board) the other task also moves or changes field status within its own board


CONTEXT

There are 2 projects, 1 being a reference only board and the other is an on-going process board.

“Test Pipeline” is the reference only board which shows each upcoming test/creative sets as a task.

“Campaign Build” is the on-going process board. A task is automatically created here via the rules from the reference board to create the campaign relevant to the test/creative sets.

columns/custom field status in the reference board:

  • Creatives in Production
  • Ready to Spend
  • Campaign Ready
  • Live
  • Ended

columns/custom filed status in the on-going process board:

  • To Build
  • For Review
  • Ready to Launch
  • Active Campaign
  • Paused Campaign

INTENTIONS

As the task in the on-going process board moves along the columns, we want the relevant task in the reference board to move along it’s own columns as well:

  • When a task in the on-going process board is moved to the “Ready to Launch” column, the relevant task in the reference board should move to “Campaign Ready”.

  • When a task in the ongoing process board to “Active Campaign” column, the relevant task in the reference board should move to “Live”

  • When a task in the ongoing process board to “Paused Campaign” column, the relevant task in the reference board should move to “Ended”


CURRENTLY

What we’re doing instead is having dependencies; the task in the reference project is dependent of the task in the the on-going project. As the task in the on-going project moves along the columns/changes status, a rule is triggered to create a subtask to manually do the intentions detailed above.

Is there a way to do this? We’d appreciate it very much if we can eliminate the manual part in the current set up by having the tasks be connected and move along their own boards using rules/triggers instead?

Hi @Reno_Jimenez and welcome to the forum,

Yes, the way to accomplish this is by using a global (library) custom field to coordinate between the projects; see Sync tasks between projects - #2 by Arthur_BEGOU

1 Like

Great, thank you so much for the guidance! I knew I was missing something, I should have used “sync” instead of connect in the search bar.

:bowing_man:

1 Like

Oh actually this does not work on our case. This Sync tasks between projects - #2 by Arthur_BEGOU makes use of one task in two projects. Meanwhile, our use case has 2 different tasks, one on each separate project.

Task A is in Project X and Task B is Project Y. But Task A and B has to be interlinked in such way that while Task B moves through columns/changes status in Project Y, Task A also moves along columns/changes status in Project X.

I hope there’s a way to do this.

Does it have to be two separate tasks, or could it be one task on the main process board that is multihomed to the reference board, and then different rules on each board, with the only the relevant custom field/status showing on each board. I’m thinking main board would move from To Build to For Review. Then a rule in the reference board would say if custom field is changed to ‘for review’ change other custom field to ‘ready to spend’ or whatever the relevant pairing of custom fields would be.

2 Likes

I’m open to any solution that might get us to the same end.

Currently, As soon as tasks in Project X goes through the “final pass” a rule is triggered and creates a separate task in Project Y to build the campaign that will use those images.

Project Y is essentially the creatives production work area (project). When creatives are approved and ready, we cannot continue on working the same task for building the campaign since it has become so crowded at that point already and need the creatives development task to end there.

We want the campaign creation process to start a clean slate but is still connected/in sync with the task that triggered its creation, the creative development task that is relevant to the campaign build.

that’s why we have 2 separate work areas (projects), one for creative development and another for campaign builds each have their own separate workflows, and campaign build always come after creatives development.