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

[Milan Seth]

I have integrated JIRA cloud version with Pega 7.4. Integration was successful but I get this error "Field 'reporter' cannot be set. It is not on the appropriate screen, or unknown." on creating user stories,bugs etc.

Can someone help with this ?

[Nic Brough _Adaptavist_ · Accepted solution]

Whatever Pega is trying to do, it is doing it via "create issue" or "edit issue", and it is using a user account in Jira to do it.

You need to make sure that the account Pega is using has the right permissions in the project (create and/or edit, and "edit reporter" too), and that the reporter field is on the screens.  Try creating an issue there manually and see if it's there.

[Milan Seth]

Thanks for the response. It worked :)

[Joshua Warren]

I am also having this problem. I have checked that my custom field is on all screens. I am using the python module (jira-python: https://github.com/pycontribs/jira) so it is not an issue with my JSON query (well - I trust it). I am admin so permissions should not be an issue. I can create the Issue manually (and the field appears there). 

[Nic Brough _Adaptavist_]

Forget admin logins, they just give you admin rights, not project rights.

Look at the user you are using for the connection.  If you log in as that user rather than admin, can you see the issue you are trying to update remotely?  Can you click edit, and see the field on screen?

If you can, then can you try the example curl commands in the docs for updating an issue with that account - does that work?

[Joshua Warren]

I am project admin too! And I'm using that login for the connection. And yes I can edit and see the field on screen. However I get the same error from the curl command. The command works if I do not set that field.

[Joshua Warren]

SOLVED: I didn't realise I needed to refer the custom field by it's customField_ID name, rather than the name I gave it! 

Thanks for your help though Nic

[Noel Garside]

fields array key customfield_10036 where 10036 is the id of the field rather than the name of the field

[Justin Rice]

I am having this same issue as well. I had an admin create an API key. This admin is also an admin of the project as well as the account. The request body looks like this:

{
"update": {},
"fields": {
"summary": "Main order flow broken",
"issuetype": {
"self": "https://BLAHBLAH.net/rest/api/3/issuetype/3",
"id": "3",
"description": "A task that needs to be done.",
"name": "Task",
"subtask": false,
"avatarId": 10318
},
"project": {
"id": "10000"
},
"reporter": {
"id": "ACTUAL_USER_ID"
},
"displayName": "Admin",
"active": true,
"timeZone": "America/Chicago",
"locale": "en_US"
},
"description": {
"type": "doc",
"version": 1,
"content": [
{
"type": "paragraph",
"content": [
{
"text": "Order entry fails when selecting supplier.",
"type": "text"
}
]
}
]
}
}
}

I have the post request going to: rest/api/3/issue?

And the error I get back is:

{    "errorMessages": [],    
     "errors": {        
"reporter": 
"Field 'reporter' cannot be set. It is not on the appropriate screen, or unknown."    
}}