How to control Jira filter table columns via ADF when creating Confluence Cloud pages through REST A

[Rodrigo Xavier]

Hi community,

We're building an automated report generator that creates Confluence pages via the REST API using ADF (Atlassian Document Format). One section of the page embeds a Jira filter as a table of issues ("INICIATIVAS"), and we're trying to control which columns appear — but nothing we've tried respects our configuration.

Our goal: embed a Jira filter as a table showing only these columns, in this order: Type · Key · Summary · Status · Due Date · Updated · Parent

What we've tried:

Attempt 1 — embedCard

{

"type": "embedCard",

"attrs": { "url": "https://company.atlassian.net/issues/?filter=12345", "layout": "full-width" }

}

Result: renders correctly as a table, but uses the Jira filter's own saved columns. No way to override via ADF.

Attempt 2 — Confluence Jira macro with columns param

{

"type": "extension",

"attrs": {

"extensionType": "com.atlassian.confluence.macro.core",

"extensionKey": "jira",

"parameters": {

"macroParams": {

"columns": { "value": "issuetype,key,summary,status,duedate,updated,parent" },

"jqlQuery": { "value": "filter=12345" },

"serverId": { "value": "<server-id>" }

}

}

}

}

Result: columns parameter is completely ignored — Confluence renders with its own default columns regardless.

Attempt 3 — blockCard with datasource

{

"type": "blockCard",

"attrs": {

"url": "https://company.atlassian.net/issues/?filter=12345",

"datasource": {

"id": "datasource-jira-issues",

"parameters": {

"cloudId": "<cloud-id>",

"jql": "filter=12345"

},

"views": [{

"type": "table",

"properties": {

"columns": [

{ "key": "issuetype" }, { "key": "key" }, { "key": "summary" },

{ "key": "status" }, { "key": "duedate" }, { "key": "updated" }, { "key": "parent" }

]

}

}]

}

}

}

Result: "We ran into an issue trying to fetch results" — the datasource fails to load entirely.

Questions:

1. Is there a correct ADF format to control which columns appear in a Jira filter table embedded in Confluence Cloud?
2. Does the datasource approach require the Jira filter to have specific sharing settings (e.g., shared with "Any logged-in Atlassian user")? Could that be causing the fetch error in Attempt 3?
3. Is there a newer ADF node type for this use case in Confluence Cloud that isn't well documented yet?

Any help appreciated. We're on Confluence Cloud, using the v2 REST API.

[Tomislav Tobijas]

Hi @Rodrigo Xavier ,

Interesting initiative. 👀
Regarding Jira work items, I did manage to dig out this: 

To control which columns appear and their specific order, you must use the extension type with the columns parameter. The values must be comma-separated internal field IDs (e.g., issuetype, key, summary).

Ensure the following:

• Parameter Name: Use columns within the macroParams object

• Field Keys: Use the exact internal keys. For your request, the string should be: issuetype,key,summary,status,duedate,updated,parent

• Server ID: A valid serverId is mandatory for the macro to render correctly. You can find this by manually creating a page with a Jira macro and inspecting the storage format via GET /wiki/api/v2/pages/{id}?body-format=storage.

Now, note that this is what I managed to find, but I haven't tested this myself (at least not in a while). I could try playing around with Postman to see if I can send those requests and if that call will actually end up with the desired outcome 🤔

As for the blockCard - I did see this question in the Dev community (see here) but I'm not sure if they resolved it or not. 

Generally speaking, Developer Community could be a good place to also ask this, as folks there are working more with APIs and these, let's say, custom things. 👈

If I do find time next week, I could play around with it more to see how you could actually build this. 

Cheers,
Tobi