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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Sub Tasks - Auto populate certain fields from parent on creation

Deleted user Mar 28, 2019


When we create a sub-task, is there a way to populate some of the fields before hand so that user does not have to type them again?




3 answers

I used an automation rule to accomplish this. 

The rule is run when issue is created (I also made a second rule to be used when issue is updated to continually refresh the subtasks). 

Use a branch rule and specify sub-tasks.

Use the "Edit issue fields". Select all of the fields you want to populate. Select where you want the information to come from (trigger issue, parent issue, epic issue).

It worked for me!

Good luck!


I also didn't want any users to edit this information. So I created a copy of my screen and named it "read-only" and then I removed the fields from this screen. In my screen scheme, under the edit operation, I associated the read-only screen. In my view screen, I have all of the fields. So now the user can view all of the fields but not change. 



Hi Sally can you post the steps as well regarding this because we  have tried the same but facing errors in the Automation. Looking for your reply.


0 votes
John Funk Community Leader Mar 28, 2019

Hi Sumit,

Yes, it is possible, and we do it a lot. Just edit the Create transition for the Sub-task (the transition from the first circle to the first status) and add a post function for each field that you want to populate on create. 

John Funk Community Leader Mar 28, 2019

Sorry, should have mentioned that we use the JMWE add-on to accomplish that. 

Deleted user Mar 31, 2019

Thanks John. JMWE is another paid add-on. Is there any other option apart from this?

John Funk Community Leader Apr 01, 2019

You could add a post function for the Create transition and try to use the Update Issue Custom Field post function. But not sure if that will actually work since it is not really an update but an initial population of the field. 

Hi @[deleted] ,

i have never done it before but my first thought is to create a custom script listener (maybe) with Scriptrunner addon so it can take values from parent issue and copy them to subtask.

Best Regards.



------------- Edit:

Go to the workflow of this issue. Find the create transition and in there, exist a post function tab. Click to add a post function and check the option "copy field values from parent to subtask issue".

Deleted user Mar 31, 2019

Thanks Christos.


One Query, Post function will be executed once the user saves the sub-task, right? Or it will be before that.


FYI we want to pre-populate the values when use clicks create sub-task from the parent Story/Task and the form gets loaded.




Hello @[deleted] ,

What do you mean after the user saves the subtask?

  • When the user clicks the subtask button a subtask is just created. Until you move to the subtask itself the fields will be already be populated if its done correctly :)

Another thing that u should do! Create a test environment of the instance... Make any changes and tests that you want and if they are working, apply them to the production instance



Deleted user Apr 01, 2019

@Christos Moysiadis 

What I mean is when user clicks on new sub-task, does the post-function apply before the user sees the sub-task form or post-function applies when user clicks Create button after entering all the details on the sub-task form.


Also, can the post function be executed based on issue type(sub-task) in this case?

We are using JIRA cloud. is it possible to create test instance there or should I work with a test project?



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events