Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Confluence 'Table Filter' does not list all the unique values in a column


I am using Confluence Cloud and Jira Cloud. I am fetching data from Jira to confluence using a JQL inside a 'Table Filter'. My JQL has 1500 results.

The issue is, the filter drop down does not show ALL values from the Assignee column. Drop down only shows those unique values that are currently displayed in the confluence page, which is decided by 'Maximum Issues' count.

Suppose, if I set the 'Maximum Issues' count to 100, and those 100 records does not have an Assignee, (say John), then John will not even show in the dropdown list of values, even when the embedded JQL has John as Assignee in records 101 and beyond.

Note: Setting the field 'Maximum Issues' leads to performance issues during page load.

1 answer

3 votes
Stiltsoft support
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 17, 2023

Hi @Keshav ,

The Table Filter macro works with the data coming from the Jira Issues macro to Confluence.

So, this behavior is expected and correct: you show 10 issues and the Table Filter macro works with the 10-row table; you show 1000 issues, then the Table Filter macro works with the 1000-row table. 

May be the Jira Charts and its two-dimensional chart will be of any use to you? You'll be able to aggregate all the assignees from the Jira project.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events