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

"epic link" queries for specific epics have stopped working

Jesse Pelton March 5, 2021 edited

For many years we have made extensive use of JQL to search for specific epics:

"epic link" in ("EPIC-1")

especially in Confluence. Articles where such queries already exist are displaying the tickets as expected, but if we attempt to update the epic(s) in a query using the Confluence "Insert JIRA Issue/Filter" dialog, or to run such a query via Jira's advanced search, an error is reported. Confluence doesn't indicate why, but the advanced search says "The option 'EPIC-1' for field 'epic link' does not exist." The epic exists and I can view it.

image.png

The non-existent epic message is correct in this case. If the epic did exist, that message does not appear, suggesting that the epic was found despite the "option does not exist" condition.

Our Jira administrator says that Atlassian must have broken this formerly working query and that there's nothing he can do about it. He suggested searching by epic name, but that generates the same error.

The following also fail:

"epic link" = "EPIC-1"
"epic link" != "EPIC-1"

The following succeed, though they're of no use to me:

"epic link" is empty
"epic link" is not empty

Do epic link queries work for anyone else?

Is it possible that there's something about our Jira Cloud configuration that's causing this problem?

1 answer

1 accepted

0 votes
Answer accepted
Bill Sheboy
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.
March 5, 2021

Hi @Jesse Pelton 

That syntax for JQL is working for me: "epic link" in ("EPIC-1")

That second error message seems to indicate another field named "epic link", perhaps a custom field with multiple options: "The option 'EPIC-1 for field 'epic link' does not exist."

Have you asked your site admin if there is a custom field that was defined with that same name as the built-in field?

If there is not, I suggest asking your site admin to submit a support ticket to Atlassian here:

https://support.atlassian.com/contact/#/

Best regards,

Bill

Jesse Pelton March 5, 2021

That's very helpful. The advanced query bar suggest both "epic link" and "epic link [dropdown]" if I type "epic li. I'll bet that second suggestion, whatever it is, is the problem. I'll ask the administrator.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Upcoming Jira Events