Automation issues using "User Added to Group" trigger

[Ben SIlver]

Hello!
I've been wrestling with this automation for a while.

I think it should be a very simple setup, but it gives me a warning every time.

Here is what I would like to happen:

Trigger: A User is added to a group

Actions:

Create a "New Employee Checklist" page from template
(It would be great if the page could be called "[User] Checklist"

Update the permissions on that page so that the user owns the page and only the admins and that user can see it.

This feels very basic, but it gives me a very generic "This component mat be incompatible" error. It does the same thing if I try the "Restrict Page" action as well.

[Bill Sheboy]

Hi @Ben SIlver 

As @Shawn Doyle - ReleaseTEAM describes, the problem is the Change Page Owner action cannot "see" the newly created page, and so a branch is needed first.  However...

A new problem will occur: the branch will happen so quickly the page will not be available yet, preventing assignment of the page owner.  I just tested to confirm this happens in Jira Cloud because of the time required to make the page available to the rule.  Curiously...the {{page.id}} is available to support the branching!

I do not believe the Delay or Re-fetch Issue actions are available to slow down the rule, and so the only workarounds I can think of for this scenario are: 

• Use a call to the REST API with Send Web Action to slow the rule.  If this method is used, it could set the new page owner with Update Page and so eliminate the need for the Change Page Owner action.
• Use multiple rules, where a second rule changes the owner (probably based on some content stored in the page)

Kind regards,
Bill

[Shawn Doyle - ReleaseTEAM]

Hi @Ben SIlver 

Have you tried using a foreach after the publish page?

The way I read this message is that the automation can not guarantee the page will be publish before running the Change Page Owner, not sure why the warning doesn't just say "WARNING: Possible race condition", much cooler warning imho.  Putting the Change Page Owner into a foreach (or possibly branch) will cut down the chances of this race condition.