Default status when moving an item from one board to another (automation not working)

I’m moving items from one board to another using an automation when the item status changes.

The item (once moved) is not inheriting the status from the previous board BUT there is a status column that matches the group titles.

I set the default status to a specific group but when the item moves, the status refuses to match the default settings and an automation I set to ensure the status is labeled correctly.

Below are some screenshots of my automations and defaults from the 2 boards.

Original Board: Automation

Second Board: Automation (**I added the automation at the top because every item the moves into the board defaults to an ‘Active’ status and it worked BUT I don’t think that’s scalable.

Hey Cory,

Just to clarify, is the issue that when the item moves to the destination board, it isn’t retaining the approved status label? Are you able to specify what your end goal is here? Is it for the item to move to the Master Projects board and retain the done label? I am trying to understand the relationship between the automation on board 1 and the automations on board 2 - apologies for my confusion here, I want to ensure I am across the behaviour here :pray:

Hi Bianca,

Thanks for your reply. YES, the goal is to move OR create (they seem to be similar) an item from board 1 to board 2 after a status change and when that happens, the item should be placed into the ‘backlog group’ and assigned ‘backlog’ label.

The issue is that the item isn’t adopting the ‘backlog’ label BUT is going into the group.

@sorigami Hi Cory,

It seems like in order to achieve your desired functionality, you should remove the “and only if Status is Active” condition from your automation.

That will ensure that the status is always set to “Backlog” when an item is moved to the board.

A couple of points:

  1. By clicking on the item bold text in your Original Board automation (the one that moves the item), you can change mappings and either input default values or use dynamic values.
  2. Groups and statuses are not inherently linked. Many people like to use them that way and there is a sense in which it is intuitive, however they are not actually connected. Personally, I prefer to avoid using groups and statuses in that way as it creates a double data situation. You’re maintaining two separate pieces of data with the same function (Group and Status).
1 Like

Hey Francis,

The ‘only if status is active’ was a workaround. I’ll look into your solution again tomorrow. Thanks!

1 Like