Issue Summary

This is reproducible on Data Center: (no)

Jira GET Issue rest endpoint provides wrong "self" when we use api.atlassian.com/ex/jira. This happens with both v2 and v3.

The self link in the response body is missing '/ex/jira/cloud_id'.

Steps to Reproduce

1. make a rest call using api.atlassian.com

   curl --location 'https://api.atlassian.com/ex/jira/{{cloud_id}}/rest/api/3/issue/{{issue_id}}' \
   --user $EMAIL:$TOKEN
   

1. Check the self link in the response

   curl --location 'https://api.atlassian.com/ex/jira/{{cloud_id}}/rest/api/3/issue/{{issue_id}}' \
   2>/dev/null \
   --user $EMAIL:$TOKEN | jq '.self'
   

Expected Results

The self link in the response body is properly formatted, like this,

"self": "https://api.atlassian.com/ex/jira/{{cloud_id}}/rest/api/3/issue/{{issue_id}}",

Actual Results

The self link in the response body is missing '/ex/jira/cloud_id'. like this -

"self": "https://api.atlassian.com/rest/api/3/issue/{{issue_id}}",

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available