...
...
...
...
...
...
...
...
...
...
...
...
Contents:
|
|---|
...
Box Scope
A task can be in the scope of more than one Box. Below, you can find two ways of finding out to determine if a given task is in more than one Box.
...
Gantt
Go to the Gantt module.
Click on a task on the Gantt timeline (don't click on the task key, as it is a link). You will Now you can see a list of all Box IDs related to a given task in a pop-up - the task is in the scope of those Boxes.
You can locate Boxes using their IDs:
The IDs function as links - they will take you to the Overview module of a given Box.
You can also use the search functionality:
In the Box switcher.
In the Overview module of the root (Home) Box.
WBS
When the WBS widget is enabled, you can see the Boxes the task is in the scope of on a Jira issue page.
Make sure the WBS widget is enabled.
Go to the issue page in Jira.
If needed, expand the WBS widget.
Use the Box dropdown of a widget to see the list of Boxes the task is in.
...
The App will list all Boxes a task is in the scope of (regardless of the box's scope type of those Boxes).
...
Using the Gantt module provides you with a list of Box IDs. It doesn't provide give any information on:
how How are those Boxes are boxes related to each other (nested).?
if the Boxes have Own or Sub scope.
...
you can see the Box tree.
All Boxes that are part of the tree path are shown.
Boxes that are a part of the structure , but don't contain the task , are greyed out.
...
Task in multiple Boxes
| Info |
|---|
A single task cannot have different values in different Boxes. It has to be displayed identically in all Boxes. Boxes display tasks based on field values in a connected tool. The App may show a Jira issue in two different Boxes, but it is still the same Jira issue, and it has the same field values. An assignee can't be a different person in one Box and different in another - an assignee is simply a value of a Jira issue displayed in a Box. |
Changing the start/end date in one Box will cause an adjustment of the task period in another Box:
| Multimedia | ||||||
|---|---|---|---|---|---|---|
|
...
Even settings independent from a connected tool (such as a task color) are the same identical in all Boxes. Task color is stored directly in the App and isn't in any way app and is not related to Jira.
| Multimedia | ||||||
|---|---|---|---|---|---|---|
|
Potential Scheduling Conflicts
| Info |
|---|
If you are experiencing erratic task behavior, check if the task is in the scope of multiple Boxes. Conflicting scheduling rules applied to a single task in different Boxes (such as task scheduling mode, WBS structure, and dependencies) can make the behavior of the App seem inexplicable:
|
Below you can find a few simple examples of possible situations. Keep in mindRemember, this is not an exhaustive list but is instead meant to demonstrate possible problems.
...
scheduling mode - auto top-down
the same task has different parent tasks in two separate Boxes
Period The period of a child task can't can’t be changed in the ALFA Box because of restrictions imposed by a parent task in the BETA Box.
| Multimedia | ||||||
|---|---|---|---|---|---|---|
|
...
Task ALFA-9 can be moved without any problems, but its duration can't be extended. Additionally, changes of period of ALFA-12 result in identical period changes of ALFA-9.
...
Situation: dependency + parent relationship conflict
| Info |
|---|
Sometimes, a task may stay in a position that defies validation rules because a new validation hasn't been triggered yet. Still, if you try to move/adjust a task (or perform any other action that is a trigger), validation will happen. |
...
| Multimedia | ||||||
|---|---|---|---|---|---|---|
|
Dependency created
Moving the child task
Moving the target task of the dependency
