-
Suggestion
-
Resolution: Low Engagement
-
1
-
When using the new experimental endpoint Search for users within an organization that was released for the Organizations REST API and expanding the PRODUCT_LAST_ACCESS field, the returned information contains only the site cloudSiteId information.
Example POST:
{
"emailUsernames": {
"contains": "john.doe"
},
"emailDomains": {
"eq": [
"yourdomain.com"
]
},
"expand": ["NAME", "EMAIL", "PRODUCT_LAST_ACCESS"],
"limit": 20
}
Response:
"productLastAccess": [ { "productKey": "confluence.ondemand", "lastActiveTimestamp": "2023-11-09T14:44:29.857268146Z", "cloudSiteId": "<YOUR_SITE_ID>" }, ...
Suggestion:
It would be interesting to have the Site URL included in the response.
While the Site URL is not available, it's possible to use the endpoint Get list of workspaces to return a list of all the sites registered under the Atlassian Organization.
The cloudSiteId returned by PRODUCT_LAST_ACCESS can then be matched with the ID stored in the "id" attribute:
{
"data": [
{
"id": "ari:cloud:jira-admin::site/<YOUR_SITE_ID>",
"type": "workspaces",
...
The site URL will then be found in "hostUrl":
"hostUrl": "https://<YOUR_SITE_URL>",
[ID-8574] Include the Site URL when calling the endpoint "Search for users within an organization"
It is npot possible to do a "get a workspace" API call for 1 single cloud site id. You can only get a list - so get a list, build a dictionary of all the SiteIDs by extracting them via regex from the data.id attribute. Too much work if you only want to check where a single user accessed a certain site.
Would be great to have a filter there in the "Get list of workspaces" and to have the IDENTICAL site_id in both the workspace list and in the "search users in the organization" result.
Hi everyone,
Thank you for bringing this Suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity for an extended period of time, this Suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. If you’re interested in what’s planned or coming soon, check out our Cloud Roadmap.
In addition, if you feel like this Suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team, we appreciate your engagement and partnership in helping improve our products - Atlassian Cloud Product Management