I'm trying to create a workflow scheme where any new sub-tasks inherit "Component/s", "Fix Version/s" and a custom field from the parent issue. Unfortunately, it's not working. Whenever I attempt to create a sub-task, the fields are still blank. I've ensured that it's on the "Create" transition, but that the post-functions occur AFTER the "Create Initially" step.
There's now a very easy to configure way to keep fields for parents and sub-tasks in sync using Automation for JIRA!
(this example updates the description, but pretty much any field can be edited)
To clarify, I'm saying it's still blank after the issue creation. Right now, I've got it set up like:
Set field value from Parent (Component)
Set field value from Parent (Fix Version/s)
Set field value from Parent (Dev Team)
Re-index the issue (I've tried with and without this)
Fire "Issue Created" event.
I leave the fields empty, and hit the "Create" button. After hitting that create button, the sub-task is created, but the fields remain empty.
Hello Zack L,
Are you using a separate workflow for the "Subtask" issue type? I think you need 2 different workflows, 1 for bug/task/improvement etc and another one for Subtasks. Then for the subtasks workflow create transition, just add the post function Set field value from parent.
Yes I am. I've got a sub-task workflow along with a couple of other workflows assembled into my workflow scheme. I've specifically assigned sub-tasks to that workflow and double-checked that part of the config. I'm using the post-function you've listed, and the behavior is not working as listed.
A few things I've noticed that might help others:
* You do NOT need separate workflows for sub-types. Using only one workflow means that any non-sub-typ issue will try inheriting values from it's parent, but since it doesn't have one, nothing will happen, and it will use the values entered on creation.
* System Fields (like Component/s) need to be inherited BEFORE the "create initially" step
* Custom Fields can be placed AFTER the "create initially" step.
* You can have a field mandatory in parent issues and let it be inherited to sub-tasks and make the field optional in the subtask field configuration, then remove the field from the sub task create screen, that way user cannot enter a value only to see it being over-written by the inheritance function. Then make the field visible and mandatory in the edit screen, so that you can change the value in the sub-task later if you need to, still forcing the field to have a value.
Hope it helps!
Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events