How Do I Automate the Estimated Completion Date?

[Kelley Mills]

Background:

Have a rule that sets a custom field "Date Review Due" when the parent issue is transitioned from step 1 to step 2.

Have another rule that creates sub-tasks and copies field values from the same parent issue (including Date Review Due) when a parent issue is transitioned from step 1 to step 2.

The Date Review Due field is based on the value entered in a separate number field, "# Pages".

Once Project Automation creates the sub-task, need it to update the Estimated Completion Date field in the sub-task, based on the value in the #Pages field.

Have tried variations of the following; can't show screen shots:. I am hoping that I don't have to include this in the rule that creates the sub-task because this means I have to create a rule for EVERY scenario - I have a lot of them.

When: Issue transitioned from Assign to Consult

If: Issue Type is "Parent Issue"

And: Sub-tasks are present

For Sub-tasks

If: # Pages is less than or equal to 3

Then: Edit Issue fields

Set Estimated Completion Date to {{now.plusBusinessDays(4)}}

etc.

Also tried

When: Issue is created

If: Issue Type is "subtask"

If: # Pages is less than or equal to 3

Then: Edit Issue fields

Set Estimated Completion Date to {{now.plusBusinessDays(4)}}

Nothing is working, and I am stumped

[Bill Sheboy · Accepted solution]

Hi @Kelley Mills 

I note that you said you can't show screen shots, but posting an image of your rule and the audit log from execution will help the community offer ideas.  Consider if there is a way to obscure what you do not want to show in the images before posting.

Without seeing the rule, I wonder...

• You note one rule is uses the parent transitioning status to create sub-tasks...
• And another rule triggers on sub-task creation.  When one rule can trigger another (intentionally) check the details to confirm the Allow rule trigger setting is enabled in the second rule.  When this is disabled, the rule engine detects rules trigged in close proximity as an error, and so stops the firing.

Best regards,

Bill

[Kelley Mills]

Thanks Bill. I will try this when I get to server... I was about to respond to my own post and ask if it is the trigger...

[Kelley Mills]

I am going to try what you said, and include the Related Issues condition, being as specific as possible about the details of the parent issue. Something like this:

[Bill Sheboy]

Hi, @Kelley Mills 

What is your Re-fetch for at the end of the rule?  That action is normally used when...

• You edit fields in the triggering issues, and need to access them later in the rule, so you reload them, or...
• A create issue trigger runs too fast, and so the data is not yet available.  Using the re-fetch slows things down and reloads so the data is available to continue processing.

Thanks!