Creating subtasks doesn't inherite components / fix-versions ?

[Christoph]

We have a number of projects where the questioned action works just fine.
But there is one (new) project where these items are not inherited.
Since this is supposed to be "standard functionality" I haven't found anything adjustable.

Checked: "Create Issue Transition" / "Screen Scheme" / "Field Config Scheme"
What did I forget / oversee ?
Thanks for any ideas / hints 

[teilor_soares · Accepted solution]

This is actually the expected behaviour. Subtasks do not inherite this fields from the parent task.

We have a Feature request for this in https://jira.atlassian.com/browse/JRA-5225, where we list some possible workarounds with third-party plugins, maybe you are using one of this workarounds in your other projects.

Cheers!
Teilor

[Christoph]

What would be the trigger for such an action. I have adjusted all schemes to be same as with one of the working projects with no sucess. Comparing exported XML workflows don't show any differences.
Hmm - Let's have weekend first .... More tests on Monday ...