I'm trying to update a parent Initiative Start/End dates bases on the earliest/latest dates represented in its child Epics.
I want the Initiative Start Date to represent the earliest Start Date across its child Epics. Similarly, I want the Initiative End Date to represent the latest End Date across its child Epics.
For Edit work item fields:
Start Date: {{lookupIssues.due date.max}}
End Date: {{lookupIssues.start date.min}}
Can I not use Parent for Initiatives?
Hello, Good day. I see the rule trigger is value changed, instead you can go for scheduled rule and with the same syntax that you have. This should help your requirement. Thanks!
I'd like the Initiative to update automatically whenever a child Epic is updated (based on a child Task moving to a new Sprint).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried adding the manual trigger as you suggested to troubleshoot faster, and I'm getting the same throttled status I get with the status update trigger.
Automation for Jira has exceeded the allowed total processing time for this rule. Maximum allowed processing time over 12 hours is (in seconds):
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've tried a few different permutations now, including the attached, and I keep getting a throttled error :( I don't know how manually updating 1 Initiative could exceed the processing time
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can try the following logic
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.