要約

Users who have the Manage Sprint permission can't start or complete specific sprints in Jira Cloud, or receive error messages when they try to.

Confirm necessary permissions

Users trying to start, edit, or complete sprints on a board must have two permissions:

• Manage Sprints
• 課題のスケジュール

These two permissions must be granted to users on:

• All projects that have issues in the sprint
• All projects that are included in the board where the sprint is being managed

Often, the board filter includes more projects than are actually represented by issues in the sprint.

Check which projects are included in the board

1. Navigate to the board where you are managing the sprint
2. Select ... (More settings) > Configure board
3. On the General tab, examine the Board filter
   1. The Filter details expander will indicate which projects are included in the board filter
4. Ensure any users who manage sprints on this board have the Manage Sprint permission for all included projects

Find the sprint origin board and confirm which projects it includes

When a sprint is created in Jira, the board that was used to create the sprint is recorded. Informally, we can call this the sprint's "origin board."

The origin board's filter is also included in the permissions check when users attempt to manage sprints, even if the origin board isn't where the sprint appears, or is being managed from.

If the board filter is not complex and only includes projects where users have the Manage Sprint permission, this is the next likely cause for permission errors. 

Here's how we'll diagnose this problem:

1. Get your sprint's ID number
2. Query the Jira API for your sprint
3. Compare the sprint's origin board with the board you're working on
4. Query the origin board's filter via API

Retrieve the sprint ID

The easiest method to retrieve sprint IDs in Jira Cloud is via JQL auto-complete.

1. Navigate to Jira issue search
2. Start searching for the Sprint by its name using JQL Advanced Search
3. Select the right sprint from the auto-complete dropdown
4. This will convert the sprint name to ID in the JQL search bar

For other methods, please refer to Jira Software: How to identify the ID of a sprint.

Query the REST API with your sprint ID

Request the following URL in your browser, or send a GET request via an API interface like Postman.

Replace the instance name with your site, and include the sprint ID from the previous step.

https://<instance_name>.atlassian.net/rest/agile/1.0/sprint/<your_sprint_ID>

The return should be something like the below:

{
	id: 7,
	self: https://<instance_name>.atlassian.net/rest/agile/1.0/sprint/<your_sprint_ID>,
	state: "active",
	name: "<your_sprint_name>",
	startDate: "2022-08-15T06:15:38.984Z",
	endDate: "2022-09-06T10:35:00.000Z",
	originBoardId: <origin_board_id>,
	goal: ""
}

Compare origin board details with your working board

Use the value from the "originBoardId" in the following endpoint:

https://<instance_name>.atlassian.net/rest/agile/1.0/board/{board_ID}/configuration

Inside the return object, you'll see various details about the origin board, including its name and associated filter ID:

{
  "id": <id>,
  "name": "<board_name",
  "type": "scrum",
  "self": "https://<sitename>.atlassian.net/rest/agile/1.0/board/<id>/configuration",
  "location": {
    "type": "project",
    "key": "<pkey>",
    "id": "<pid>",
    "self": "https://<sitename>.atlassian.net/rest/api/2/project/<pid>",
    "name": "<project_name>"
  },
  "filter": {
    "id": "<filter_id>",
    "self": "https://<sitename>.atlassian.net/rest/api/2/filter/<filter_id>"

All of this information relates to the board where the sprint was originally created. 

As mentioned, this board's filter factors in to the Manage Sprint permissions check. You'll need to ensure that users have the Manage Sprint permission for all projects included in this board's filter. 

Access the origin board's filter

You can either directly access the origin board based on the information retrieved above, or request the filter details via REST API.

If you copy the URL in the filter's "self" key from the above endpoint, you can directly request this as an API endpoint to retrieve the filter syntax.

Request:

https://<sitename>.atlassian.net/rest/api/2/filter/<filter_id>

The return will include a "jql" value:

"jql": "<origin_board_jql>",

You can now ensure that affected users have the Manage Sprint permission on all projects mentioned in this filter. 

If you can't successfully access any of the origin board or filter details, please contact Atlassian Support to assist further.