Groovy script for sub-task is not working in jira 7

Question

Hi,

We recently upgraded JIRA to version 7.2.4 and script runner plugin 4.3.16 is used.

The groovy scripts used for sub-task creation, assignee, set due date is not working now.

I used the below script in JIRA 6 at additional issue actions section and it was working there.

import com.atlassian.jira.user.ApplicationUsers

issue.summary = sourceIssue.summary + ' - Summary ';
//SET ASSIGNEE FOR Sub-task
if (cfValues['Product]*.value.contains("A")){ 
cfParent = customFieldManager.getCustomFieldObjectByName('Userpickerfield')
parentMyFieldValue = transientVars["issue"].getCustomFieldValue(cfParent)
if (parentMyFieldValue != null)
{
issue.setAssignee(ApplicationUsers.toDirectoryUser(parentMyFieldValue))
 }
//SET DUE DATE
def cf = customFieldManager.getCustomFieldObjectByName('Datefield')
val = issue.getCustomFieldValue(cf) - 9
issue.setDueDate(val)
}

I am getting error at bold lines.

Please suggest a solution.

Thanks

Sachin Dhamale_o1c5zi · Answer

If you corrected mentioned error and the error mentioned by me then it should worked

you can write a log.error("==="+ parentMyFieldValue) and check in the log file that you get a expected value for assignee.

like this you can debug your script line by line and find out the where exactly error comes

Krithica Gowri Shankar · Answer

1.cfParent- The variable cfParent is undeclared.

2. parentMyFieldValue - The variable parentMyFieldValue is undeclared.

3. getCustomFieldValue-Cannot find matching method

4.issue.setAssignee--Cannot find matching method

even we corrected these errors, sub-tasks are not getting assigned to the custom field value which we entered as users.

Sachin Dhamale_o1c5zi · Answer

* What exactly error you get in first bold Line?
* On Second Bold Line: You cannot set the long or int value into Due Date. It has to be Date Object.