Jira trigger creates 2 Trello Cards/Lists. Adding an issue to an existing Sprint acts like 2 events, and triggers twice

I’m still new to n8n. I created this workflow but it double triggers, creating: cards when set to cards, and lists when set to lists. So I get two either way.

Jira Cloud
n8n Cloud

I’ve been messing with it for a while now and I’m lost. I think it’s something obvious, but I can’t be sure.
It worked great when I had the JQL filter set to “Status =” but if I recreate that scenario it still makes 2 (lists or cards).

Any insights?


Do you have the workflow activated? If so and you do a manual execution by clicking ‘execute workflow’, the workflow might execute twice:

  1. The saved version will execute, but won’t be shown in the editor (a ‘production’ execution)
  2. The latest version in the editor will execute and will be shown in the editor (a ‘test’ or ‘manual’ execution)

However once you’ve finished testing and the trigger is running automatically, it should only run the workflow once.

Spent some time troubleshooting and simplifying.

My Event is “Issue Updated”
If the “Update” is me moving an issue into the current sprint, it triggers twice for some reason. Not sure if that’s a bug or a feature. I tried comparing json outputs for: Issue Summary change vs Issue Sprint change, but couldn’t find any clues.

The workaround I came up with is:
Event: Issue update
JQL: status != Done AND Sprint = TESTME AND issuetype != Sub-task AND labels = List

So, adding the Issue to the Sprint does nothing in n8n, but when I do so Jira is automated to add the Label “List”, which is the trigger for n8n.

I know it’s obscure, but maybe it will help someone in the future.

Thanks for reporting back, @Mike8! Sounds like it may be some kind of quirk in how webhooks work on the Jira side.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.