[JSWSERVER-21280] "Epic Link" dropdown suggestions are not working properly due to changes introduced at JSWSERVER-21026

Type: Bug
Resolution: Fixed
Priority: Highest (View bug fix roadmap)
Fix Version/s: 9.2.0, 8.20.12, 8.13.25, 9.1.1
Affects Version/s: 8.22.0, 8.20.7, 8.13.20, 8.20.8, 8.20.10
Component/s: Epics, Issue - Fields
Labels:

Introduced in Version:
8.13
Support reference count:
54
Symptom Severity:
Severity 2 - Major
UIS:
752
Bug Fix Policy:
View Atlassian Server bug fix policy

Issue Summary

This is reproducible on Data Center: (yes)

Implementation of ~~JSWSERVER-21026~~ introduces some changes that were targeted to significantly improve performance for retrieving epics for epic picker in large environments with a lot of Epic issues. However, under some conditions, it is now no longer possible to get the correct and expected Epic Name suggestion list while typing the text.

Steps to Reproduce

So far, we were able to identify the following failure use-cases.

Create some Epic issues with "EpicA", "EpicB", "EpicC" etc.
As an example of Epic Link suggestions you could try creating any non-Epic issue:
- Scroll down to Epic Link field and click on it to set focus. All issues will be returned as part of the suggestion:
Start typing the name of the desired issue. While typing "epic" word there will be no suggestion returned until you type the full name of the issue (i.e. "epicA"):
2_typing_epic_no_suggestions.mov

Another example is the issue with hyphen character in the name:

Create some Epic issues with the hyphen character in the name. For example, "ux-pretty-panel", "ux-pretty-button" and "ux-prima".
Same as for the previous case, create a new issue and start typing the name of the desired issue. While typing character before hyphen suggestions will not work until the whole word will be typed. Next, after hyphen you will need again to type the whole next word to make suggestions work again:
3_typing_epic_no_suggestions_hypen.mov

Before ~~JSWSERVER-21026~~ while requesting data for Epic Name suggestion, Jira simply queried all issuetype = "Epic"

2022-03-14 15:51:43,245+0000 http-nio-8080-exec-6 DEBUG jira_admin 951x15667x1 11k4v0a 192.168.208.1,192.168.208.5 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL query: {issuetype = "Epic"} order by key ASC
2022-03-14 15:51:43,247+0000 http-nio-8080-exec-6 DEBUG jira_admin 951x15667x1 11k4v0a 192.168.208.1,192.168.208.5 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL lucene query: type:10000

After 8.22 where ~~JSWSERVER-21026~~ was implemented the query logic became more sophisticated (see JSWSERVER-21026 JQL-based epic picker for detailed description):

