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

No way to trigger automation when comment is edited or deleted?


I'm implemeting one-way card mirroring, so that when I edit a card on Board 1, the edits show up on the mirrored card on Board 2.

I can do this without issue for most properties. For example, I can trigger an automation when I add description or edit an existing one on a card on Board 1.



But with comments, I can seemingly only trigger an automation when a comment is posted, not when it's edited or deleted.

This is very frustrating! It means that if I edit or a delete a comment on a card on Board 1, the edit or deletion won't be reflected on the mirrored card on Board 2.


Desired Solution

The most natural solution would be to make "posted" in the "when a comment is posted to a card..." trigger a dropdown with options "posted", "edited", and "deleted".

A less intuitive solution, but one that would still work, is something analogous to what's in place for card name and description, where the trigger is "when the [name/description] of a card starts with [text]..."

If for [text] you input the wildcard {*}, then the automation will be triggered when a name or description is added or edited to anything at all (or deleted, i.e. cleared). I find this pretty nonintuitive, but it does work.



🙏 Trello/Atlassian team, can you please implement this change? It should be very easy to do and would close the loop on comment automations.

❓Does anyone know a workaround that achieve this?



Side note: Some other bizarre gaps in automation triggers I've discovered when implementing this one-way mirroring:

  1. You can't add/remove a variable label unless you use a super hacky workaround of creating a colorless label. And even then, you have to manually create identical (same color and name) labels on both boards, or else the mirrored labels will be colorless even if the original labels aren't.
  2. You can't trigger any automation based on card covers.
  3. You can't set a start/due date based on a non custom field variable, e.g. if you want to set a date on the mirrored card when you set one on the trigger card. The only option is another super hacky workaround, where you create a custom field to store the date value and then set the due date on the mirrored card based on that.

Desired solutions for these:

  1. Don't make us select labels based on both color and name in automation triggers. (If this is a problem because there can be labels of the same color with different names and others of the same name with different colors, then let us choose based on label ID.)
  2. Offer automation triggers for adding/editing/deleting card covers.
  3. Let us set/move start/due dates with variables like {triggercardduedate}.

1 answer

1 vote
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.
Oct 27, 2022


Based on my own RYO mirroring, working comment is tricky since the power up or bot is attached with a admin credentials while comments are specific to the board user. For example in the mirror board a added comment would have <user> : made or edit this comment. Another challenge I faced was in deleted comments.  Just like deletion of card, the data is actually erased in the database. 

for your other list of requirements, and if can do some coding, you should be able to use http request to handle them. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events