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

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
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Sunday in Agility

You asked for it, so we delivered: images on issues have arrived

A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...

892 views 3 12
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