Default Resolution causes issues to be committed with Resolution Date

Summary

If we have default resolution set in JIRA, committing issues through live plans causes the new tickets created in the process to have a Resolution Date, though no Resolution.

Steps to Reproduce

1. Create a project
2. Create a Portfolio plan and add the project as an issue source
3. Go to Resolutions page in JIRA (type g+g >> resolutions, under https://instance.atlassian.net/secure/admin/ViewResolutions.jspa)
4. Select a resolution as default
5. Add an issue to the plan
6. Commit it so it's created in JIRA

Expected Results

The ticket is created without Resolution Date, as it doesn't have a resolution.

Actual Results

It's created with no Resolution (as expected), but with a Resolution Date (not expected):

Workaround

Workaround 1

1. Unset default resolution (in 'Clear defaults') in Resolutions page
2. Commit
3. Set the default resolution back

Workaround 2 (suggested in comments below)

1. Change the 'Create' transition for this issue
2. Add a post-function to clear the 'resolution' (not resolution date)
   • This should also clean the resolution date