-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
Severity 1 - Critical
-
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Summary
It is possible to saved a broken filter to a queue when the JQL query returns an uncaught exception. This causes the Queues view to display no queues and prevent the creation of new queues.
Steps to Reproduce
- Create a queue with a valid filter. e.g: resolution = Unresolved
- Edit the queue
- Change to resolution > Unresolved
- Save queue
Expected Results
The queue is not saved and a message is displayed indicating the the JQL filter is invalid.
Actual Results
The screen doesn't change as if the "Save" didn't work but the filter was saved in the background.
Loading the queues again shows no queues.
Notes:
The problem is actually caused by an Uncaught exception returned by JIRA when searching resolution < unresolved but JIRA Service Desk could prevent the JQL to be saved in these scenarios. JSD correctly prevents the saving a JQL that is invalid if it doesn't error.
Workaround
Find the queues on the project:
SELECT * from "AO_54307E_QUEUE" where "PROJECT_ID" in (select id from project where pkey = '<PKEY>');
Find the filter that is broken by searching JIRA using the same JQL
Update the queue in the database to a working JQL.
- relates to
-
-
- Closed
-
- mentioned in
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
- was cloned as
-
TESLA-946 Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-4322] JIRA filter for a queue that has an uncaught exception breaks Queues view
| Remote Link | Original: This issue links to "JSDS-90 (JIRA Server)" [ 231763 ] | New: This issue links to "JSMDC-90 (JIRA Server (Bulldog))" [ 231763 ] |
| Remote Link | New: This issue links to "Page (Atlassian Documentation)" [ 563777 ] |
I just did something like this inadvertently in JIRA Service Desk Application v4.5.3, Jira v8.5.3. Is it not fixed?
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2304744 ] | New: JAC Bug Workflow v3 [ 3126114 ] |
| Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
| Symptom Severity | Original: Critical [ 14430 ] | New: Severity 1 - Critical [ 15830 ] |
| Workflow | Original: JSD Bug Workflow v5 [ 2058686 ] | New: JSD Bug Workflow v5 - TEMP [ 2304744 ] |
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2056720 ] | New: JSD Bug Workflow v5 [ 2058686 ] |
| Workflow | Original: JSD Bug Workflow v5 [ 1956478 ] | New: JSD Bug Workflow v5 - TEMP [ 2056720 ] |
| Workflow | Original: JSD Bug Workflow v4 [ 1615952 ] | New: JSD Bug Workflow v5 [ 1956478 ] |
Following up on my comment....
The workaround did work and I am glad to have my queues back.
I am surprised that Jira SD 4.5.3 let me save a queue with a JQL filter that is invalid.