-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
6.1
-
6.01
-
The issue navigator makes a REST request to rest/api/2/filter/favourite when it loads. This request is expected to respond with an array of objects with filter data in them.
If this REST request fails – e.g., gives a non-200 response, times out, or contains something that isn't an array – then the issue navigator stops working properly.
- causes
-
TF-350 Failed to load
- derived from
-
JSP-176852 You do not have permission to view this issue
Form Name |
---|
[JRASERVER-36172] Issue navigator stops working if favourite filters can't be retrieved
Minimum Version | New: 6.01 |
Workflow | Original: JAC Bug Workflow v2 [ 2832302 ] | New: JAC Bug Workflow v3 [ 2923265 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2553055 ] | New: JAC Bug Workflow v2 [ 2832302 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1521455 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2553055 ] |
Labels | New: affects-server |
Component/s | New: Issue Navigation & Search - Filters [ 43391 ] | |
Component/s | Original: Issue navigator [Deprecated] [ 10670 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 666328 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1521455 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v5 [ 642807 ] | New: JIRA Bug Workflow w Kanban v6 [ 666328 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v5 [ 589141 ] | New: JIRA Bug Workflow w Kanban v6 [ 642807 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Soaking [ 10041 ] | New: Resolved [ 5 ] |