Jira Spoke "Create Issue" Action – Reporter field failing with Email even when Server Type is set to Server

Atlassian Developer Tools
1

Hi everyone,

I’m currently using the ServiceNow Jira Spoke to automate the creation of Jira Stories from ServiceNow. I’ve encountered a discrepancy in how the Reporter field is being handled between Jira Server and Jira Cloud configurations.

The Jira Spoke documentation suggests that if the Server Type is set to “Server”, the action expects a User Name (e.g., mohan.m@xyz.com) for the Reporter field. If set to “Cloud”, it expects the Account ID.

However, in our environment:

  1. When configured as “Server,” passing the User Name fails ( the Reporter remains empty/errors).

  2. The action only works when we provide the Account ID, regardless of whether the connection is toggled to Server or Cloud.

My Questions:

  1. Has anyone else experienced the Jira Spoke ignoring the “User Name” input for the Reporter field on Server/Data Center instances?

  2. Is there a specific Jira System Setting (like GDPR/Privacy settings) that disables user lookup by User Name via the API, effectively forcing the use of Account IDs even for on-premise setups?

  3. Is this a known bug in the Spoke logic where the payload structure defaults to accountId regardless of the server_type attribute?