You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
This question is in reference to Atlassian Documentation: Page Properties Macro
The document says: "In the macro body create a two column table and remove the header row." in the paragraph "Adding the Page Properties macro to a page" and "If your table has a header row, this row will be ignored by the Page Properties Report macro. You should remove the header row." in the footnote but I found no need to remove the header. In addition, we can leave the 3rd and more columns which might be useful for legends, descriptions, comments, remarks of the row. I think the Page Properties Report Macro gracefully ignore those columns now.PageProperties_vertical-edit.PNG
And I found a horizontal table with heading row could work as my expectation;
PageProperies_horizontal-edit.PNG
The result of the Page Properties Report macro was seen;
PagePropertiesReport.PNG
This is great! But is this an unexpected behaviour of the macros or lazy updating documentation?
Hi Mamoru,
Thanks for pointing out the errors on that page. We promise it's not laziness; we're just super busy!
Hi Giles, I know you are one of the busiest persons in the world.:-) I hope this feature of the Page Properties Report macro won't disappear in future. Thank you, TASH
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
are there plans to make the report scrollable like the rest of the tables in the latest version?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vince, I agree with your idea but guess you better raise another proposal desribing your idea in detail to Atlassian Support with a bloody-prefixed title like "FATAL! ", "CRITICAL!! " to attract the busiest engineers' attentions;-) Thank you, TASH
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.