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

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 

2 answers

1 accepted

0 votes
Accepted answer

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

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 ...

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,731 views 17 21
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you