I have two identical board set-ups, one is used for active/ new incoming requests and the other is used as an archive (I find this easier than using the actual archive in monday). On the active board there is an automation that moves an item to the archive board upon changing to aa specific status. In the automation it is defined how columns in the target board will populate from the current board, and because we have the same board set-up on both boards we are basically just matching all the columns to each other. I am able to match all columns except the Tags column type. I can not set a tag column in the active board to populate a tag column in the archive board.
Both these columns are called Tags, but see in this screenshot that there is no “Tags” to choose from the drop down.
Does anyone have similar problem? or have found a workaround?
I am using the same process as you, I have a main board for all of my projects and another board for the archive and I would like to know how did you connect them.
I use an automation that is “When Status changes to Archived, move Item to Archive board”.
When you set Item it asks you what columns from one board should be populated with what column in the other board. So i didn’t really connect them I just have an automation that moves items to the archive, triggered by a given status.
Hope this explains it.
thank you so much. I did something similar, “When Status change to Done, and only if item is in Group move item to Archive.”
I use the Group as the projects and the items inside it I use as tasks, so everytime I create a new group I need to duplicate it to the Archive Board and create a new automation that is moving a group on the main board to another one with the same name on the Archive. It was a bit too much but now it´s working fine.
Thanks for your help.
Hi @Jenny! I did some research on this, and it looks like tags can’t be mapped when moving items to other boards. Here’s the article I found: https://support.monday.com/hc/en-us/articles/115005905685-The-Tags-Column
Hi Tanner, ohh that makes me so sad to hear, we will be loosing valuable data because of it (we might have to consider to use a different column type then) but thank you so much for your answer