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

Rule is linking back to the template card instead of new card created from it.

So I have a rule that when a card with a particular name is added to my list To Do, it renames the card, sets a due date, and then finds another card (on a different board) and links my newly created card as a checklist item on the found card.  I have a template (in list Templates) that I use to create the card in the To Do list.  For some reason, the rule keeps linking the checklist item back to the template instead of my new card, even though the rule trigger is a card being added to list To Do, so I would think {triggercardname} would refer to the copy, not the template card.  Here's the rule:

home to do linking issues.jpg

Can anyone offer insight into why it's seeing the template card as the trigger? And what variable I should use instead to get it to link to my actual card in the To Do list instead of the template?


1 answer

1 accepted

0 votes
Answer accepted
Jared Atlassian Team Mar 23, 2022

It's not seeing the template card as the trigger; it just doesn't know about the name change to the trigger card because that was an earlier action in the rule.

Okay, that makes sense.  I changed {triggercardname} to {triggercardlink}, assuming that the link to the card doesn't change just because the name does, and now it works.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events