The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions
Release Notes
Community
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

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

Rodrigo Xavier
Rodrigo Xavier
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
July 10, 2026

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": {
"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.

Watch
Like Anwesha Pan likes this
414 views

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

2 votes
Answer accepted
Tomislav Tobijas
Tomislav Tobijas
Community Champion
July 11, 2026

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

View More Comments
Rodrigo Xavier
Rodrigo Xavier
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
July 13, 2026

Hi @Tomislav Tobijas ,

Hope you're well!

Thank you so much for taking the time to reply — your tip about inspecting the page via GET /wiki/api/v2/pages/{id}?body-format=atlas_doc_format was exactly what we needed.

It worked! The problem was the id field inside the datasource object. We were using the string "datasource-jira-issues" as a placeholder, but Atlassian requires the actual UUID of the Jira Issues Datasource provider.

The fix:

// ❌ Wrong
"datasource": { "id": "datasource-jira-issues", ... }

// ✅ Correct
"datasource": {
  "id": "d8b75300-...",
  "parameters": {
    "jql": "filter=12345",
    "cloudId": "your-cloud-id"
  },
  "views": [{
    "type": "table",
    "properties": {
      "columns": [
        {"key": "issuetype"}, {"key": "key"}, {"key": "summary"},
        {"key": "status"}, {"key": "duedate"}, {"key": "updated"}, {"key": "parent"}
      ]
    }
  }]
}

We discovered the correct UUID by fetching the ADF of a manually-configured page — d8b75300-... is the fixed provider identifier for the Jira Issues Datasource in Atlassian Cloud.

(Attaching a diagram of how our AI agent generates Confluence pages — in case it helps for context.)

diagram-ai-agent-confluence.png

Like • Tomislav Tobijas likes this
Tomislav Tobijas
Tomislav Tobijas
Community Champion
July 13, 2026

Awesome explanation and reply @Rodrigo Xavier ! Thanks for this 🙌 (glad you got it resolved as well :) )

Like • Rodrigo Xavier likes this
Reply
Confluence
Confluence
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Release Notes
    Copyright © 2026 Atlassian
    Privacy Policy Notice at Collection Terms Security