Inherit component from parent issue

[Jenni Chen]

I have set up an automation rule but it doesn't seem to be working. When i tried to create sub-task, still needed to manually choose the component.

[Bill Sheboy]

Hi @Jenni Chen 

It is possible this is a timing issue.  The Issue Created trigger can fire so quickly the issue data is not available at the time the rule runs.  This can cause later rule steps to not work as expected; for example, perhaps the parent is not visible / set yet for the copy of Components.

The work-around for this is to always add the Re-fetch Issue action immediately after the Issue Created trigger.  This will slow down the rule by about a second and reload the issue data before proceeding.

Please try that to see how it impacts the results.

Kind regards,
Bill

[Jenni Chen]

Thanks Bill, added a re-fetch issue action but unfortunately it is still working.

[Bill Sheboy]

Please move the Re-fetch up to immediately after the trigger, and then re-test:

• trigger: issue created
• action: re-fetch issue
• condition: issue type equals Sub-task
• action: edit issue fields for Components

[Jenni Chen]

Thanks again Bill, tried as you suggested, still not working. 

[Bill Sheboy]

Please show images of your Edit Issue action and the audit log details showing the rule execution.  Those may help to explain this.

Also, is this a company-managed or a team-managed project?  You may find that information at the bottom-left side of the page's expanding area.

[Marta Woźniak-Semeniuk]

After you create the issue the component should be changed to the one from parent - but the rule is only run at the moment you click create at the bottom of issue create form. 

[Jenni Chen]

Thanks Marta, I've made the 'component' field a mandatory field to mark before creating a task, so it looks like there is no better way to do this.