The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

CSM: API-created requests still invisible in Help Center "My requests" (CSM-33?) — need a verified w

Katy de Bruijne
September 6, 2026

Hi all,

 

We run a Customer Service Management (CSM) project (Jira Service Management, projectTypeKey customer_service) and are hitting a visibility issue that survives every configuration check we can find.

 

Setup: organization correctly added under Customer access (Access tab), Sharing set to "Requests from their organization", customer is the sole active member of that organization, no Security Level on the issue, correct Request Type set.

 

Test we ran: we created a brand new request via the proper endpoint, POST /rest/servicedeskapi/request, with serviceDeskId, requestTypeId, and raiseOnBehalfOf set to the customer's accountId. Response was 201 Created, reporter correctly returned as accountType "customer", and GET /rest/servicedeskapi/request/{id} returns 200 with a fully resolved request. The customer even received the usual email notification for a new request.

 

Despite all that, the request does not appear in that customer's "My requests" list on the Help Center — not under "All", "Created by me", or "Shared with my organisation".

 

We suspect this is related to CSM-33 ("Requests created in Jira/via API don't appear in the Help Center"), since the symptom matches, but we haven't been able to independently verify the exact mechanism or a working fix — we tried a suggested "raise" endpoint (helpcenter/{id}/issue/{key}/raise) in a few variations and it 404'd for us.

 

Has anyone actually hit this and found a confirmed, working fix or workaround (ideally with a concrete example), rather than just field edits (Request Type / Organization) after the fact, which don't seem to be enough? Also curious whether anyone has visibility into CSM-33's actual timeline.

 

Thanks!

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Ajay _view26_
Community Champion
September 6, 2026

Hi @Katy de Bruijne ,

Yes it looks like its related to https://jira.atlassian.com/browse/CSM-33

Katy de Bruijne
September 6, 2026

Thank you

0 votes
Arkadiusz Wroblewski
Community Champion
September 6, 2026

Hello @Katy de Bruijne 

About your primary suspicion, I also think it's related to csm33

As for For the documented CSM-33 workaround, the full endpoint is not on the normal your-site.atlassian.net/rest/... API:
POST https://api.atlassian.com/jsm/csm/cloudid/<cloudId>/api/v1/helpcenter/<helpCenterId>/issue/<issueKey>/raise
with:
Authorization: Bearer <OAuth token>
X-ExperimentalApi: opt-in


The caller also needs the CSM agent role, EDIT_ISSUES, access to that Customer Experience, and the OAuth scope:
write:csm-request:jira-service-management
Also make sure the helpCenterId is the Customer Experience / Help Center ID, not the serviceDeskId you used with /rest/servicedeskapi/request.


Successful call returns 200 and a supportSiteRequestUrl, for example:
{
"supportSiteRequestUrl":
"https://example.atlassian.net/helpcenter/.../user/requests/CSM-123"

Best,

Arek 🤠 

Katy de Bruijne
September 6, 2026

Thank you very much! This was very helpful

Like Arkadiusz Wroblewski likes this
Arkadiusz Wroblewski
Community Champion
September 7, 2026

Nothing to thanks. We are here to help each other 🤠

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events