Why request-channel-type is set as "portal" even if ticket was created via API?

[Paweł Grams]

Hi,

We are working on some report to have more visibility on where tickets are created, and found request-channel-type issue property. According to this:
https://confluence.atlassian.com/jirakb/using-the-request-channel-type-property-on-filters-1188759288.html
There's 6 options, and one of those is "API".

Thing is - we have few integrations that create tickets via API, and this property is always set as "portal".

Is there any explanation for this?

Is there any other option to check which issues were created via API?

[Kris Dewachter]

Hi @Paweł Grams ,

My guess is that the API integration is not setting the correct value for that field when creating the ticket. And therefor it falls back on a default value (being "portal").

Best regards,

Kris

[Paweł Grams]

That's my guess as well. Question is - should it be the case? I think this is build-in Jira mechanics, and whatever comes via API should be marked as API.