Sub-Task No Longer Inherits Parent's Component Field

Issue Summary

When a user creates a sub-task in JIRA off an issue from a JIRA Agile project that already has a component field, the newly created sub-task does not inherit the parent issues Component.

Steps to Reproduce

1. Create a test component in a project e.g. Test Comp that is an Agile project
2. Create an issue.
3. Add the Test Comp component to the issue created above.
4. Remove the "Component/s" field from issue create screen
5. Create a sub-task; make sure Component/s field is hidden on the issue create dialog

Affects Version

The above issue was observed in JIRA 7.2.8, JIRA 7.3.x and we can confirm that it works correctly in JIRA 6.4.13 (the customer tested this on JIRA 6.4.8).

Expected Behavior

The sub-task would inherit the parent issue's component

Actual Behavior

The sub-task component field is empty and you would need to manually set it.

Workaround

1. You can manually set this.
2. You can use a plugin like Minyaa Suite which has a post function to make the Child issue inherit the parent issue's Component field.
   Please note that we do not provide support if you decide to proceed with the second suggestion.