The following custom configurations can be set using the Structure Dark Features and Fine Tuning interface.
Scheduling and Time Limits
Structure.Gantt has some facilities that prevents it from locking the Jira instance in the event that scheduling operations are taking too much time. By default, we assume that most charts calculations should take no more than 5 minutes, and Structure.Gantt will stop performing any further scheduling for a particular structure if the calculation exceeds this time. In this case, a message such as this will be shown:
These situations are treated as abnormal and usually mean that the Structure.Gantt scheduling algorithm got stuck for some reason, so we highly recommend that you contact our support team to further investigate the cause. In some rare cases, tuning of these facilities may be needed.
|This property declares scheduling timeout (in seconds), i.e. maximum time Structure.Gantt can perform scheduling calculations for a single chart. (The default value is based on our measurements for structures with 100,000 issues. It should be sufficient for most cases, but it can be configured to a lower or higher value.)||300 seconds|
|This property holds a comma-separated list with the IDs of the structures that have Gantt chart calculations turned off. Any structures listed here will automatically be excluded when Gantt scheduling takes more time than is declared by the structure.gantt.settings.schedulingTimeLimit.||Empty|
|This property declares an additional timeout when waiting to apply a change made by the user on a Gantt chart. Recommended values are up to several minutes.||120 secs|
|This property declares the timeout when waiting for Gantt attributes, in order to show them in the Structure grid. Structure.Gantt will try to get the attributes within the declared time and then display empty values if the operation fails. As soon as the chart is finished calculating, the actual values in the grid should refresh automatically. Recommended values are from 30 secs to several minutes.||30 secs|
|The timeout for poll to wait for the ability to calculate the update. This timeout ensures Structure.Gantt will not hold update requests and threads for an unlimited amount of time. It is recommended to keep this value less than 1 minute.||10 secs|
Resource Leveling Configurations
When false, Edit permissions are required to start or reset Resource Leveling.
When true, Control permission is required.
|Set to false to disable Resource Leveling, cancel all leveling calculations and delays, and remove any controls related to Resource Leveling from the UI.||true|
|Determines the maximum number of tasks that can be leveled by a single Leveling session.||5,000|
Maximum number of threads allocated for Resource Leveling calculations on every node.
The number of threads is determined by the formula `NUMBER_OF_CPU_CORES * threadPoolSizeFactor` and by default means that Resource Leveling may use no more threads than half of the available CPU cores, i.e. for a 4 CPU core machine, Resource Leveling should use no more than 2 threads for calculations. Setting this value to `0` will guarantee Resource Leveling will occupy only a single thread on any node.
|Set to false to disable Sandbox feature, and remove any controls related to it from the UI.|
|Include resolved tasks in the critical path.|