Epic Link - Copy from Trigger Issue not working in Automation

[michelle.purcell]

Hello Community,

I wanted to reach out to see if anyone else is experience any problems recently with automations where you are creating a task or story under an epic.  Previously, I have been able to add the field to the create and input "Copy from Trigger issue".  For the past several days, it will show that the automation has run successfully, but is not linking to the Epic Link causing orphan stories/tasks.

This is occurring in previously published automation that ran without concern as of 10/16.

I know that changes are coming to remove Parent & Epic Link and move towards Parent, but automation does not have "Parent" as an option.  

Is anyone else experience this and if so, have you been able to resolve the issue?

Picture for context:

[Bill Sheboy · Accepted solution]

Hi @michelle.purcell 

You did not post your entire rule, yet from what I see...there is a condition on Issue Type equals epic.  If that is the trigger issue, it will not have an epic link, and so this rule could never have worked that way.  Please post your entire rule, and the audit log details showing the rule execution, to confirm that.

If I am incorrect (from what I see of your rule) and the trigger issue is not an epic...

I agree with your hypothesis that this is related to the epic field sunset / changes happening.

And as that parent field is not in the drop-down list for the edit action options, you could update your rule to use the smart value directly:

• type (or copy/paste) this smart value in the field: {{triggerIssue.parent.key}}
• when the smart value appears below the field, select it to use it

Kind regards,
Bill

[michelle.purcell]

@Bill Sheboy 

The trigger is the epic, and here is an instance where it works for task and sub tasks, but after further review I added for Epic Link "Copy from Epic" when I re-fetched the data for the recently created issue.  (Image 3) 

This automation is still working as expected which is why I assumed I could follow a similar format for the new automation I am building that would have a similar build just based on a different component that would fire these. 

Images for audit log for above:

So to your point though would it be creating a new smart value variable?  I have only used that functionality once and that was create automation for subtasks under a task as I am still learning (and have a lot to learn) with automation.  

Really appreciate your help. 

[Bill Sheboy]

To help see the big picture, I recommend using either a screen capture tool or browser addon so the entire rule can be captured in one image.  And so I am guessing a bit from some of the posted images showing the rule in pieces.

In the action where you create the issue (i.e. Task), the Epic Link is set to "Copy from Trigger Issue".  But that cannot work because the trigger issue is an epic, and so has no parent / value in the Epic Link field.  If you want the new task to have the trigger issue as its parent, please change that value to {{triggerIssue.key}}

Later there is a branch to that newly created Task...

• I believe the re-fetch is unnecessary as the trigger issue (the epic) has not changed
• Then an edit tries to copy the components and set the epic link (again)
• I believe the entire branch can be removed, and instead the components can be copied from the trigger issue when the Task is created.

If I am misunderstanding your rule, please let me know so I can try to help.

[michelle.purcell]

Bill,

Thank you so much for your assistance. The triggerIssue.key value worked for linking the epic.  I also was attempting to remove the fetch data and update fields for the copying of the labels and component from the epic.  However, I ran into an error.  Below is the audit log and rule. I also attempted to copy from Parent and experienced the same error. 

[Bill Sheboy]

Awesome; progress!

That error can be caused by a several things.  Let's check them in order of likelihood:

• Rules can get "glitched" by too many edit/publish cycles.  I do not know why this happens
  • Checking this:
    • Disable and re-enable your rule, and re-test
    • If that does not help, disable your original rule and re-create it from scratch, and re-test
  • Fix: Please see above
• Who is the rule actor? 
  • Checking this: You may find that at the top of the rule in the details.  The default is Automation for Jira, and if it has been change it can cause problems.
  • Fix: Set the actor back to Automation for Jira.
• Are the fields on the edit page view for a new Task? 
  • Checking this: If you create a new Task from the Create button at the top of the page, can you see the Components and Labels fields?
  • Fix: Work with your Jira site admin to ensure the fields are available for Tasks
• Very unlikely...There could be a problem with duplicate fields with the same name  
  • Checking this: Immediately before the action to create the new issue, please add a write to the audit to check the values:
    • components = {{triggerIssue.components}} and labels = {{triggerIssue.labels}}
  • Fix: Work with your Jira site admin to identify any duplicate fields and decide how to proceed

[michelle.purcell]

You are my hero!  Thank you.  It ended up being the fields were only included in default and edit of the task. I had to enable them for create and it worked like a charm.  I really appreciate all of your assistance.  Have a fantastic day! 

[Jerónimo García Álvarez]

https://community.atlassian.com/tnckb94959/rss/search?q=tags:(jira-software-cloud)