| Info |
|---|
Once all the issues have been addressed, clear the log by clicking the "Clear log" button within the "Box warnings" dialog. Even if issues have been addressed, the dialog box won't disappear until the log has been cleared. |
Causes of Scope Misconfiguration
The error appears when the current Scope Definition of a Box can't be implemented because:
- A scope element (Jira project, filter, board) ceased to exist - JQL used to define Box scope leads to a deleted item.
- A project included in the Box scope has been archived.
- 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).
This error can occur when:
- Some permissions/settings have been changed in the external tool - the scope used to function properly, but now it is corrupted. For example, the Scope Owner user account has been disabled in Jira.
- A scope element (Jira project, filter, board) has been deleted. Tasks from a deleted project are no longer displayed in modules. When you go to the Scope Definition, the problem will be indicated in red.
.png?version=1&modificationDate=1701162357812&cacheVersion=1&api=v2&width=1867)
- You are trying to define a scope of a Box - in such a case, if there are any problems, after clicking "Save," you will immediately see the message informing you that the scope has not been properly configured.
- The user adds to a Box a new task (Jira issue) that the Scope Owner can't access (keep in mind, when you create a new task, for example, directly in Gantt, you always have to make sure the item will be created in the correct Jira project).
.png?version=1&modificationDate=1701162351341&cacheVersion=1&api=v2&width=1853)
- There are missing permissions in team-managed projects. No access to Jira Cloud issues with role-restricted permissions (this option is available for team-managed projects in Jira Clouds).
If you decide to restrict an issue for specific roles, BigPicture will not be able to access such issues and you will see them as "No access" items in the App.
This situation happens because it is impossible to add an add-on to any project role (including Big Picture). We encourage you to vote for the issue we reported to Atlassian describing this inconvenience.
There are missing permissions on the issue security level (company-managed projects in Jira Cloud).
The warnings appear when trying to move tasks on the Gantt module (BigPicture is trying to change the "Start date" and "End date" fields).
You can have trouble accessing specific issues in BigPicture as you will see "No access" items in scope.
You can experience this situation because single tasks might have a security level set. If the lock icon is red, the settings are active.
...
Automatic Rules Check
| Info |
|---|
You can't access Box Configuration if a Box is in 'Closed' status. |
Every Box has a scope - it contains a collection of tasks from connected tools such as Jira and Trello. Box scope can be found in Box configuration under Tasks > Scope definition. To fix the problem, go to the Scope definition of a Box and verify the Automatic rules. Make sure that no invalid JQL has been used and that all added Boards, Filters, and Projects still exist.
You can click the "Scope Settings" button to go directly to the Scope Definition.
.png?version=1&modificationDate=1701162352873&cacheVersion=1&api=v2&height=234)
When you go to the Scope Definition, the problem will be indicated in red.
.png?version=1&modificationDate=1701162357812&cacheVersion=1&api=v2)
If the incorrect Box Scope does not allow you to load the Box/Program, you can access the Box configuration from the Overview by clicking on the cog icon on the right side:
...