How to copy field from parent to subtask on create screen using behaviour

Rob B_jadbuo

I want to be use a behaviour to copy multiple fields from the parent to the subtask so they appear before i create the subtask.

I have figured out how to do the summary using other posts on the community, but i cant get the custom fields to work.

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.customfields.option.Option
import com.atlassian.jira.issue.fields.CustomField
import com.onresolve.jira.groovy.user.FieldBehaviours
import com.onresolve.jira.groovy.user.FormField
import groovy.transform.BaseScript

import java.sql.Timestamp

import static com.atlassian.jira.issue.IssueFieldConstants.*

@BaseScript FieldBehaviours fieldBehaviours

FormField field = getFieldById(getFieldChanged())
FormField parent = getFieldById("parentIssueId")
Long parentIssueId = parent.getFormValue() as Long


if (!parentIssueId || field.getFormValue()) {
// this is not a subtask, or the field already has data
return
}

def issueManager = ComponentAccessor.getIssueManager()
def parentIssue = issueManager.getIssueObject(parentIssueId)
def customFieldManager = ComponentAccessor.getCustomFieldManager()
def cfspid = getFieldByName("SPID")

// REMOVE OR MODIFY THE SETTING OF THESE FIELDS AS NECESSARY
getFieldById(SUMMARY).setFormValue(parentIssue.summary)
//getFieldById(SPID).setFormValue(field.cfspid)

 

Ram Kumar Aravindakshan _Adaptavist_

Hi @Rob B

You cannot get the values from the Parent issue field and pass them to the Sub-Task during issue creation. Why? This is because the issue (Sub-task) doesn't exist yet. Hence, the link between the Parent issue and the Sub-task doesn't exit, so you cannot invoke the value from the Parent issue.

To proceed,  I suggest you first create an Issue Picker scripted field so you can select the Parent issue from it.

Once the Parent issue is selected from the Issue Picker, you can invoke the values from the system field as well as the custom field(s) from the selected Parent issue and pass it to the Sub-task on the Create screen.

Below is a screenshot of the Issue Picker configuration:-

Next, you must create a Server-Side Behavior for the Issue Picker field.

Below is the sample working code for your reference:-

import com.adaptavist.hapi.jira.issues.Issues
import com.onresolve.jira.groovy.user.FieldBehaviours
import groovy.transform.BaseScript

@BaseScript FieldBehaviours behaviours
def issuePicker = getFieldById(fieldChanged)
def issuePickerValue = issuePicker.value.toString()

def sampleMultiLine = getFieldByName('Sample Multi Line')
def sampleNumber = getFieldByName('Sample Number')

if (issuePickerValue == 'null') {
    return
} 

def parentIssue = Issues.getByKey(issuePickerValue)
def parentMultiLineValue = parentIssue.getCustomFieldValue('Sample Multi Line')
def parentNumberValue = parentIssue.getCustomFieldValue('Sample Number')
sampleMultiLine.setFormValue(parentMultiLineValue)
sampleNumber.setFormValue(parentNumberValue)

Please note that the sample code above is not 100% exact to your environment. Hence, you will need to make the required modifications.

Below is a screenshot of the Issue Picker Behaviour configuration:-

Below are a couple of test screenshots for your reference:-

1. Below is a screenshot of the Parent issue. In it, 2 custom fields have been set with a value, i.e. Sample Multi Line and Sample Number.

 

2. Next, with the Sub-task's Create screen, no values are passed into the Sample Multi Line and Sample Number fields as shown below:-

 

3. Finally, once the Parent issue has been selected from the Issue Picker, the values from the custom fields are passed to the Sub-task as shown in the screenshot below:- 

I hope this helps to solve your question. :-)

Thank you and Kind regards,

Ram