Katerina Kovriga {Stiltsoft} Expert

Hi @Yana Yusupov , It's a strange behavior - I've checked the case on our test Confluence instance and everything works fine for me (Confluence version 7.12.5, app version 7.9.5 - the latest one). Please check the version of the app and update it to the latest one. If this doesn't help, please raise a support request.…

Maybe try to simplify your Page Properties Report - collect Page Properties by labels, not the id, show all the columns, etc. For testing purposes, I mean. Maybe you've caught a bug or smth - do other Page Properties Reports work as expected for your Confluence instance?

Hi @Christian Holm , Have you tried to change your sequence of macros and make the Page Properties macro collect just pure tables: table <- Page Properties <-Panel macro? It looks like your table headers are messed up.

Hi @Steve Wallis , Please can you give more details about the case? You have a page tree with a parent page where you keep the Page Properties Report macro that collects data from all the child pages? And there are several similar Page Properties Reports which you want to collect into one big table? Our app (Table Filter…

I can suggest trying our app - Table Filter and Charts for Confluence (it is a paid add-on). Maybe you've already been using it for your Confluence - it works with the Page Properties Report macro perfectly well. You'll be able to filter your report by statuses (like in Excel) and sort them with the help of the Table…

Hi @Rufus John , I guess you can't build a chart using an attachment and a standard Chart macro. If you put an Excel macro in the Chart macro body, the table won't be recognized. When I copy the same table from the excel file inside the macro body manually, only then I can see my graph. What concerns the Chart macro and…

Hi @Chris Streeter , We can suggest our app - Table Filter and Charts for Confluence - to create Jira dashboards in Confluence based on the standard Jira Issues macro. Our Table Filter, Pivot Table and Chart from Table macros work with dynamic Confluence macros perfectly well and allow you to visualize your data. Here are…

Hi @Kelly Pelkie If you look back at the screenshots, you'll see the difference: your numbers are included into your statuses. But for his example Diego put also plain text before the Status macro. Not "[1-High]", but "1[1-High]"

The Page Properties Report macro collects only one-row tables. As I have mentioned before, Table Excerpt/Table Excerpt Include macros collect multiple-row tables, but they come with the Table Filter and Charts for Confluence app - it's a paid add-on.

I assume your JQL Filter comes from something similar to this and this threads, so you are able to put plain text and variables inside its body. Or maybe the macro comes from another 3rd party app? We've got the idea of your case but can't come up with any solution.

Yes, you are right - there will be an additional column. To hide it, use the Table Filter macro: * Wrap your Table Excerpt Include into the Table Filter macro * Go to the Settings -> Filters tab and check the Hide columns option * Go to the Filtration tab -> Set filters' default values and choose the last unnamed column to…

Hi @Szymon Kołodziej , I suggest browsing the Marketplace - there should be some apps (maybe even free ones) that allow you to import CSV files into Confluence. Our app (that is Table Filter and Charts for Confluence) focuses mainly on table filtration, data aggregation and visualization, calculations in tables, etc. But…

Hi @Emily Berg , I'm afraid, this case is not possible to implement. The result of the Table Transformer macro will be always a table of some kind, it won't serve as an input (variable) for the JQL filter.

Hi @Дмитрий Пересекин , We can suggest trying our app - Table Filter and Charts for Confluence app and its Table Excerpt/Table Excerpt Include macros. The macros work similar to the Page Properties and Page Properties Report macros but allow you to collect multiple-row tables and show the following page meta data: * page *…

Maybe you'll come up with a structure where your parent page will collect child tables. Like switch your templates or smth. Then it will be much easier to handle everything. 

Hi @lalitha meenakshi , You may try to use the standard Jira Issues/Filter macro - as far as I know, it allows you to delete whatever fields you want, there are no any default rules. I assume, that currently you use this macro. As a workaround, I may suggest using the Table Filter and Charts for Confluence app - it's our…

Don't get what you mean by the 4 tables collected by the Table Excerpt Include macro - here is a similar use case where we collect multiple-row tables in Confluence Cloud. Please check the screenshots - you'll be able to get one combined table. Just don't put an employee name somewhere near the table - create tables with 3…

Maybe I didn't get your case, so let me rephrase it once more: * Every employee has several training programs * He/she creates a new page for every program with a standard one-row table at the top of the page: Employee / Training name / Status * Each table is wrapped into the Page Properties macro * Your manager has…

Hi @Nimo , The option to search for any Excerpts on the parent page is not included into the Table Excerpt Include macro as for now. As usual, the parent page is a place for the combined report, generated using the tables located lower on the Space page tree. And your case is somewhat the opposite one - your child page…

Hi @Naveen Basar , If your employees create and update one-row tables on their local pages, you may collect the combined table using the standard Page Properties/Page Properties Report macros (these macros are native Confluence macros). If you need to collect multiple-row tables across your Confluence instance, we can…

Hi @Donna Macauley , We can suggest using our app - Table Filter and Charts for Confluence. Wrap your Jira Issues macro into the Table Transformer macro and set the required column width.

Hi @Nimo , The problem is in the double headers of your tables, it's a tricky case for Confluence macros to process them correctly. If you have the Table Filter and Charts for Confluence app installed for your instance (it's our add-on), we can suggest using its Table Excerpt/Table Excerpt Include macros. The published…

It is because the Merge preset is chosen by default for the Table Transformer macro (it comes first in line), so the first row (similar for the two tables) was misinterpreted as a header row. Thank you for reaching out, I'm glad that everything works now.

Hi @Pei-ju Hsu , You may implement the following steps: Here we have your tables that are collected with the help of the Table Excerpt Include macro: The last step is to merge your transposed tables via the Table Transformer macro. Here we choose the standard Merge preset: And here check the Transpose source tables option:…

Let's wait for the answers from other vendors, but I really can't come up with a better solution. If both of your tables come from the Jira Issues macro, then you may merge them automatically by a unique field (see an example here). But if you need to add comments by hand in Confluence, then you really have to follow my…

As I have mentioned before, you should have something common to merge your tables - for your case it's the "Key" field. For the first table it's generated automatically by the Jira Issues macro. For the second table it's a manually created column. You type in the key of the issue that you want to comment on and leave some…

We should be able to match the two tables by the unique "Key" column

You don't need to use any custom SQL - choose the Look Up preset and combine you tables by the "Key" column. And don't forget to add the "Key" column to your second manually created table! 

In edit mode you will be able to edit you manually created table (add rows/columns, fulfill Why.../How... cells) and every time you publish the page you'll see your merged table.

Yes, it doesn't matter which manually created table you want to add (it can have any columns you want). The Jira Issues table will be matched with the manually created table by the unique Issue Key field.