Just had a problem on 2/14/20 occur with a stable recipe that's was running for years that created Jira Issues and populated the Assignee field using the Jira username option that was set in the recipe.
Atlassian has changed their User object and depreciated/removed the username and userkey fields from the API, and will only accept the accountid to assign a valid user to the Assignee field (otherwise it's blank/unassigned).
Workato did not pick up this error. The recipe ran and completed successful with no error for not mapping/passing data to the Assignee field (even tried using a bad username). It created the Jira Issue, but Assignee was set to Unassigned. Switched to accountid option in recipe for Jira Assignee field and provided the user accountid data. Recipe ran successful, Jira Issue created with correct user assigned.
Here's a link to the Atlassian Deprecation notice: https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/
Send us a ticket, we will try our best to assist you with your problem