Page Properties Report Column Width

[Mark Sutcliffe]

Is there a way to control column widths in a page properties report? It seems a bit random which column is text wrapped. Also the preview appears and behaves differently (and better) than the published version. See Forecast Spend column.

[Dominic Lagger · Accepted solution]

Hi @Mark Sutcliffe 

Unfortunately, you can't change or set the width of the page properties table. 

For Confluence Cloud, here is the feature request: https://jira.atlassian.com/browse/CONFCLOUD-67089

Regards, Dominic

[Steve Terelmes]

Is there a reason this issue is not open for voting or comments? This used to be my favorite Confluence Macro. 

[Dominic Lagger]

Hi @Steve Terelmes 

Perhaps you are not logged in. You have to create an atlassian account to vote and comment.

[Paul Lebel]

Why is this page marked as 'Solved' ? 

Atlassian clearly hasn't fixed the issue.

[Dominic Lagger]

Hi @Paul Lebel 

The post is marked as solved, not the issue itself.

The mark "Solved" only describes, that the answer was accepted. And in this case, the short answer is, that atlassian has an open feature request:

• CONFCLOUD-67089 
• CONFSERVER-53330 

Regards, Dominic

[Shaun Sheehan]

This is a pain point for us as well.  I upvoted the feature request. The macro on its own is great, but not when you want to separate by labels and have the same page properties report macro repeated on the page.  Then it looks choppy and unprofessional. 

[Micheal Planck]

2024 and I am having the exact same issue.

[Katerina Rudkovskaya _Stiltsoft_]

Hi guys,

If it happens so that you use our Table Filter and Charts for Confluence app, you may use its Table Transformer macro to set width of the Page Properties Report macro.
Please, check this part of our documentation (navigate to the “Changing column width” section).

[Paul Lebel]

This is a very frustrating issue for our team. What is the solution?

[Dominic Lagger]

Actually, there is no solution.

Vote for the issues:

• CONFCLOUD-67089 
• CONFSERVER-53330 

[Paul Lebel]

Voted for both issues. But yea, it seems like Atlassian isn't interested in solving this given the timeline.