Scope misconfiguration errors and warnings

X tasks in the scope. Synchronization may take a bit longer...

While trying to save the scope, you might encounter the following warnings:

• "X tasks in the scope. Synchronization may take a bit longer..."

The warning will appear if the task limit in Technical info is not defined or exceeds 25,000 tasks.

• "Scope misconfiguration! A value with ID '10375' does not exist for the field 'id.' user: (...)."
  In case of Scope Misconfiguration / Scope corruption, visit the Scope Misconfiguration - Corrupted Scope page for troubleshooting instructions. 

The scope is corrupted:

• A scope element (Jira project, filter, board) ceased to exist - JQL used to define box scope leads to a deleted item

• A scope owner no longer has permission to access at least one of the scope elements.

• A scope owner is no longer active (the user account in the connected tool has been disabled)

There is a problem with at least one scope element

Open

Scope Owner doesn't have access to one of the elements (Board/ Filter/ Project) you have tried to use to define the Box scope.

Example

The app 'reads' all tasks through the lens of a Scope Owner. A Box can only include tasks to which the Scope owner has at least viewing access. 

In the example below, "Tofu" is the Jira user chosen to be a scope owner. User "Tofu" doesn't have permission to access the project added to the scope definition. As a logged-in user, you can have full access to a given item, but if the Scope Owner can't access it, the error will pop up. 

Open

Solutions

Change the scope owner

You can use a different user as a scope owner. The new Scope Owner user must have permission to access a given project/filter/board. 

Change permissions of the item

In the example above, the Project permissions were the problem. Go to project settings:

Open

You have two options.

1. Associate a different scheme with the project.

   Open

   

2. Modify the existing permissions scheme.

   Open