For our users the usual case is, to gather information across different spaces, so an option to show the space is essential for the users of page properties report macro.

We have a report that search for pages created across different spaces using a template. 

I agree it make sense to have the option 'Show space', to see where it's coming from, so we don't need open each page to find the space.

Some of the Atlassian macros do include this option. It seems inconsistent that this one doesn't have it as an option. It sure would be useful.

I too could use this right now. Please reconsider.

Using '$space.key' (and other variants from cql) as a 'column to show' would be preferable.

Regards,

Martin

I could use this as well... Too pity...

Too bad Atlassian won't implement this. I agree that the LOE is probably minimal and it would be immensely useful. I had another great idea of how I could mine page data using this and provide useful reports to people, but without the space name, the resultant table isn't too useful.

(And I agree it should be optional to show the space name, like it is in some other macros.)

I'm implementing an 'enterprise' view of spaces in Confluence. I'm gathering all pages of a certain type into one reference page. As a result there are pages referenced from different spaces and it would be desired to know and to sort on from what space it originated. Is there a re-consideration of completing this request, or has it perhaps been resolved in another fashion?

Is there a way that i could modify the summary macro myself in order to show this behaviour?

It would be really helpful for me in order to show summary pages about project specific data without having to manually copying the project name into every page property macro.

we strongly rely on templates (conventions) and therefore the pages containing the respective data all have the same name in the different project spaces.

Certainly unfortunate, as it seems the LOE would be minimal, but I appreciate setting expectations. Thanks Bill.

Thank you for raising this issue. While we can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Thanks again for your idea.