Our stories can have subsequent sub-tasks based on needed refinement, and I want to locate the assignee of the prior related sub-task to make them the assignee of the additional new sub-task. This is what the scenario would look like under the story:
I want to find the assignee from the original sub-task based on a value in the summary field, and use that to assign the corresponding additional sub-task. Is there a way to get to that in Jira automation?
Hi @Chad Wege -- Welcome to the Atlassian Community!
Short answer: maybe
Longer answer...with a lot of caveats:
If your related subtasks have summaries in a consistent format as you described, and you can write a JQL statement to find them, you could use a Lookup Issues action to get at the correct one. Using an ORDER BY statement on the JQL for the lookup should help you select the correct one, making it always the last one returned.
Hi @Chad Wege and welcome to the community!
** Edited based upon @Bill Sheboy's response ** (Thank you Bill)
You could try something like this:
Hi @Mark Segall
Have you tried that technique before with a branch and created variable, shadowing?
My understanding is that branches with one-and-only-one issue (e.g. branch on Parent) get run-inline and so variable shadowing works. But, for all other branches which could process multiple issues (e.g. JQL, related issues, etc.) they are run asynchronously and in parallel...leading to the variable being created and disposed of with each loop pass. Thus it is a different variable than the one in the main flow.
Thanks, and kind regards,