I have a public sample page that demonstrates the behavior described in the title. Inline comments are not returned by REST v2, but by REST v1.
Let’s get the inline comments of this page:
Using REST API v1 first - because this works:
https://inera.atlassian.net/wiki/rest/api/content/3502244374/child/comment
Returns (slightly abbreviated):
{
"results": [
{
"id": "3505160502",
"type": "comment",
"status": "current",
"title": "Re: 2024-01-12 Aktuellt om Säker digital kommunikation",
"macroRenderedOutput": {
},
"extensions": {
"location": "inline",
"_expandable": {
"inlineProperties": "",
"resolution": ""
}
}
}
],
"start": 0,
"limit": 25,
"size": 1
}
Now REST API v2:
https://inera.atlassian.net/wiki/api/v2/pages/3502244374/inline-comments
Returns:
{"errors":[{"status":404,"code":"NOT_FOUND","title":"Not Found","detail":null}]}
Also, expanding doesn’t change the result.
This:
https://inera.atlassian.net/wiki/api/v2/pages/3502244374/inline-comments?resolution-status=resolved,open,dangling,reopened&status=current,archived,trashed,deleted,historical,draft
Returns:
{"errors":[{"status":404,"code":"NOT_FOUND","title":"Not Found","detail":null}]}
This page has indeed one resolved inline comment which is the one returned by the v1 REST endpoint:
No footer comments are present on this page.
Note that when calling the REST API v2 endpoint for a page without inline comments, the server response changes from 404 to empty result:
Try this page (no inline comments at time of this writing):
https://inera.atlassian.net/wiki/api/v2/pages/3502113389/inline-comments
This returns an empty result set (as one would expect):
{"results":[],"_links":{"base":"https://inera.atlassian.net/wiki"}}
Overall, this looks like a bug in the v2 inline comments endpoint.
