Table and Charts Macro Data Limitation

[Craig_Harley]

Hi have been using this macro for quite some time now and it is incredibly useful for my purposes. However I think i have hit a data limitation.

In one of the areas I use this I have over 1000 rows of data I am pulling in, however when looking at the filter view and charts I have created from it, it only returns the first 1000.

Is this a known limitation?

if so are there any plans to increase this?

Otherwise this is going to be problematic for my continuing usage moving forward as the datasets i use are only increasing in size

[Stiltsoft support · Accepted solution]

Hi @Craig_Harley ,

It seems that you are talking about our Table Filter, Charts & Spreadsheets for Confluence app.

If this is the case, then there are no any limitations regarding our macros. For example, you may take a 1000+ row .csv file that can be easily generated, recreate a table in Confluence using the Table from CSV macro, and aggregate/visualize it. You should see the outcome based on the whole table.

The only limitation that comes to our mind is a 1000-issues limit regarding the Legacy Jira Issues macro. The 3rd party vendors can't technically support the New Jira macro as for now, so, we use the Legacy one instead.

So, if this is the case, then in Jira you may have 1000+ tickets but in Confluence you'll see only first 1000 of them. That's why your charts are also based on the first 1000 issues.

The workaround may be to split your JQL into several parts, insert several Jira Issues macros, use the Table Transformer to merge these 1000-row table into one big table, and then perform other transformations.

If this post doesn't answer your initial question and you need to share more details about your use case for deeper investigation, please contact our support portal (that is confidential) directly.

[Staffan Redelius]

Hi @Craig_Harley 

I don't know if there is an actual limit but my experience is that large tables are difficult to handle (it has improved over the years but still gets a bit clunky loading pages)

Have you tried using databases in Confluence? I think they are better att handling larger volumes of data.

Best regards,
/Staffan