Days Remaining in Sprint Gadget showing error in the dashboard
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
"Days Remaining in Sprint Gadget" randomly gets timeout errors when loading on the dashboard page.
1
The requested board cannot be viewed because it either does not exist or you do not have permission to view it.
The affected gadget URL is /rest/gadgets/1.0/g/com.pyxis.greenhopper.jira:greenhopper-gadget-sprint-days-remaining/gadgets/greenhopper-sprint-days-remaining.xml
Environment
Jira Software 9.12.2
Diagnosis
Gather HAR file and look for the request url - JIRA-BASEURL/rest/greenhopper/1.0/gadgets/sprints/health?rapidViewId=BOARD_ID&sprintId=SPRINT_ID. The default timeout is 60 seconds. If exceeded the default time, the request will returned errors:
In the atlassian-jira-slow-queries.log, look for the stack trace below:
1 2 3 42024-03-11 10:08:41,533+0000 http-nio-8090-exec-2820 WARN xxxx xxx /rest/greenhopper/1.0/gadgets/sprints/health [c.a.j.i.search.providers.LuceneSearchProvider_SLOW] LuceneQueryExecutionEvent{query={key in ("xxxxx")}, queryTermMetrics={org.apache.lucene.search.TermInSetQuery=TermMetric{count=1, isCustomField=false}}, numberOfClausesInQuery=1, executionTime=15205, numberOfResults=3591, collectorType='TopDocs'}Look for the number of issues returned in the sprint -> numberOfResults=3591 , the results shows the sprints alone contains around 3k+ issues that causes some slowness to display the data in the gadget.
Cause
The sprint selected in the Days Remaining in Sprint Gadget contains a large number of issues causes the gadget failed to load the data.
In the future, the sprint would cause a board timeout errors when closed or complete the sprint due to the fact the sprint contains a large number of issues, please find the known bug ticket -Timeout errors can occur when completing sprints in Scrum boards
Solution
If the number of issues is larger than 1k+ in a single sprint, we recommend reducing the number of issues in the sprint by splitting to half and assign to a new sprint.
Create a new Sprint
Run the following JQL query to find the larger number of issues:
1project = PROJECT_KEY AND sprint = SPRINT_ID AND statusCategory != DoneThe query above will returned all the issues. Kindly modify the query based on your desired results to reduce the number of issues and then assign to a new sprint.
Run a Bulk Edit operation to bulk change the issues sprint to the new sprint from Step 1.
After running the bulk edit operation, please check the issues have been assigned to a new Sprint by running the JQL search
1project = PROJECT_KEY AND sprint = <newsprintID>
Was this helpful?