...
Task start field - defines a Jira field to store task start date/time. Both, date and datetime fields are allowed. Fields of type date can’t store time, so time component will be lost and tasks would always start at start of a day. For your convenience, the field type is displayed on the right side in parenthesis.
The field must be added by admin user to project’s create/edit screens.Task end field - defines a Jira field to store task start date/time. Both, date and datetime fields are allowed. Fields of type date can’t store time, so time component will be lost and tasks would always start at start of a day. For your convenience, the field type is displayed on the right side in parenthesis.
The field must be added by admin user to project’s create/edit screens.Task deadline field - defines a Jira field to store task deadline. This field is optional. Task edit dialog will only allow to set a deadline if the Task deadline field is set.
Task duration - defines how task duration is calculated, e.g. how long the task will be on Gantt chart.
There are two options:
1) Calculated based on start and end dates only
Task duration is calculated as task end date minus task start date. Default duration of one day will be set if start or end date aren’t provided. This option requires Task start field and Task end field (see above) to be configured. Otherwise error will be shown.
2) Calculated based on provided estimate, otherwise based on start and end dates
Task duration equals task estimate. Estimate comes from Jira’s standard time tracking field. If estimate is missing, task duration will be calculated as end date minus start date.
...
Chart start date / Chart end date - define chart boundaries. In most cases, data outside this range is not visible, and chart can only be scrolled within this range.
These dates can be left blank. In this case, app will try to determine dates based on chart tasks. But this might be inconvenient when creating a chart since task dates aren’t yet defined and chart range would be too narrow.JQL filter - Jira JQL query, allows to narrow down the task selection for a chart.
Gantt Suite appends JQL filter to own query. The resulting query can be viewed by clicking view generated link below the label. If JQL filter contains “OR” keyword, please wrap the query in parentheses ( ), like shown below. Otherwise, the resulting JQL will return incorrect results from Jira. Also, please note that “order by …“ clause stays out of parentheses.
Impersonated view - normally, users without permissions to access projects or issues will not see them on a chart. This option lets users with restricted access to see tasks on a chart in view-only mode. The name of a person who enabled the impersonated view is shown next to enabled Impersonated view.
To summarize, this option allows everybody to see a chart like the impersonation person does (even though, viewers might not have have the required Jira permissions).Default task mode
Defines the default behaviour for tasks with children (e.g. parent tasks). The behaviour can be overridden for each task, when viewing the chart. High chances are your desired selection here is “Bottom-up“ (the default one).Bottom-up - initially selected mode. In this mode parents are defined solely by children. This means parent task ignores its information in Jira (like start/end dates, work, etc) and calculates itself from children. The parent starts where the first child starts, and the parent ends where the last child ends. Progress and work also calculated from children. Moving a child outside parent’s boundary will resize the parent. The parent itself can’t be resized.
Manual - parent task duration is independent from its children. In this mode, the parent task reads its estimate, progress, work, etc. from Jira rather than calculates from children. Unlike in “Bottom up“ mode, this mode allows resizing of parent tasks.
Screens, which are present on 'Chart settings' tab of the chart configuration, is a convenient feature that allows to assign Jira fields to Jira project screens directly from the chart configuration. The Screens field, in chart configuration, is only visible to admin users. The app will try to populate screens automatically, once a project is selected inside the Project field. On Add fields button click, the app would assign selected Task start/end fields and Time Tracking field to selected screens. The app requires the Time tracking field in order to specify the task duration, and will not work correctly if the field is not added to the project screens. Despite the Screens feature, we strongly recommend our customers to additionally review and correct, if needed, Jira project screens. This can be done either by Jira admin or project admin, in project settings.
...