Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

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

Paweł Grams
Paweł Grams Oct 24, 2023

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?

Answer
Watch
Like Be the first to like this
94 views

1 answer

0 votes
Kris Dewachter
Kris Dewachter
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
Oct 24, 2023

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

View More Comments
Paweł Grams
Paweł Grams Oct 27, 2023

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.

Like
Reply

Suggest an answer

Log in or Sign up to answer
Jira Service Desk
Jira Service Management
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events

See all events