Status and Label Fields Not Populating From Linked Page in Database

[Casey Conger]

I am trying to create a confluence database where one column has a link to another confluence page. I am then trying to add another column that displays that pages status and labels using the status and label fields in the database. However, once I add the status/label column, it looks like it's loading (see some dark oval in the entries where I expect the status/label to be filled in), but then nothing ends up populating in the database entry.

I can see on the linked pages that they do have labels and a status - the changes are published. The pages are all in the same space, and I never get any sort of message letting me know something isn't working.

Just curious what I can do to try and debug the situation and figure out what the issue is - I'm not given any error messages or anything to help identify what could be wrong. (Further, Rovo or whatever the AI tool is called, gave me outright wrong information saying that label fields do not pull from the linked page, when it seems like that's exactly what they are meant to do.)

[Mia Tamm _Simpleasyty_]

Hi @Casey Conger,

You’re not missing anything — at the moment, Confluence databases don’t automatically pull status or labels from linked pages. The link field connects entries, but metadata like page status or labels isn’t dynamically synced from the linked page into your database.

If you’re seeing that dark loading oval, it’s just the database trying to resolve the field — but since those values aren’t supported for cross-page references yet, it ends up empty.

If you mainly need to display and organize this kind of information inside Confluence, you might want to try Simple Table for Confluence — I work on that app. It’s a table-based approach that gives you more control over how data and page details are displayed, without relying on database links.

Hope that helps clarify things!

— Mia Tamm

[Casey Conger]

Hi @Mia Tamm _Simpleasyty_ ,

Thanks for the response! I feel like I'm crazy or I need to work on my reading comprehension skills, but does this description on label type fields for databases not sound like that's exactly what it should be doing?

The label field type displays all labels of a page or live doc referenced in the database with the page and live doc link field.

Found on this page.

So, based off of this description, I would expect that if I:

1. created a link field in the database and in some entry linked to a different confluence page
2. created a status or label field in the same database and pointed it to the link field I just created
3. That it should then display the status or labels of the page linked to in the link field column

Are you saying that that is not how this is expected to work?

Is it just that they will scrape the options for status/labels so that when you click on an entry it will have the all of those options available to select? If so, that seems very confusingly worded.

[Mia Tamm _Simpleasyty_]

Hi @Casey Conger ,

That’s a great observation — and you’re absolutely right that the description can sound a bit confusing in this case.

If you’re mainly trying to display page status or labels across multiple pages, there’s actually a simpler and more reliable model you can already use today:

• Use the Page Properties macro on each Confluence page to define the fields you want (for example Status, Labels, Owner, etc.) in a table.
• If you’re using AppFox Approvals (you can ask to @Yulia Lenina _AppFox_ for this app), you can even include the approval macro inside that same table so that its value (approved/pending/rejected) appears directly as a property — and then pull everything together with a Page Properties Report on your summary page.

This approach keeps the data always in sync because it’s reading live from each page, not from a static database entry.

That said, we’re currently working on something even more flexible with Simple Table for Confluence — it’s a table-based app that soon will make it possible to centralize and auto-update page information (status, labels, approvals, etc.) while giving you the power to filter, group, and calculate directly inside Confluence.

Unlike the new databases, Simple Table doesn’t just display data — it helps you work with it in meaningful ways.

Hope that gives you a practical workaround until this is ready for everyone!

— Mia Tamm

[Casey Conger]

Thanks so much! That helps clear things up, I will look into both Simple Table and AppFox.

[Mia Tamm _Simpleasyty_]

That’s great to hear, @Casey Conger! 😊

Just a quick note — the integration between AppFox Approvals and Simple Table for Confluence is actually coming later this month.

If you’d like, we can add you to the early access list so you can try it before it’s publicly released. You just need to open a short ticket on our help center .

— Mia Tamm