-
Suggestion
-
Resolution: Fixed
-
7
-
-
Summary
Despite the fix in JSWSERVER-20452, it takes more than 20s to load the epic dropdown in large instances (300k+ epics)
Steps to Reproduce
- Create 300k epics in an instance.
- Open the epic link on an issue.
Expected Results
The epics should load only partially and fast, the same way we do with user list in the assignee field.
Actual Results
We load all epics from the index, this can take more than 20s.
Workaround
Archive unused or closed epics.
- causes
-
JSWSERVER-21280 "Epic Link" dropdown suggestions are not working properly due to changes introduced at JSWSERVER-21026
- Closed
-
JRASERVER-73724 The "Epic Link" field in JIRA stopped displaying the Epics list in alphabetical order
- Closed
- is related to
-
JSWSERVER-20452 Epic Link query causes timeouts
- Closed
-
JSWSERVER-21250 Configure the frequency at which Epic Link suggestions may submit search requests.
- Closed
- mentioned in
-
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...
- relates to
-
DELTA-1134 Loading...