Hi there, this automation does what I want it to do, however the subtask is getting the old due date from the parent. Here is my scenario:
The user is updating a field (Network Type) in the parent to one of 3 values (Simple, Standard, Complex). The automation will kick in and change the due date on the parent as follows:
Simple = {{issue.created.plusBusinessDays(20)}}
Standard = {{issue.created.plusBusinessDays(20)}}
Complex = {{issue.created.plusBusinessDays(60)}}
This part of the automation works great
When the automation branches to the subtasks I set the subtask due date to {{triggerIssue.duedate}}
Unfortunately, the subtask due date is set to the original parent due date, not the updated date.
How can I fix this? Thanks in advance.
Hi Glen
It may be advisable to include a re-fetch component before updating the subtask to ensure that the automation retrieves the most current data from the issue.
Ref: https://support.atlassian.com/automation/kb/usage-of-refetch-component/
Best regards
Sam
Thanks Sam, I think this is cloud only. my JIRA is internally hosted.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You will need to create a new automation that triggers whenever the due date is updated, as the current automation is caching the due date and there is no method in DC to reflect the data accurately.
The process in the Cloud is straightforward, as it allows for the utilization of the Re-Fetch component.
Hope this helps
Sam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @glen_adams_bellmts_ca -- Welcome to the Atlassian Community!
For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!
Until we see those...
If you followed the examples in that linked thread, you may have a problem in either the branches or in the smart value used to change the dates. Seeing the details of your rule and the audit log will help confirm the cause.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Bill, here are some images:
For the Simple network type:
Then later in the automation:
I hope this helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please show your entire in one image for context. For longer rules, you may capture the image with an app or browser addon to scroll the page.
Please also show an image of the audit log details for the rule execution. That will show which rule steps happened, and allow comparison to what you expected.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.