Issue Summary

Requests created from within the agent view don't appear in the support site when you access "My requests".

Steps to Reproduce

1. Create a CSM ticket in the agent view (via the Create button)
2. Assign a reporter
3. Logged in as the reporter, go to the support site
4. Go to My requests

Expected Results

There should be a mechanism to select how to share with the reporter updates through the support site.

Actual Results

There is currently not such mechanism by design, only support requests created through CSM channels are represented in the support site. 

Workaround

(Updated) Pick a SOURCE = a ticket that already displays correctly in the portal (e.g. one raised via the Help Center) and has exactly one form. Your TARGET = the API/agent-created ticket. All calls use Basic Auth (ATLASSIAN_EMAIL:ATLASSIAN_API_TOKEN).

 1.  Find the SOURCE form (this is the endpoint to use — not project-forms):

GET https://api.atlassian.com/jira/forms/cloud/\{cloudId}/issue/{source}/form
 

2.  (Optional) Read TARGET summary/description to populate the form:

GET https://\{site}/rest/api/3/issue/{target}?fields=summary,description
 

3.  Copy the form to TARGET (no template id needed — TARGET must have no existing form):

POST https://api.atlassian.com/jira/forms/cloud/\{cloudId}/issue/{source}/form/copy/{target}
 

4.  Fill answers on the new TARGET form (clear first, then set Summary/Description):

PUT https://api.atlassian.com/jira/forms/cloud/\{cloudId}/issue/{target}/form/{formId}
 

5.  Submit/lock the form so it renders in the customer view:

PUT https://api.atlassian.com/jira/forms/cloud/\{cloudId}/issue/{target}/form/{formId}/action/submit
 

6.  Read SOURCE channel context and write it to TARGET

GET https://\{site}/rest/api/3/issue/{source}/properties/sd.channel.context.key
PUT https://\{site}/rest/api/3/issue/{target}/properties/sd.channel.context.key
Once TARGET has both the copied+submitted form and the sd.channel.context.key property, it will appear in the customer's request list and open correctly (the "we're unable to show you this data" error was caused by the missing/submitted form).

Important caveats

•  SOURCE must have exactly one form, and that form must have both an id and a formTemplate.id. If SOURCE has zero or multiple forms, this simpler flow can't pick the right one — start from a clean Help Center ticket that has a single form.
•  Copying does not carry over SOURCE's answers — the form structure is copied, then you fill TARGET's own Summary/Description in step 4.
•  Submitting locks the form content — after submit, the portal-visible content can't be changed through normal form editing, so fill it correctly before step 5.
•  The API token must be an Atlassian account API token for the same user as ATLASSIAN_EMAIL.