Community
Q&A
Confluence
Questions
Can you confirm whether the GitLab macro data is intentionally removed from body-format=view?

Can you confirm whether the GitLab macro data is intentionally removed from body-format=view?

We are using the Confluence v2 API to retrieve page content.

Previously, when calling: /wiki/api/v2/pages/{id}?body-format=view the response included GitLab macro information, which allowed us to call the GitLab API and fetch the related file details.

Recently, this endpoint only returns a placeholder like: <div>GitLab File</div> and the GitLab metadata is missing.

1 answer

0 votes

Hello and welcome to Atlassian community @jobin

Which GitLab integration is this Atlassian's native GitLab Smart Link, or a Marketplace GitLab macro/app?

And btw. Could you try retrieving the same page/version with:

?body-format=atlas_doc_format

and, for comparison:

?body-format=storage

Best,

Arek 🤠

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

We are using the GitLab Marketplace app/macro. The structure of ?body-format=atlas_doc_format is different from body-format=view. With body-format=view, the other macros work fine — only the GitLab-related items are missing

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

When behavior started to change?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

I think last Wednesday we had a production release, and at that time we noticed this issue.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Arkadiusz Wroblewski likes this

Given your confirmation that this is a Marketplace application, I recommend raising this with the application vendor. Specifically, inquire whether there have been recent changes to the REST or static representation of their GitLab macro.

If the vendor confirms that nothing changed on their side and this is caused by a Confluence rendering/API change, then I think it would make sense for you to involve Atlassian Support.

Other way we will go too deep into guessing.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Reply

Suggest an answer

Log in or Sign up to answer

Was this helpful?

Thanks!

DEPLOYMENT TYPE

CLOUD

PRODUCT PLAN

STANDARD

TAGS