Jira smart values not populated into page content

[Steffen Burzlaff _K15t_]

Hey everyone,

I have an automation which is triggered when a Jira Work Item is created.

The automation has a simple if condition to check what the parent is set to.
Then based on that I want to create a page in Confluence with page content.

The page publishing should fill the "page content" field to populate some content directly on the page.

That the work item and the page are related to each other I wanted to add some details from the created work item:

So far so good. The page gets created, the title for it is set - but the table in the page content is empty.



I've tried several things (plain text, code formatting, etc.) but nothing seems to transfer the smart value content into the page content.
Is there a special formatting I need to respect, or is this simply a bug?

Thanks in advance!

Cheers,
Steffen

[Steffen Burzlaff _K15t_ · Accepted solution]

It seems that this is a timing issue.
I've added a delay action of 5 seconds between the generation of the work item and the creation of the page. Now it works.

[Bill Sheboy]

Hi @Steffen Burzlaff _K15t_ 

Well done solving this question yourself!

And as an FYI...

The Work Item Created trigger has a known racetrack timing error where the rule can start before the data is stable / available to the rule.  This can cause weird errors and empty smart values, leading to unpredictable results.  The Atlassian team knows about this, and is working on architectural changes to address this, with no announced timelines for resolution.

To mitigate this problem, I recommend two rule changes to what you show:

• Immediately after the trigger, add the Re-fetch Work Item Data action. 
  • This will slow the rule slightly, reloading the data before it proceeds. 
  • This is better than using the Delay() action, which only waits...and does not reload the data.
• Do not use the new feature to add conditions directly to the trigger with the Work Item Created trigger; instead add separate conditions after the Re-fetch
  • The reason for this one is when the work item data is unstable, the conditions in the trigger could return incorrect results
  • Adding the conditions after the Re-fetch improves the chances they will be accurate

Kind regards,
Bill