2022-03-14 17:00:43,273+0000 http-nio-8080-exec-5 DEBUG jira_admin 1020x1050x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL query: {project in ("SP")} AND ( {cf[10104] ~ "e"} OR {key in ("e")} ) AND {issuetype = "Epic"} order by key DESC
2022-03-14 17:00:43,275+0000 http-nio-8080-exec-5 DEBUG jira_admin 1020x1050x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL lucene query: +projid:10000 +((+customfield_10104:e #nonemptyfieldids:customfield_10104 #visiblefieldids:customfield_10104) ()) +type:10000
2022-03-14 17:00:43,277+0000 http-nio-8080-exec-5 DEBUG jira_admin 1020x1050x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL sorts: [<custom:"projkey": com.atlassian.jira.issue.search.parameters.lucene.sort.StringSortComparatorSource@b6e3f2c>!, <custom:"keynumpart_range": com.atlassian.jira.issue.search.parameters.lucene.sort.StringSortComparatorSource@4e6256e3>!]
2022-03-14 17:00:43,282+0000 http-nio-8080-exec-5 DEBUG jira_admin 1020x1050x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL query: {project not in ("SP")} AND ( {cf[10104] ~ "e"} OR {key in ("e")} ) AND {issuetype = "Epic"} order by key DESC
2022-03-14 17:00:43,284+0000 http-nio-8080-exec-5 DEBUG jira_admin 1020x1050x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL lucene query: +(#nonemptyfieldids:projid -projid:(10000) #visiblefieldids:projid) +((+customfield_10104:e #nonemptyfieldids:customfield_10104 #visiblefieldids:customfield_10104) ()) +type:10000
2022-03-14 17:00:43,287+0000 http-nio-8080-exec-5 DEBUG jira_admin 1020x1050x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL sorts: [<custom:"projkey": com.atlassian.jira.issue.search.parameters.lucene.sort.StringSortComparatorSource@79608fac>!, <custom:"keynumpart_range": com.atlassian.jira.issue.search.parameters.lucene.sort.StringSortComparatorSource@25691b2d>!]
2022-03-14 17:00:45,079+0000 http-nio-8080-exec-4 DEBUG jira_admin 1020x1051x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL query: {project in ("SP")} AND ( {cf[10104] ~ "ep"} OR {key in ("ep")} ) AND {issuetype = "Epic"} order by key DESC
2022-03-14 17:00:45,080+0000 http-nio-8080-exec-4 DEBUG jira_admin 1020x1051x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL lucene query: +projid:10000 +((+customfield_10104:ep #nonemptyfieldids:customfield_10104 #visiblefieldids:customfield_10104) ()) +type:10000
2022-03-14 17:00:45,082+0000 http-nio-8080-exec-4 DEBUG jira_admin 1020x1051x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL sorts: [<custom:"projkey": com.atlassian.jira.issue.search.parameters.lucene.sort.StringSortComparatorSource@3581f47f>!, <custom:"keynumpart_range": com.atlassian.jira.issue.search.parameters.lucene.sort.StringSortComparatorSource@1ac87eb5>!]
2022-03-14 17:00:45,088+0000 http-nio-8080-exec-4 DEBUG jira_admin 1020x1051x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL query: {project not in ("SP")} AND ( {cf[10104] ~ "ep"} OR {key in ("ep")} ) AND {issuetype = "Epic"} order by key DESC
2022-03-14 17:00:45,090+0000 http-nio-8080-exec-4 DEBUG jira_admin 1020x1051x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL lucene query: +(#nonemptyfieldids:projid -projid:(10000) #visiblefieldids:projid) +((+customfield_10104:ep #nonemptyfieldids:customfield_10104 #visiblefieldids:customfield_10104) ()) +type:10000
2022-03-14 17:00:45,092+0000 http-nio-8080-exec-4 DEBUG jira_admin 1020x1051x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL sorts: [<custom:"projkey": com.atlassian.jira.issue.search.parameters.lucene.sort.StringSortComparatorSource@168eb8a5>!, <custom:"keynumpart_range": com.atlassian.jira.issue.search.parameters.lucene.sort.StringSortComparatorSource@4fea5117>!]
2022-03-14 17:00:46,636+0000 http-nio-8080-exec-7 DEBUG jira_admin 1020x1052x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL query: {project in ("SP")} AND ( {cf[10104] ~ "epi"} OR {key in ("epi")} ) AND {issuetype = "Epic"} order by key DESC
2022-03-14 17:00:46,637+0000 http-nio-8080-exec-7 DEBUG jira_admin 1020x1052x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL lucene query: +projid:10000 +((+customfield_10104:epi #nonemptyfieldids:customfield_10104 #visiblefieldids:customfield_10104) ()) +type:10000
2022-03-14 17:00:46,638+0000 http-nio-8080-exec-7 DEBUG jira_admin 1020x1052x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL sorts: [<custom:"projkey": com.atlassian.jira.issue.search.parameters.lucene.sort.StringSortComparatorSource@18bb95fa>!, <custom:"keynumpart_range": com.atlassian.jira.issue.search.parameters.lucene.sort.StringSortComparatorSource@5117bb42>!]
2022-03-14 17:00:46,644+0000 http-nio-8080-exec-7 DEBUG jira_admin 1020x1052x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL query: {project not in ("SP")} AND ( {cf[10104] ~ "epi"} OR {key in ("epi")} ) AND {issuetype = "Epic"} order by key DESC
2022-03-14 17:00:46,646+0000 http-nio-8080-exec-7 DEBUG jira_admin 1020x1052x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL lucene query: +(#nonemptyfieldids:projid -projid:(10000) #visiblefieldids:projid) +((+customfield_10104:epi #nonemptyfieldids:customfield_10104 #visiblefieldids:customfield_10104) ()) +type:10000
2022-03-14 17:00:46,648+0000 http-nio-8080-exec-7 DEBUG jira_admin 1020x1052x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL sorts: [<custom:"projkey": com.atlassian.jira.issue.search.parameters.lucene.sort.StringSortComparatorSource@4a46d714>!, <custom:"keynumpart_range": com.atlassian.jira.issue.search.parameters.lucene.sort.StringSortComparatorSource@26e7a8b5>!]
2022-03-14 17:00:47,394+0000 http-nio-8080-exec-10 DEBUG jira_admin 1020x1053x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL query: {project in ("SP")} AND ( {cf[10104] ~ "epic"} OR {key in ("epic")} ) AND {issuetype = "Epic"} order by key DESC
2022-03-14 17:00:47,395+0000 http-nio-8080-exec-10 DEBUG jira_admin 1020x1053x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL lucene query: +projid:10000 +((+customfield_10104:epic #nonemptyfieldids:customfield_10104 #visiblefieldids:customfield_10104) ()) +type:10000
2022-03-14 17:00:47,397+0000 http-nio-8080-exec-10 DEBUG jira_admin 1020x1053x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL sorts: [<custom:"projkey": com.atlassian.jira.issue.search.parameters.lucene.sort.StringSortComparatorSource@5e47308a>!, <custom:"keynumpart_range": com.atlassian.jira.issue.search.parameters.lucene.sort.StringSortComparatorSource@33386be2>!]
2022-03-14 17:00:47,402+0000 http-nio-8080-exec-10 DEBUG jira_admin 1020x1053x1 d21876 172.30.0.1 /rest/greenhopper/1.0/epics [c.a.j.i.search.providers.LuceneSearchProvider] JQL query: {project not in ("SP")} AND ( {cf[10104] ~ "epic"} OR {key in ("epic")} ) AND {issuetype = "Epic"} order by key DESC

Current logic uses partial user input as a source of CONTAINS operator which, indeed, will not return the expected result in such case:

"Epic Name" ~ "epi"
To get all possible results asterisk ("*") characters should be used in the query:
For the other use-case, the hyphen character needs to be additionally escaped:
"Epic Name" ~ "ux\"-\"pr*"

Expected Results

Suggestions for Epic Name will be returned while typing part of possible Epic's name (like it was before changes introduced at ~~JSWSERVER-21026~~)

Actual Results

In some cases, suggestions are not returned until the whole Epic name (or whole part before hyphen character) is typed

Note on fix

In the fixed version you'll be able to find "Technical Epic" by typing "T", "Techni", "nical", "Epi", "TECHNIC" and so on (i.e. case-insensitive substring search).

Workaround

Possible workaround would be enabling com.atlassian.jira.agile.darkfeature.legacy.epic.picker.enabled dark feature that reverts to the old mechanism of retrieving name for the epic picker.
Note that it is not recommended approach and might cause performance degradation over 100 000 epics.

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List

1_notext_all_suggestions.png
47 kB
14/Mar/2022 4:35 PM
2_typing_epic_no_suggestions.mov
926 kB
14/Mar/2022 4:44 PM
3_typing_epic_no_suggestions_hypen.mov
2.87 MB
14/Mar/2022 4:54 PM
4_epic_name_contains_noresult.png
85 kB
14/Mar/2022 5:08 PM
5_epic_name_contains_asterisk_results.png
94 kB
14/Mar/2022 5:10 PM

is caused by

JSWSERVER-21026 Epic link dropdown slow in large instances

Closed

is duplicated by

JRASERVER-73922 Epic Link searchQuery is not returning all matching values

Closed

JRASERVER-73752 searching for "Epics" to link to an "Issue" are inconsistent and often don't show all available "Epics"

Closed

mentioned in: Page Failed to load; Page Failed to load; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(26 mentioned in)

Form Name

Jim Malgieri added a comment - 21/Oct/2022 8:34 PM

try escaping the left and/or right brackets with a backslash - or use an ampersand as a wildcard after PROG

Jim Malgieri added a comment - 21/Oct/2022 8:34 PM try escaping the left and/or right brackets with a backslash - or use an ampersand as a wildcard after PROG

Jim Malgieri added a comment - 21/Oct/2022 8:33 PM

99d6959fc943 try escaping the left and/or right brackets with a backslash - or use an ampersand as a wildcard after PROG

Jim Malgieri added a comment - 21/Oct/2022 8:33 PM 99d6959fc943 try escaping the left and/or right brackets with a backslash - or use an ampersand as a wildcard after PROG

Artem Tikhobaev added a comment - 11/Aug/2022 10:53 AM

Hi all,

We have also faced this issue in 8.13.22 after upgrading from 8.13.15. Example of Epic Name that is impossible to find now - [02] PROGRESS.

One more workaround is to search by Epic's issue key. In this case Jira returns valid results.

Artem Tikhobaev added a comment - 11/Aug/2022 10:53 AM Hi all, We have also faced this issue in 8.13.22 after upgrading from 8.13.15. Example of Epic Name that is impossible to find now - [02] PROGRESS . One more workaround is to search by Epic's issue key. In this case Jira returns valid results.

Kamil Cichy (Inactive) added a comment - 05/Aug/2022 11:24 AM

~~JSWSERVER-21026~~ improved the performance of the epic picker, but unfortunately it came with annoying bugs.

~~JSWSERVER-21280~~ (this issue) fixes these bugs and is currently awaiting release. In the fixed version you'll be able to find "Technical Epic" by typing "T", "Techni", "nical", "Epi", "TECHNIC" and so on (i.e. case-insensitive substring search).

Kamil Cichy (Inactive) added a comment - 05/Aug/2022 11:24 AM JSWSERVER-21026 improved the performance of the epic picker, but unfortunately it came with annoying bugs. JSWSERVER-21280 (this issue) fixes these bugs and is currently awaiting release. In the fixed version you'll be able to find "Technical Epic" by typing "T", "Techni", "nical", "Epi", "TECHNIC" and so on (i.e. case-insensitive substring search).

Simon König added a comment - 20/May/2022 6:38 AM

We have the same problem on 8.20.8. Makes working with Epics harder. The workaround does not work.

Hyphens do not work and give us no suggestion at all.
Eg.: "epic - " gives us no suggestion even though we have multiple "epic - 1", "epic - 2" usf.

Simon König added a comment - 20/May/2022 6:38 AM We have the same problem on 8.20.8. Makes working with Epics harder. The workaround does not work. Hyphens do not work and give us no suggestion at all. Eg.: "epic - " gives us no suggestion even though we have multiple "epic - 1", "epic - 2" usf.

Mark.Bonifay added a comment - 02/May/2022 8:18 PM

We are currently on Jira version 8.20.8 and are experiencing this problem. Do we know if the solution in 8.22.0 will be back ported to older versions such as ours?

Mark.Bonifay added a comment - 02/May/2022 8:18 PM We are currently on Jira version 8.20.8 and are experiencing this problem. Do we know if the solution in 8.22.0 will be back ported to older versions such as ours?

Mathias Merbold added a comment - 02/May/2022 8:09 PM - edited

The error occours in Jira 8.20.8 too.

Mathias Merbold added a comment - 02/May/2022 8:09 PM - edited The error occours in Jira 8.20.8 too.

Vincent Jansen added a comment - 22/Mar/2022 9:53 AM

We are using Jira version 8.20.7 and have the same problem.

Vincent Jansen added a comment - 22/Mar/2022 9:53 AM We are using Jira version 8.20.7 and have the same problem.

Andre Lehmann added a comment - 17/Mar/2022 12:21 PM

The workaround doesn't change the behaviour if the Epic-Link auto-suggestion. At least not in our environment with Jira 8.22.0

Andre Lehmann added a comment - 17/Mar/2022 12:21 PM The workaround doesn't change the behaviour if the Epic-Link auto-suggestion. At least not in our environment with Jira 8.22.0

Assignee:: Kamil Cichy (Inactive)

Reporter:: Alexander Artemenko

Affected customers:: 62 This affects my team

Watchers:: 81 Start watching this issue

Created:: 14/Mar/2022 5:22 PM

Updated:: 07/Oct/2024 10:23 AM

Resolved:: 23/Aug/2022 1:42 PM

Details

Description

Issue Summary

Steps to Reproduce

Expected Results

Actual Results

Note on fix

Workaround

Attachments

Attachments

Issue Links

Forms

Activity

Collapse comment: Jim Malgieri added a comment - 21/Oct/2022 8:34 PM

Expand comment: Jim Malgieri added a comment - 21/Oct/2022 8:34 PM

Collapse comment: Jim Malgieri added a comment - 21/Oct/2022 8:33 PM

Expand comment: Jim Malgieri added a comment - 21/Oct/2022 8:33 PM

Collapse comment: Artem Tikhobaev added a comment - 11/Aug/2022 10:53 AM

Expand comment: Artem Tikhobaev added a comment - 11/Aug/2022 10:53 AM

Collapse comment: Kamil Cichy (Inactive) added a comment - 05/Aug/2022 11:24 AM

Expand comment: Kamil Cichy (Inactive) added a comment - 05/Aug/2022 11:24 AM

Collapse comment: Simon König added a comment - 20/May/2022 6:38 AM

Expand comment: Simon König added a comment - 20/May/2022 6:38 AM

Collapse comment: Mark.Bonifay added a comment - 02/May/2022 8:18 PM

Expand comment: Mark.Bonifay added a comment - 02/May/2022 8:18 PM

Collapse comment: Mathias Merbold added a comment - 02/May/2022 8:09 PM, Edited by Mathias Merbold - 02/May/2022 8:10 PM

Expand comment: Mathias Merbold added a comment - 02/May/2022 8:09 PM, Edited by Mathias Merbold - 02/May/2022 8:10 PM

Collapse comment: Vincent Jansen added a comment - 22/Mar/2022 9:53 AM

Expand comment: Vincent Jansen added a comment - 22/Mar/2022 9:53 AM

Collapse comment: Andre Lehmann added a comment - 17/Mar/2022 12:21 PM

Expand comment: Andre Lehmann added a comment - 17/Mar/2022 12:21 PM

People

Dates

Backbone Issue Sync