Using macro-body for parameters to reporting-filters

Thanks a lot, that seems to work as expected, however my case is of course slightly more advanced than what I asked for :-)

I'm using the report in question to generate a set of list-options for a list-data scaffold surrounding the report. To get the list-option macro to render its body I've found that the data has to be injected instead of using report-info, meaning that with your suggestion there is a double injection happening.

When I applied your suggestion the dynamic text filter works like I wanted in a test case, but with my actual code i'm now getting "Error formatting macro: report-on: java.lang.NoClassDefFoundError: com/atlassian/confluence/mail/address/ConfluenceMailAddress" in place of the expected list. Changing the second injection to a report-info macro makes the list work, but every item is the unrendered report-info macro instead of the expected results.

My code looks like this when giving the abovementioned error:

{list-data:Oppgave|blank=true}
{report-on:injected=true}
{report-block:injected=true}
{expanding-reporter:data:Oppgaver|as=oppgave}
{local-reporter:page:descendents|source=Milepæler}
{text-filter:page:labels|include=.*arbeidspakke.*}
{local-reporter}
{expanding-reporter}
{text-filter:oppgave > data:Personer|include=.*%page:title%.*}
{report-body}{list-option}%oppgave > data:Oppgave%{list-option}{report-body}
{report-empty}Ingen oppgaver.{report-empty}
{report-block}
{report-on}
{list-data}


Any tips on how I can force rendering of the report-info macro so that each list-option contains the report item result?

Actually I'm using Confluence 2.9 with Reporting 3.1.0 (at least I think I managed to downgrade back to 3.1.0 as some compatibility-issues I had after upgrading has disappeared, but it still reports 3.2.0 in the plugin-console).

The downgrade probably wasn't completely successful so maybe that is causing the issue. Should the report above be working as expected with Reporting 3.1.0 on Confluence 2.9? In that case I'll give downgrading another shot.

I'd love to upgrade but I'll have to get this working on the current system as it is needed in just a few days. An upgrade for Confluence is coming, but it'll be a while before it gets done. Big organization and all that...

Thanks a lot for your help!

I couldn't figure out why your {report-on} trick stopped working, but I found another comment you made somewhere else about using a custom user macro instead, and since all I needed to filter on was the page title that worked for me. It'll do until we get Confluence 3 up and running :-)

Thank you very much for all your help. For great customer service you guys are simply unbeatable :-)

Hi again!
We've finally upgraded to Confluence 3.0.2, and I've upgraded to Reporting 3.2.0 as well, but your neat trick of enclosing a report inside an {report-on:injected=true} macro to get injections from the current page, which is something I've started using several places, now suddenly gives the following error:
Error formatting macro: report-on: java.lang.StackOverflowError

I've tested the report-on seperatly and it works as expected, but it gives the error when enclosing another report like this:

{text-data:Label}{text-data}
{report-on:injected=true}
{report-table}
{space-reporter:space=@global}
{text-filter:space:labels|include=.*%data:Label%.*}
{space-reporter}

{report-column:title=Prosjekt} {report-info:space:name|link=true} {report-column}

{report-empty}Empty.{report-empty}
{report-table}
{report-on}


Any ideas?