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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,826 views 12 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot