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, where we list some possible workarounds with third-party plugins, maybe you are using one of this workarounds in your other projects.



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
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

229 views 1 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