Comments
-
@Bill Sheboy , you're looking at the total in the first screenshot. I don't think that was the issue since I was able to add a new component in a different part of the rule then move it into place.
-
{{lookupIssues.first.key}} worked perfectly! Thanks, @Bill Sheboy !
-
Thanks, Bill. I ran some tests and I believe this would work, but I ended up creating a custom field and just populating it with the initiator along the way.
-
I was really hopeful to use this workaround for a similar issue, but my variable is a date and doesn't seem to translate.
-
I think I've got it working well enough for now. In each automation that creates recurring task clone, I run a lookup just before the clone. The JQL "parent in ({{issue}})" returns the list of sub-tasks which I then store in a custom field on the new clone. I then run an automation triggered by the creation of the clone. I…
-
Thanks for the reply, @Bill Sheboy . Good call on the re-fetch. I'll try your suggestion and see where it leads me.
-
I do something similar except I simply check if the field value Sprint is empty. I then update that value to the current open sprint. So long as you never want to intentionally leave issues outside of any sprints, this should work.
-
@Bill Sheboy Thanks! That got me to where I needed to be. Just using .asNumber wasn't enough, but using .value.asNumber worked. {{issue.created.withDayOfMonth(issue.Due Day.value.asNumber)}}
-
@Bill Sheboy Even when written to the audit log I get an empty value whether I use .value or not. Due Day is a Select List (single choice) with a series of numeric choices.
-
@Bill Sheboy Yep. I get the same result. There is no error, but the field is left empty.
-
Hello @Bill Sheboy , thanks for the reply. Here is a collection of screenshots to demonstrate what I am seeing. First I convert the custom field value to a temporary value that displays correctly in the audit log as "1". Due Day: 1 The issue had a starting value in the Due Date field of 2021-06-01. When this rule runs, the…
