Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Confluence Jira Two Dimensional Filter does not work for JQL queries > ~3200 characters

BMJ Ventures
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 17, 2019

Problem: Jira two dimensional filter macro will not create and/or save setting of an existing one where the parsed JQL character length exceeds ~ 3200 characters. (Confluence version: 6.15.7 - Server | Jira Version: 7.11.1#711001-sha1:ea73d62)

Goal: Display the results of issues committed, added, completed, removed in the sprint for multiple teams within a product group using native JQL and Script Runner (so please, no comments advising trimming down the JQL).

Scenario 1: Creating a new two dimensional filter

  1. Insert Jira Issue/Filter
  2. Click on Jira Chart->Two Dimensional
  3. Enter the Jira Filter > ~3200 characters (in this example DB-EHR-S20-CommittedAll) -> click Preview -> see chart results -> click Insert (chart does not save)

Scenario 1.png

Scenario 2: Revise existing two dimensional filter

  1. Edit Jira Two Dimensional Issue/Filter
  2. Observe chart rendered for existing query
  3. Enter the Jira Filter > ~3200 characters (in this example DB-EHR-S20-CommittedAll) -> click Preview -> see chart results -> click Insert
  4. Edit Jira Two Dimensional Issue/Filter again (chart retains original setting, does not save revised entry)

Scenario 2.png

Question: If the root of the problem is the limitation on the JQL length, is there a way to adjust it?

Note: The Jira Issue/Filter will save if it is created as a simple filter (not as a two dimensional filter):

Note.png

1 answer

0 votes
Nic Brough -Adaptavist-
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.
September 17, 2019

You have no choice but to get an answer about shortening the JQL - that is your only option (unless you want to rewrite every part of the Jira and Confluence code that works with JQL)

As you have scriptrunner, you might find it possible to write functions that will help you shorten it, but I could not tell you where to start, as I've not seen the filter.

Suggest an answer

Log in or Sign up to answer