Create issue - Getting error on Reporter "Field 'reporter' cannot be set

Hello,

I am trying to use JIRA Rest API to create an issue in JIRA. I am seeing this error

{

"errorMessages": [],

"errors": {

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

}

}

I checked with the client and he says the user that I am using has the permission to create the issue. Client is using 4.X version? Please shed some light and any leads are highly appreciated.

Thanks in advance.

4 answers

1 accepted

Thanks a lot Nic for your support. I was able to resolve the issue. It was the permissions issues for the user that I was using and Just for more details: I was trying to access this from SF, to connect it make sure to use base64 encoded authentication and add this to http request header as AuthenticationHeader.

4 votes

Does the user you are logging in as have the right to "modify reporter"?

Is the reporter on the "create issue" screen at all?

Yes, I see the "reporter" field on the screen. And the username i am using here has the full permissions to create/modify.

Do I need to worry about the user I am using in the header? Do I need to check whether this user that I am using in the header also has the permission to create the issue?

I am invoking using the Rest API/Create issue.. here is the request:

{ "fields": { "project":{ "key": "Key"}, "summary": "REST EXAMPLE", "description": "Creating an issue via REST API", "issuetype": { "name": "Story"}, "customfield_11212": {

"self": "http://jiradev/rest/api/2/customFieldOption/12554",

"value": "Astra CSI",

"id": "12554"

}, "customfield_10324": [{

"self": "http://jiradev/rest/api/2/customFieldOption/12196",

"value": "Astra",

"id": "12196"

}], "reporter": {

"self": "http://jiradev/rest/api/2/user?username=name",

"name": "name",

"emailAddress": "email@email.com",

"displayName": "Name",

"active": true

} } }

Can you please check and let me know what I am missing.

Absolutely yes, the person you are running the REST request in is the one that needs the permissions, so the headers should match.

Your REST call looks good to me though.

So, You mean the User that I am using in the REST client header should be able to modify the reporter field on the JIRA side. That kind of persmission the user should have. Is that correct statement?

Yes, exactly.

The REST API respects the way Jira works on the front-end, so if the user can't do something in the UI, REST won't let them either.

Hi Nic, not sure what I am missing here. We are able to create the issue successfully on the UI and were also able to modify the reporter. But using the REST API, still getting the same issue when we are creating --> {

"errorMessages": [],

"errors": {

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

}

}

I would really appreciate if you could suggest me what we are missing here?

Nor am I. It really does sound like REST is not understanding who you are logging in as.

Could you try it without the reporter in the request and see what it does? Have a look at the issue it creates and see what it manages to set.

Thank you Nic! My problem was down to certain users not having the 'modify report' permission. Been battling with it for the last few hours. 

When getting errors like;

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

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

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


Solution: (you should create screen permission before creating issue with the code, only if you are creating it with the code)

Solution 1: 1st solution is the same as @Ravi Somisetty provided on this same page.

Solution 2: Here i will elaborate @Nic Brough [Adaptavist]'s answer.

Verify if the "reporter" or "assignee" or "summary", exists on the 'Create Issue'.

You may find the 'Create Issue' as;

  • Go to your JIRA project main page.
  • Click the "Project administration" , on the bottom of left sidebar.jiraProjectAdministrationCogSnap.PNG
  • Select the "Screens"  from left sidebar.jiraProjectScreenSnap.PNG
  • Now click the "Default Screen" . jiraProjectScreenSnap2.PNG.
  • Here is your "Create Issue" screen.jiraProjectScreenSnap3.PNG
  • Add any field that is missing.
  • ......and your code should succeed.

I am not creating with code and I see 'assign' 'summary' & 'reporter' all in Create Issue. 

I can only create JIRA tickets from Zendesk for one project. I have 4 more projects which I would like to have this ability. I currently receive the error "Field 'reporter' cannot be set. It is not on the appropriate screen, or unknown."

My current work around is to create the JIRA ticket in the project that works, then move the ticket to another project.

That strongly suggests that you are using a user who does not have access to the failing four projects, or if they do, they do not have the "edit reporter" permission.

Yes, I see the "reporter" field on the screen. And the username i am using here has the full permissions to create/modify.

Do I need to worry about the user I am using in the header? Do I need to check whether this user that I am using in the header also has the permission to create the issue?

I am invoking using the Rest API/Create issue.. here is the request:

{ "fields": { "project":{ "key": "Key"}, "summary": "REST EXAMPLE", "description": "Creating an issue via REST API", "issuetype": { "name": "Story"}, "customfield_11212": {

"self": "http://jiradev/rest/api/2/customFieldOption/12554",

"value": "Astra CSI",

"id": "12554"

}, "customfield_10324": [{

"self": "http://jiradev/rest/api/2/customFieldOption/12196",

"value": "Astra",

"id": "12196"

}], "reporter": {

"self": "http://jiradev/rest/api/2/user?username=name",

"name": "name",

"emailAddress": "email@email.com",

"displayName": "Name",

"active": true

} } }

Can you please check and let me know what I am missing.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,307 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot