Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

linked card automation question

I have a board with two lists projects, tasks.

The project cards have a checklist names TASKS

The project cards have some custom text fields cardname, program.

I have an automation thats creates task cards in the task list when items are added to the TASKS check list on the project cards by converting it to a linked card.


  1. Is there a way to add the cardname field from the title of the project card to the task card?
  2. Is there a way to copy the program field from the project card to the task card?

1 answer

1 accepted

0 votes
Answer accepted
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 08, 2023

So this solution is a two-parter.

The first part manually converts the card in to a linked card. Using 5 commands instead of 1. For the sole purpose of having the new card's name include the two custom field variables in a specific format.



The second rule is specifically looking for cards created with the specific format in the name, and uses Wildcards to extract them and set them in to its own custom fields, before getting rid of all the extra data in the name.


Note 1 : (The other reason the first rule manually creates the card, is that once you convert, you cannot then access the custom field of other cards (ie the project card) without some kind of chicanery. With the other workaround I know of only allowing access to a single custom field)

Note 2 : (The trigger exception in the first rule is so that it can replace the checklist item with a link to the created card, without re-triggering the rule.)

Note 3 : (You can mess about with the commands in the first rule to tailor the connection between the project and task cards. one way link or two ways. or eschew attachments altogether and adding a checklist PROJECT with a link back to the project card via {triggercardlink} for instance.)

Note 4 : (Once the rules have run their course, the checklist item in TASKS will temporarily have the "task-name#cardname#project" pattern. But this is merely because the Trello links are not up to date with the actual card's name. Refreshing the page will update the link to show the correct name.)

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events