Cannot create a Jira OnDemand issue via Zendesk

[Markus Nordvik]

Every time I attempt to create an issue in Zendesk, I get the error:

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

I have given the Zendesk for JIRA user every permission I can.  When I use the Permission Helper for:

• User: Zendesk for JIRA
• Issue: Any issue
• Permission: Modify Reporter

Everything checks out as green.  Same for permissions Administer Projects, Create Issues, Edit Issues, Assign Issues, etc.

Everything I have read so far is that this is caused by a permissions problem, but I don't know which permission I need to be altering if Modify Reporter is checking out.

[Bruno Rosa · Accepted solution]

Markus, is the Reporter field on the "Create Issue" screen at all (on JIRA's side)? Please bear in mind that the REST API respects the way JIRA works on the front-end, so if users can't do something in the UI, REST won't let them either.

[Markus Nordvik]

Hi Bruno - that was it. I really appreciate the response.

[Farhan Ghani]

worked for me too, thank you

[francis]

Hi Markus,

Next to the DIY approach (which is kind of fun to do),  you can consider one of the issue synchronisation solutions - check query here?

One of these apps - Exalate - allows synchronizing between Jira and Zendesk (but also Jira, Github, ServiceNow, HP QC and more to come).  It provides a number of capabilities such as

• Multiple bidirectional connections
  You can link a single Zendesk instance with multiple other instances (Jira (all deployment models), ServiceNow, Github, ... and more to come), or link a single Jira with multiple Zendesk instances (or any permutation you can imagine)
  
  
• Completeness
  Whenever you exalate an issue to Jira, you can send over the complete ticket history (all comments, descriptions ...).  And comments are copied over as if they have been created locally.  Status synchronisation is possible also on Jira Server
  
• No dependencies between the different instances
  The target project is selected on the Jira side.  Whenever you need to make a change in your Jira configuration - you can do it without affecting the synchronisation agreements.

Let us know if you would like to see it in action - we're here to demo the capabilities of Exalate  and to discuss your requirements - just select a convenient timeslot here

Psst - Obviously I'm with the exalate team :-)

[Anton]

Hello! I have the exact same problem.

On our "create issue" screen, however, the reporter field is present.

---

Anton

[Enzo Iwata]

Did you check if in permissions scheme the "atlassian-addons-project-access" is granted to "Modify Reporter"?