Sub-task assignee not updating with Quick Subtasks plugin

[Danny Powell]

I have installed the JIRA Quick Subtasks plugin and everything seems to be working properly except I can't update the assignee field for the subtasks. Other values like Component, description, fixversion, etc are updated as specified in the template, with the exception of "assignee". That field remains the same as the parent issue. Any ideas where to look? I tried using a basic template like below and still no luck.

- Subtask Summary / assignee:"admin"

Running JIRA 6.3.11

[Danny Powell · Accepted solution]

@Micha Kops I found the problem. In the workflow, I had an "assign issue" postfunction on issue creation step. I removed that and the assignee updates correctly. I apologize for not thinking/checking on this sooner. Thank you for your assistance.

[Micha Kops]

@Danny Powell I'm glad to hear that it's working now :)

[Micha Kops]

@Danny Powell It would be nice if you could configure the logging for the plugin to provide more details.

Please go to System > Logging & Profiling > Configure logging level for another package > Package name > And enter 'com.hascode' (without the quotes) and set Logging Level to 'DEBUG' (no restart required)
Create a subtask using a template like 

- Test Subtask / assignee:"admin"

Take an excerpt from the logs - could look like this sample from my test system:

[..]
2015-01-21 21:14:01,673 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.rest.CreateMultipleSubtasksRestService] createSubtasks called with issueKey: DEMO-1 and template: - Test Subtask / assignee:"admin"
2015-01-21 21:14:01,675 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.rest.CreateMultipleSubtasksRestService] returning resolved issue type: Sub-task
2015-01-21 21:14:01,676 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] 1 lines extracted from given string - Test Subtask / assignee:"admin"
2015-01-21 21:14:01,676 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] groups matched for given expression - Test Subtask / assignee:"admin": 2
2015-01-21 21:14:01,677 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] summary extracted: Test Subtask
2015-01-21 21:14:01,677 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] additional part: / assignee:"admin"
2015-01-21 21:14:01,677 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] additional part does match the optional part pattern
2015-01-21 21:14:01,677 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] optional part extracted: / assignee:"admin"
2015-01-21 21:14:01,677 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] assignee matcher does match now testing for forbidden characters
2015-01-21 21:14:01,677 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] extracted assignee: admin
2015-01-21 21:14:01,677 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] estimation matcher does not match
2015-01-21 21:14:01,677 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] component matcher does not match
2015-01-21 21:14:01,677 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] description matcher does not match
2015-01-21 21:14:01,677 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] priority matcher does not match
2015-01-21 21:14:01,677 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] component matcher does not match
2015-01-21 21:14:01,677 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] fix-version matcher does not match
2015-01-21 21:14:01,677 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] affected-version matcher does not match
2015-01-21 21:14:01,678 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] issue type matcher does not match
2015-01-21 21:14:01,678 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] reporter matcher does not match
2015-01-21 21:14:01,678 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] due-date matcher does not match
2015-01-21 21:14:01,678 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.DslProcessorImpl] 1 dtos aggregated: [IssueDto [summary=Test Subtask, estimated=null, assignee=admin, description=null, priority=null, fixVersion=null, issueType=null, affectedVersion=null, dueDate=null, reporter=null, customFields={}, components=[], labels=[]]]
2015-01-21 21:14:01,678 http-bio-2990-exec-3 INFO admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.Dto2IssueMapper] mapping subtask context: BasicSubtasksContext [reporter=admin(admin), issue=DEMO-1, dslString=- Test Subtask / assignee:"admin", issueType=com.atlassian.jira.issue.issuetype.IssueTypeImpl@f04eb6f2, prefixSubtasks=false]
2015-01-21 21:14:01,679 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.BasicSummaryInterpolator] trying to resolve property summary
2015-01-21 21:14:01,687 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.BasicSummaryInterpolator] trying to resolve property assignee
2015-01-21 21:14:01,688 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.BasicSummaryInterpolator] trying to resolve property key
2015-01-21 21:14:01,688 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.Dto2IssueMapper] no specialized subtask issue type set, using fallback.
2015-01-21 21:14:01,688 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.Dto2IssueMapper] searching for an existing assignee with given name: admin
2015-01-21 21:14:01,688 http-bio-2990-exec-3 DEBUG admin 1274x7714x1 1l5u0yp 127.0.0.1 /rest/subtasks-create/1.0/facility/issue/DEMO-1 [plugin.quick_subtasks.core.Dto2IssueMapper] existing assignee for given name found admin
[..]

The last two lines could give us a hint why setting the assignee does not work.

[Danny Powell]

@Micha Kops

Yes the 'admin' does exist on our instance. I also used other users, but it always shows the name of the person creating all the sub-tasks. I looked in the logs and I am seeing several lines like below:

2015-01-19 09:16:46,784 http-bio-8080-exec-29 INFO dpowell 556x77578x3 srsk8i 192.168.4.105 /download/resources/com.atlassian.jira-core-project-templates:jira-softwaredevelopment-item/story.png [plugin.webresource.servlet.PluginResourceDownload] Could not locate resource: /download/resources/com.atlassian.jira-core-project-templates:jira-softwaredevelopment-item/story.png

Any ideas where to look next?

[Micha Kops]

@Danny Powell I'm not able to reproduce the problem described (using JIRA 6.3.11 and Quick Subtask Plugin v3.2.1). Does the problem still exist? A user with loginname = 'admin' does exist on your JIRA instance? Do the log files contain any hint?