Hello Atlassian community,
I have a pretty specific question:
I am using the page properties report macro to collect information from a variety of pages. One of the columns should contain a status macro and to make editing easier for my colleagues I have added all possible status options to the header of that column.
It looks like this in the page properties macro:
In the page properties report, the column containing the status macro is automatically displayed directly after the title of the page on the left-hand side. We would prefer for the column to be displayed last, just like it is in the page properties macro I set up.
I know that I have the option of describing which columns I want displayed when configuring the page properties report macro (and thereby which order I want them to appear in). However, the configuration field of course does not allow me to use macros to describe headers.
I have tried:
- Test, Test 2, Decision
- Test, Test 2, Decision Status 1 Status 2 Status 3
- Test, Test 2, Decision [Status 1] [Status 2] [Status 3]
None of which are accepted versions that the macro recognizes as this specific column and its header.
Does anyone know how I need to format the input in order for the macro to recognize the header?
Hi @Luisa Grams
Thank you for your question!
Do you mind elaborating on your use cases regarding the status placement in the header? Is it mainly to showcase the available options to set status from? In this scenario, I can suggest trying out our Handy Macros for Confluence app and its Handy Status, which has a dropdown for dynamic statuses that can be managed directly in the view mode, check for status history. They also work nicely with page properties and page properties report macros. Once the status is changed in one place, it is updated everywhere.
Additionally, with the help of our Table Filter, Charts & Spreadsheets for Confluence app, the status column can be filtered for specific status via Table Filter macro.
You can check out and try both apps for free to see if it fits your use cases well.
Cheers,
Anastasia
Dear Anastasia,
thank you for your reply, unfortunately, this does not solve my issue. We are actually using the second Add-On you suggested, and filtering the status is not our issue.
The issue is purely dependent on using the page report properties macro.
All the best
Luisa
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.