Issue Summary

The resource ID pattern in Organizations REST API for Policies and Workspaces is not the same for the Jira application

Policy: https://developer.atlassian.com/cloud/admin/organization/rest/api-group-policies/#api-v1-orgs-orgid-policies-get\

Workspace: https://developer.atlassian.com/cloud/admin/organization/rest/api-group-workspaces/#api-v2-orgs-orgid-workspaces-post\

Steps to Reproduce

Run the Policy and Workspace APIs above and you can see below output:

Policy API

{"id":"ari:cloud:jira::site/537f930a-a47c-4025-a9f0-f0d991be4eea","applicationStatus":"applied","type":"","createdAt":"2024-04-11T12:36:12.932Z","updatedAt":"2024-04-11T12:36:13.452Z"}

Workspace API

{"id":"ari:cloud:jira-admin::site/537f930a-a47c-4025-a9f0-f0d991be4eea","type":"workspaces","links":{"self":"https://api.atlassian.com/admin/v1/workspaces/ari%3Acloud%3Ajira-admin%3A%3Asite%2F537f930a-a47c-4025-a9f0-f0d991be4eea"

Here the Workspace API has resource IDs like ari:cloud:jira-admin whereas in a Policy API, we see *ari:cloud:jira* resource.

The other patterns which we get are jira-servicedesk and jira-software

Expected Results

The Policy API must have the same resource ID as the Workspace API. This will help us cross-check whether the resources are available in both Policies and Workspaces.

This is the issue only for Jira application as we have multiple patterns as below: jira-servicedesk, jira-software and jira-admin

Actual Results

The resource in Policy API is not having complete information as in Workspace.

Workaround

No workaround at the moment.