The color display of the projects and tasks in <%% APP_NAME> is diverse and depends on how you look at the project currently.
In a standard design view the color display "status" is set by default. In this color display the color of the sum operations, which are more subtasks subordinate, depende on their subtasks. They are shown in the color of its most vulnerable part of operation, e.g. in orange, red or black if no process is in jeopardy. Individual processes are colored according to their status set. Here, the color of both the state as well as the location depends on the timeline , as the following table is highlighting.
Status |
Single task |
||
in the past |
today |
in the future |
|
Undone |
grey |
grey |
grey |
Interrupted |
red |
green |
green |
Canceled |
dark grey |
dark grey |
dark grey |
Released |
red |
orange |
light blue |
Started |
red |
green |
green |
Finished |
dark green |
dark green |
dark green |
To change the color display, select the desired option by clicking in the menu "View" under the menu item "color display". There you can also find out which view is active.
If you have selected the View "hazard", the sum operations are colored according to the risk of their most vulnerable part operation, or black if no subtask is endangered. It is here, however, the danger of the resouces, considered for those operations, not the timing of the actual process hazard. Only with the status of "Completed" (dark green) or "Cancel" (dark gray), the burden of resources on the process have either been executed or not at all costs, and that therefore no danger exists. In all other cases, the process is colored according to the number of risk. Here, a number of zero risk is green and all rows above in a color gradient from yellow to red.
In the "due representation" the events of the most urgent tasks are shown due to their part. You can specify by yourself the thresholds for the urgency of the individual events, even in the options. The values can be found in the "Advanced Settings" and then select "View Settings". Here you can see the three thresholds (the period for critical, critical, very critical) set in days. As standard there are 2, 1, and 0 days are set, which describes a process in the following table.
Status |
Single task finishes |
|||
today |
in one day |
in two days |
in more than two days |
|
Undone |
grey |
grey |
grey |
grey |
Interrupted |
red |
orange |
yellow |
green |
Canceled |
dark grey |
dark grey |
dark grey |
dark grey |
Released |
red |
orange |
yellow |
light blue |
Started |
red |
orange |
yellow |
green |
Finished |
dark green |
dark green |
dark green |
dark green |
If you have in the menu item "color display" selected the option "Custom Colors", all summary tasks are colored with black and all individual events in the color that is set in its properties in the "General" under "Custom Color" is shown.
In many cases, the operations shall be displayed more clearly, because often only the timing is interesting. In this case it is possible to represent the partial operations of each sum process in the graphical representation. If then the total transaction is closed, so to speak no part of its operations should be shown, in the sum beam itself the position of the sub-processes are still detected. Choose the menu "View" menu, "Planning Board" and it is a view similar to the following.
As you can also see, in the sum operation Project 1 the sub tasks of process operation 3.1 to 3.4 are not visible because; they are summarized and presented in the total process operation 3. Therefore, in this view, a certain structure of the project is necessary. But it is also possible to set in the options a recursive color inheritance, by then the individual processes to be displayed up to the project. This value can be found in the "Advanced Settings" and then under "Operation Settings". Here you can affect with the value "Recursive color inheritance" this inheritance. However, this leads for larger projects very quickly to a complexity, since it is not possible to differ at the various different color representations, which part of the total beam belongs to which part process. <AUTHOR_SHORT%%> recommends to use this view for very small projects. In the example discussed so far this looks like the following.