I noticed all sub-tasks are being created with Parent info (Fix Version/s). In my workflows configuration the Fix version is a mandatory field (bug-workflow), except for sub-tasks (sub-tasks-workflow).
I have checked the options of the create transition on the workflow assigned to Sub-task issue types and there are no options to include parent info, in fact, I have added a Post Function on the Create transition to clean the field of Fix Version/s when the sub-task is created, but it didn't work.
Do you have any ideas why this is happening?
As mentioned in my comment on your question, if you build your workflows from scratch, this should definitely not be happening as you wouldn't have any additional function or property making certain fields be carried over (yes, based on my own program's system, but I'm 99% confident in this assertion).
Even though you said that you have checked your sub-tasks-workflow Create transition for unnecessary functions, please verify through the resolution in this link that you do not have a create transition "Set field from parent" post-function for Fix Version. https://confluence.atlassian.com/jirakb/how-to-automatically-map-fields-of-a-parent-ticket-to-a-new-sub-task-in-jira-cloud-779160741.html
In fact, what are your sub-task-workflow's post functions for Create? My built-from-scratch workflows for example came default only with the following create post-functions:
For any workflow I have, I believe these are the only 3 post-functions set.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs