Can I pre-populate the Create subtask screen with values from the parent issue using jjupin liveFields?

[Brian Leysath]

I've been searching for a way to pre-populate the fields on the Create Subtask screen with the corresponding values from the (soon to be) parent issue.  I tried using the Behaviours plugin, but am not having any luck.  Is this possible with JJupin and Live Fields?

Note - I realize I can create the populated subtask with the ScriptRunner plugin and a post function;  but that doesn't meet the user need whereas pre-populating the fields would.

Thank you in advance for any insight or assistance you can provide!

[Raluca Panait · Accepted solution]

Hi,

As Alexandra said , you can use JJUPIN and Live Fields for what you need.

You can use the sil scripts below :

lfInstantHook({"issueType"}, "hook.sil");
lfWatch("issueType", {"issueType"}, "hook.sil");

if(argv["screen"] == "create-subtask" && argv["issueType"] == "Sub-task") {
	lfSet("summary", summary);
    lfSet("description", desc);
    lfSet("components", components);
    lfSet("affectedVersions", affectedVersions);
}

Hope this helps,

Raluca

[Brian Leysath]

First of all, thank you all for taking the time to respond. I tried the code above and it looks like this is going to work perfectly. I really appreciate it!

[Antoin Stanton]

Hi Raluca,

This answer seems very helpful to someone who wants sub-tasks to inherit the field values of the "parent" issue.

However, I'm wondering how would it be possible to reproduce the same system for creating "Issues in Epics"?

Thanks,

Antóin

[Alexandra Topoloaga]

Hi Brian,

Yes you can do it using JJUPIN and Live Fields.
We have an example here, it can be adapted very easy. 
If you have any other questions, we're eager to help. 

Best Regards,

Alexandra 

[Błażej O_]

I think what Brian have been asking is how he can read the values of the parent issue, if there is technically no child in context yet (he's on the create sub-task issue screen).

[Alexandra Topoloaga]

You're right, Blazej. I haven't understood it at first. Raluca's example should fit Brian's needs. :)

[eric anier]

Hi Brian,

If the parent (soon to be) issue is not yet available, do you mean that parent and subtask will be created at the same time from the create screen? and both parent/subtask contains same values on some fields? Is this what you need?