How to increase the limit of 120 sprints and 25000 estimated issues at the Velocity Chart
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
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.
*Fisheye および Crucible は除く
要約
The Velocity chart includes estimates (committed and completed) from all issues in your sprints. For performance reasons, we’re showing a maximum of 25,000 issues.
The chart includes only completed sprints whose End date is within your chosen timeframe. By default, it shows the maximum of 120 sprints—if your timeframe includes more, we’ll show the latest 120.
ソリューション
Changing the Limit
It is possible to run the limit using a REST method:
<JIRA_URL>/rest/greenhopper/1.0/rapid/charts/velocity/max-sprints<JIRA_URL>/rest/greenhopper/1.0/rapid/charts/velocity/max-issuesBoth of the endpoints for changing limits accept two HTTP methods:
GET to check the current limit (any changes are also added to the audit log and logged as WARN in the regular logs)
PUT with JSON body like {"value": "120"}
curl -vvv -XPUT http://<myjira.base.url:port>/rest/greenhopper/1.0/rapid/charts/velocity/max-issues -H 'Content-Type: application/json' -d '{"value": "30000"}' -u <your Jira admin user>
The REST will return the HTTP response 204 if the execution was successful.