It is not possible to pre-populate a field and make it show up in the create issue screen when creating a sub-task from a parent. You could choose to use the post function "Set Field Value from Parent" to populate the field with the parents issue, which will make the value show up in the first issue status following the create issue transition. To make things tidy, you could create a separate "create issue" screen for sub-tasks and hide the field on that screen, so you do not get presented with an empty field, but do have a proper populated field after the creation of the sub-task.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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!
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