Project Automation set Epic Link is not working

[Björn Fihn]

I want some easy rule, after some EPIC is created and want that some Task it automaticly created and linked to the generated EPIC.

I dont know why but this is not working. If i created an EPIC then some new TASK is automaticly generated but withouth any link to the EPIC.

[Daniel Ebers]

Hi @Björn Fihn

it looks pretty good and should work from my point of view.

In order being able to add an Epic Link the user needs "Edit Issue Permission" on the Epic in question.
You could double check if this would be missing (I see you are creating an Epic but this would only need "Create Issue Permission" so it could be the edit is missing - and that would be leading to a failure).

However, this is just a guess and I am wondering if that would be the case an error shouldn't be visible from log.

Regards,
Daniel

[Piotr Zadrożny _Eyzee_]

Hi @Björn Fihn 

It depends what you describe as "link". If you are talking about epic link between Epic and automatically created Task then this rule should work as expected:

If you wish also to create standard link between issues (like "relates to" or "blocked by") you need to change a little your automation rule:

And the result then:

Best regards,

Piotr

[Björn Fihn]

Hi @Piotr Zadrożny _Eyzee_  

yes, i want it as "epic link between Epic and automatically created Task" but this is not woking and i dont know why.

Epic:

Taks automaticly created but without link to Epic:

[Piotr Zadrożny _Eyzee_]

@Björn Fihn please open your rule and check Audit log. Probably there you will find information why this rule does not work as expected.

[Björn Fihn]

@Piotr Zadrożny _Eyzee_ thats the most strange part it mentioned all is good :) 

[tim.wheeler]

I have exactly this same problem. I wonder if it is because the automation is quicker than the Epic creation?

I trigger the rule on Epic creation, it all works as expected. It sets other fields as specified, but cannot set the Epic Link and creates it blank. No error is shown.

[Bill Sheboy]

Hi @tim.wheeler 

First thing: I recommend creating a new question and posting images of your rule to get the most visibility to your question/use case, and add links to related community threads.  Otherwise only people watching older threads will see it.  Thanks!

Next, the Issue Created trigger has a known issue where it can fire before all of the data is available for use/conditions/etc.  I recommend *always* putting a Re-fetch action after the Issue Created trigger to slow down the rule and reload the data before any other rule components.

Kind regards,
Bill