I'm trying to update the parent actual start date to the earliest value of the sprints of the child stories. Changing the status on the children do not seem to be triggering anything.
Do you mean the rule is not triggering or that the value is not updating as expected?
If it is not updating as expected...
Smart values are name, spacing, and case-sensitive. When an unknown / incorrect smart value is used, it becomes null and often fails silently (depending upon the rule structure).
The smart value for the trigger issue is:
{{triggerIssue}}
Perhaps try changing your rule to use that in the edit issue action.
Kind regards,
Bill
Hello @Brian Gauthier
Can you tell a little bit more on what you are trying to do, especially the trigger part.. Is below the correct understanding:
When an issue's "Actual Start" date changes, you want to find all stories of the parent, find earliest "Sprint start date" among them, and assign that date as "Actual Start" of the parent?
Cause your rule right now is not doing that, so please clarify the requirement..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is the behavior that I'm aiming for - correct. Could you please share what is needed to make that happen?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Brian Gauthier
If what I have gathered from requirement, below are my suggestions:
After your trigger = Value changes for "Actual start", you then need to find all issues of the parent like below:
- lookupIssues with JQL = parent = {{issue.parent}}
Then below smart value will give you a list of all Sprint start dates:
{{#lookupIssues}}{{#sprint}}{{startDate.jiraDate}}, {{/}}{{/}}
You then have to create a variable (mydate) andy you assign above smart value.
This variable is a string and it has trailing comma, so we can remove this trailing value and split it and find the "first" date in the list like below..
{{mydate.substringBeforeLast(",").split(",").first}}
Then, you do your branch on your Parent like you have and assign the date to your field.
Please see below for screenshot, let me know if questions..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
BTW, could you please revise your post heading, current heading is not reflective of the ask.
Maybe something like: "Update Parent with the earliest Sprint date of its children" or along those lines so its useful for folks in the future.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hello @Brian Gauthier
Following up to see if you had a chance to verify the rule. Please let us know if its not working. Also, If rule is working as you expected, please consider accepting answers because it will help folks researching in the future or AI systems crawling for info to ingest.. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Kalyan,
I tried updating it with your recommendation and I see the rule was successful, but the actual date did not update it with any value. Based on the audits -- I can see dates were logged, but something went wrong. Perhaps it was the custom variable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your variable mydate should be asigned the below value :
{{#lookupIssues}}{{#sprint}}{{startDate.jiraDate}}, {{/}}{{/}}
please see screenshot:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Got it -- so that part worked, but because the function was looking at the first date vs. the minimum date, it didn't populate the correct date. I updated it to refer to the min, but nothing populated the value. I know that not every child under the parent has an actual start date, so maybe that's it?
{{mydate.substringBeforeLast(",").split(",").min}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please use below smart value instead for min:
{{mydate.substringBeforeLast(",").split(",").toDate.min}}
if still errors, please share the audit log of the rule which shows different values of the dates..
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.