Setting Reporter via Rest API Failing

Question

Hello,

I am attempting to create issues with different reporters and modify the reporter based on external factors. When attempting to create an issue, this is what the payload looks like:

{
   "fields": {
      "project": { "key": "Project Name" },
      "summary": "Test",
      "description": "This is a test",
      "issuetype": { "name": "Task" },
      "customfield_10000": "<epic-link>",
      "reporter": { "name": "Not.Me" },
      "fixVersions": [{ "id": "12345" }]
   }
}

This returns: "reporter": "Field 'reporter' cannot be set. It is not on the appropriate screen, or unknown."

I am an admin on the project I am attempting to modify the reporter for and admins have the "Modify Reporter" permission. I am accessing the API via a personal access token tied to my account.

I have confirmed that at least the names tested are recognized by JIRA to be the users "name" and that they are accessible via the gui. I have been able to successfully modify the reporter via a bulk edit but this appears to be the only way to edit these via the gui currently.

Chris Rogers · Answer

@Joe O_Connor that's correct; you'd need the reporter field added to whichever screen is associated with the create action for the project.

For example:

In this project, the Create Issue action is linked to the HOME - Create/Edit screen.  For your project, you'd want your admin to add the Reporter field to the existing screen (if it makes sense across projects) or create a screen specifically for your project where Reporter is present.

Joe O_Connor · Answer

I don't have overall admin rights and the current screen is a default screen for JIRA. Reporter is not a field in the screen currently but I can ask my JIRA admin to make a unique screen for this. Is "Reporter" just a filed that gets added under the Field Tab under the Screens menu for the project settings?

Chris Rogers · Answer

Hi @Joe O_Connor

You may have already checked this, but can you try adding the reporter field to the project's Create screen if it's not already there?  Most of my recent experience has been in cloud but sometimes Jira can be fussy about ensuring the field is on the right screen even if you don't intend on using it through the screen.