/
Potential Scope Misconfiguration

Potential Scope Misconfiguration

Depending on your Jira settings, your issues may have multiple fields filled out. Each of those fields can be used for sync with a sub-Box. Potentially, an issue can have various fields filled out. This can become a problem if multiple fields are used for sync - there can be two conflicting rules. Remember, an issue cannot be simultaneously assigned to two sub-Boxes. 

For example:

The first sub-Box (PI1) is synchronized with the 'Change risk' field (value = Low).

The second sub-Box (PI2) is synchronized with the 'Risk probability' field (value = Medium).

In Jira, there is no problem. However, if an issue meets both of those conditions (has both fields filled out as shown above), the App would have to try to put it in both Boxes simultaneously, which can't be done.

 

Related content

Issues are not synchronized properly when it has multiple associations with autopush and autopull enabled
Issues are not synchronized properly when it has multiple associations with autopush and autopull enabled
More like this
Issue can be assigned only active or future sprints
Issue can be assigned only active or future sprints
More like this
Why does the Jira Key field not sync automatically after moving an issue from one project to another?
Why does the Jira Key field not sync automatically after moving an issue from one project to another?
More like this