Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Copy field from parent to sub-task


I have an issue type named: release and it has sub-task of type sub-bug.

I want the component of the release to be filled automatically in the Create Issue screen of the sub-bug, with the same component of the parent (release) issue.

Also, I want the Fix version of the release (the parent) to be copied as the Affected Version of the sub-bug (the sub-task) automatically, prefebely filled in the Create Issue screen (but not a MUST).


6 answers

1 accepted

4 votes
Answer accepted

I highly recommend JIRA Misc Worklfow Extensions:

It has post functions that allow you to set field value from parent (any field). I use it in my workflows and it does the job. It also has other quite useful workflow additions. :)

Hi there!

I have the same issue....

Any solution that is not sponsored by a paid app?


If you are interested to apply the settings in Global level "Copy to Subtask Plugin" is very helpful. Free but unsupported plugin.

For the record: "Copy to Subtask Plugin" can't handle Lables, since they aren't a "custom" field.

There's now a very easy to configure way to keep fields for parents and sub-tasks in sync using Automation for JIRA!

You can easily modify related issues (such as parents, stories, sub-tasks, epics, linked issues and even JQL) using our related issues action and condition:


(this example updates the description, but pretty much any field can be edited)

For more details see

It may be easy, but very expensive for cloud instances of JIRA!

There is no use-case 

Another valid option is the "copy value from parent to sub task" post function of Workflow Essentials for JIRA. Its not free but has a lot of functionality to create custom workflows without any programming.

This of course still seems only in the case of using it within your workflow and not doing bulk edit of fields that already exist in sub-task tickets that have already been created and now need to copy their parent data fields down without a workflow.

I'll recommend too a solution in case that you want to create the subtask on a transition. I'm doing something like that, but with two standart issue types and a issue link with the most famous Script Runner plugin. But I'm sure you already have that...

See my previous comment,



If it's ok for you to create the subtask in a transition, Bob has the solution for you at Please give this a try, it's really powerful since the latest versions


I create the sub-bug (of Sub-Task) type manually, when we find a bug.

Therefore I cannot use the "Create subtask in a transition" solution, or I don't understand you correctly.

The best solution would be to fill the parameters in the Sub-Task Create screen.



Yes, i understand that. You would need to train your users to use a workflow action instead an operation. what might help would be to disable the original operation, put the workflow action at the very beginning and make it a global action that is available in all steps. Ok, said that , i see this is a lot of effort so Ramiros suggestion seems much better. it would just require to add a groovy post function to the create transition of the sub-task workflow

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you