Task Created event trigger

tiago_santos

Hello, everyone,

I created an automation to create Jira tasks when new action items are defined in a rolling meeting notes page. The problem here is that this Confluence document is a Live docs and any update on the Task wording is just creating new Jira tasks.

Can someone help me understand how to avoid these duplicates?

One of the issues I faced was adding the Jira task key to the Confluence task name (for auditability) and that just creates new Jira tasks.

Best regards,

Tiago Jobling Santos 

Bill Sheboy

Hi @tiago_santos 

For a question like this, I recommend posting images of your complete rule and the audit log details showing the rule execution.  Those will provide context for the community to offer better suggestions.  Until we see those...

 

Short answer: With a Live Doc in Confluence, there appear to be timing consistency symptoms for when the task_created event is raised...and thus a Confluence rule with the Task Created trigger does not always run when expected. 

As you appear to be on a paid license level, I recommend working with your Product Admin to submit a ticket to Atlassian Support to take a look: https://support.atlassian.com/contact/#/

When you hear back from them, please post what you learn to benefit the community.  Thanks!

 

For more details, and without seeing your specific automation rule...I hypothesize your rule looks something like this for the Live Doc page:

• trigger: Task Created
• action: do something with the {{task}} smart value's attributes, such as create a work item in Jira

 

When I use a rule like that with a basic Confluence page, it runs in a predicable manner because the page must be edited and saved / published for the changes to take effect.  Only new tasks trigger the rule, rather than any edits.

When I use that same rule with a Live Doc page, I observed differences:

1. As before, only creating a task triggered the rule; edits did not trigger the rule for me, unless...
2. At the end of typing the task, I pressed the Enter key, and thus created a new, empty task below the edited one
3. The detection of when the task was created, and how long it takes a person to enter the content, impacts what is in the {{task}} smart value.  I observed a couple of cases where when I paused a moment before typing, the rule triggered with empty {{task}} content (other than the id), and finishing my typing did not trigger the rule again.  As there is no equivalent of the "Re-fetch Work Item Data" for pages in Confluence automation, there is no fix for this on Live Doc pages.  Instead, one could try calling the REST API to reload the content.

 

Kind regards,
Bill