API Call to Manipulate the Channel Type on Issue Create

[Joseph Hortch]

When creating a ticket from an external source, the ticket right now is saying Jira for Channel type.  I believe that has to do with the endpoint that we are using:  rest/api/2/issue.  However, has anyone had success in setting the Channel type using API?  

My research has pointed me to conclude that I cannot manipulate this because it is meta data that is being set by Jira's system:

• This field is managed internally by Jira/JSM.
• You cannot set or override the channel value via the standard Jira REST API (/rest/api/2/issue or /rest/api/3/issue)—it is not allowed, and even if you try to include it in your JSON, Jira will ignore it or throw an error.
• Atlassian does not support direct manipulation of this field for security and auditing reasons.

So how does one set Channel to API but what process would that value on a ticket read API if using APIs do not render it as such? 

[Carlos Garcia Navarro]

Hi @Joseph Hortch ,

Did you try creating via /rest/servicedeskapi/request?

https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/

[Arkadiusz Wroblewski]

Hello @Joseph Hortch 

@Carlos Garcia Navarro is right.

request-channel-type is not a value you normally set yourself. Jira Service Management assigns it from the endpoint that created the ticket.

Create it through the regular Jira issue API, and it will show as Jira.

Create it through the JSM request API, and it will show as API.

That means, if you want the channel to be API, the request needs to be created through the JSM request endpoint, not the standard Jira create issue endpoint.

Also, if the real goal is to track which external system sent the request, I would store that separately in a custom field. That gives you much cleaner reporting later.