Populate a page properties report with a specific field in JIRA

[Craig_Harley]

I have just started using the Table Filter and Charts macro

I have a page properties report that I am pulling through into a table filter

one of the fields pulls through a JIRA epic as a reference, which is a JIRA Legacy macro added to the original page properties pages

There are 2 further fields that I would like to populate for each row with specific fields located in each JIRA epic, is there a way of doing this in the Table Filter and Charts Macro?

[Stiltsoft support]

Hi @Craig_Harley ,

Not sure what you exactly mean: our macros are compatible with the Page Properties Report and Jira Issues macros.

You can wrap these macros into our macros: their outputs will be recognized by our macros like dynamic tables. So, you may filter, aggregate, and visualize the outputs of your Page Properties Report and Jira Issues macros.

Our macros don't go to Jira or somewhere else to grab any data. If you see the required fields coming from the Jira Issues macro or Page Properties Report macro, then our macros see this data as well and work with it.

[Craig_Harley]

OK, let me make this simpler

I have a catalogue of information which is my page properties report

Every unique row has a unique service epic from JIRA assigned to it (the JIRA issues macro is added to each page properties, it is configured to only have a single unique entry, so one to one mapping between page properties report row and JIRA EPIC)

Each one of these Epics has a number of fields, such as "Assignee" and "Review by Date"

rather than include the top level epic as in the diagram above, I want to just populate the entry in my confluence page properties report with the contents of "Assignee" or "Review by Date" from my JIRA epic, is this possible?

[Stiltsoft support]

As I've mentioned before, the macros provided by the Table Filter and Charts for Confluence app don't grab data anywhere and work with the data coming from the source table.

So, as I understand, the question is to grab these additional fields through the Jira Issues macro.

To choose the additional fields to show, you need to select the "Table" form of the Jira Issues macro display (then you will be able to choose the required additional fields). 

The "Single issue" display shows a key, summary and status, you can't select additional fields here.

You may use the following workaround: leave the "Single issue" strings in your PP and collect them through PPR on the master page.

Then on the same master page show the Jira Issues macro in a tabular form: epics and other required fields.

Then these two tables (PPR and Jira Issues) can be merged by the epic names (as they are present in both tables).

The PPR firstly may be splitted by the "Service Epic" column to leave only epic name (BISCAT-131, for example) to match the Jira Issues table.