Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Move a card to a list with similar name on another board

NFT Media I'm New Here Sep 22, 2022

Our departments all have their own board and then the company has one board of all the ongoing orders. We move the cards to different boards and then return them to the ongoing orders board when completed.

In the ongoing orders board, their is a list for each project title Order #  Customer Name - Project Name. The cards are made and distibuted to the different boards' department. Each card is titled Order #  Customer Name - Project Name - Process. When the department is finished with their processes, they then need to move it back to the original list on the ongoing orders board. 

For example, the list title is 123456 John Doe - x Project and a card titled 123456 John Doe - x Project - process 1.

Is there a way to efficiently move the card back to the ongoing orders board to the original list referencing the order number only? I have tried using wildcards but it is creating a new list. I have looked into cascading too, but it seams like it is only for finding cards and not lists.

1 comment

I would say wildcards are the way to go have you tried using separators to store multiple wildcards? So for example 123456 John Doe - x Project - process 1 would be {*} - {*} - {*} and

{wildcard1} would be 123456 John Doe

{wildcard2} would be x Project

{wildcard3} would be process 1


Maybe try posting this in the questions page you might get more help


Log in or Sign up to comment
Community showcase
Published in Trello

A Trello template to help you clean up your Confluence Space

Calling all Trello + Confluence users! We're celebrating all things Work and Wellness in our Confluence collection, where our team has been sharing activities to create more mindfulness around the ...

894 views 4 13
Read article

Atlassian Community Events