-
Type:
Bug
-
Resolution: Low Engagement
-
Priority:
Low
-
None
-
Affects Version/s: 6.0.1/OD-15, 6.2.5, 6.2.7, 6.3.1, 6.4.3
-
Component/s: Navigation - Filters
-
6
-
9
-
Severity 3 - Minor
-
7
When you browse to Issue Navigator, JIRA will throw a REST call to retrieve the subscription details of every favorite filter that you might have.
Environment
JIRA 6.4.11
Steps to Reproduce
- Login to JIRA
- Create and subscribe into a few more filters (optional)
- Navigate to Issue Navigator page
Expected Results
JIRA will not try to retrieve the subscription details of your favorite filters; Issue Navigator will be displayed as usual.
Actual Results
JIRA will call for rest/api/2/filter/favourite?expand=subscriptions[-5:]&_=1406622755881 and retrieve the subscription details of every favorite filter that you might have. On first access, it adds 2.7s load time to open Issue Navigator page. This adds a lot of overhead and the information is not used anywhere on the screen when you first open it.
![]()
Notes
This could be removed to improve page load times.
Workaround
No available workaround.
- relates to
-
JRASERVER-65892 Favourite filters REST Resource is needlessly retrieving associated share users
-
- Closed
-
-
JRASERVER-65930 Favourite filters REST Resource consumes large amount of memory when user has large number of filters
-
- Closed
-
-
JRASERVER-73189 Having favourite filters with large amount of issue key literal results in Issues menu loading slowly
-
- Gathering Impact
-
- mentioned in
-
Page Loading...