Details
-
Bug
-
Resolution: Fixed
-
Medium
-
1
-
Severity 3 - Minor
-
2
-
Description
Issue Summary
Using REST API v1, we are able to fetch certain "links" that correspond to a piece of content. Examples being: `editui`, `webui`, `tinyui`, etc.
An example being:
"_links":{ "editui":"/pages/resumedraft.action?draftId=734397355", "webui":"/spaces/zmarkdown/pages/734397355/markdownPageUrlRelReplacementVars", "context":"/wiki", "self":"https://bobswift-prod.atlassian.net/wiki/rest/api/content/734397355", "tinyui":"/x/qwPGKw", "collection":"/rest/api/content", "base":"https://xxxxxxx.atlassian.net/wiki" }
These links are not available from any of the V2 endpoints, but are necessary for parity
Steps to Reproduce
- Fetch a page using V1 endpoint: /rest/api/content/{pageid}
- Observe `_links` field
- Try to this information using /api/v2/pages/{pageid}
- Notice these results are absent
Expected Results
The links fields are accessible from the V2 endpoints.
Actual Results
The links fields are absent from the V2 endpoints.
Workaround
No workaround besides using deprecated V1 endpoints.