Baseline

A saved snapshot of chart dates used to compare the current plan against an earlier version of the schedule.

Helps track delays and measure schedule drift over time.

Critical path

The sequence of linked tasks that determines the overall project duration. If a task on the critical path is delayed, the project end date may also be delayed.

Highlights the tasks that need the closest attention.

Dependency

A logical relationship between two tasks that controls how one task affects another task’s start or finish.

Supports realistic scheduling and impact analysis.

Deadline

A target date by which a task should be completed. It is used as a scheduling and tracking reference.

Helps teams spot tasks that risk finishing late.

Duration

The length of time a task spans on the timeline. Depending on chart setup, duration may be calculated from dates, work, or internal scheduling rules.

Used to understand how long work is planned to take.

Milestone

A zero-duration planning point that marks an important event, handoff, checkpoint, or delivery date.

Makes key events easy to see on the timeline.

Scenario

A what-if planning mode where users can test schedule changes without immediately applying them to the live Jira data.

Useful for evaluating options before committing changes.

Task conflict

An inconsistency between task work and task duration that requires resolution.

Prevents misleading schedules and helps keep planning data accurate.

Finish-to-Start (FS)

A dependency where the first task must finish before the second task can start.

The most common dependency type in project planning.

Start-to-Start (SS)

A dependency where the second task cannot start until the first task has started.

Useful when activities begin together or in parallel.

Finish-to-Finish (FF)

A dependency where the second task cannot finish until the first task has finished.

Helps coordinate completion timing between related tasks.

Start-to-Finish (SF)

A dependency where the second task cannot finish until the first task has started.

Less common, but supported for specialized planning cases.

Lead

A scheduling adjustment that allows a successor task to start or finish earlier than the dependency would normally permit.

Useful when tasks can overlap.

Lag

A scheduling adjustment that delays a successor task after a dependency point.

Useful for wait times, cooling periods, approvals, or buffer time.

Auto-scheduling

Automatic recalculation of task dates based on dependencies, constraints, and planning rules.

Reduces manual schedule maintenance.

Cyclic dependency

A circular dependency loop where tasks depend on each other in a way that makes valid scheduling impossible.

Must be resolved for auto-scheduling to work correctly.

Constraint

A rule that limits when a task can start or finish.

Keeps schedules aligned with real project requirements.

SNET

Start No Earlier Than. The task cannot start before a specified date.

Useful when work must not begin too early.

SNLT

Start No Later Than. The task must start by a specified date.

Useful when a latest acceptable start date exists.

FNET

Finish No Earlier Than. The task cannot finish before a specified date.

Useful for minimum elapsed time requirements.

FNLT

Finish No Later Than. The task must finish by a specified date.

Useful for hard delivery targets.

MSO

Must Start On. The task must start on an exact date.

Useful for fixed-start events.

MFO

Must Finish On. The task must finish on an exact date.

Useful for fixed-finish commitments.

Task mode

A setting that defines how parent tasks behave in relation to their children.

Affects how dates and summaries are calculated.

Manual mode

A task mode where a parent task’s dates are set manually instead of being calculated automatically from its child tasks.

Useful when a parent task must keep fixed dates independent of child task timing.

Bottom-up mode

A task mode where a parent task’s dates are calculated from its child tasks.

Useful when parent timing should reflect actual child schedules.

Resource

A person assigned to perform work on a task. In chart configuration, this is usually based on a selected Jira field such as assignee.

Supports workload visibility and planning.

Resource panel

The chart area that shows workload, availability, and overload information for resources.

Helps teams balance work and spot bottlenecks.

Resource calendar

A calendar that defines working and non-working time for a specific resource.

Improves schedule realism for part-time work, holidays, and exceptions.

Resource leveling

A process that redistributes tasks to resolve overload based on scheduling rules and resource assignments.

Helps prevent over-allocation and unrealistic plans.

Overload

A condition where a resource has more assigned work than available capacity.

Signals planning risk and possible delays.

Availability

The amount of working time a resource has during a given period.

Used to compare planned work against actual capacity.

Work

The effort required to complete a task, often measured in hours or days.

Helps distinguish effort from timeline length.

Chart

A configured Gantt view that determines what projects, tasks, calendars, fields, and settings are included.

The main working object in Gantt Suite for Jira.

Live (chart)

The active chart state that works with real Jira and Gantt Suite data, not a scenario or temporary what-if plan.

Clarifies when changes affect the actual working schedule.

Chart configuration

The settings that define chart behavior, included data, scheduling logic, calendars, sharing, and security.

Controls how the chart works and what users see.

Main chart calendar

The primary calendar assigned to a chart. It defines default working and non-working time used for scheduling when no more specific calendar applies.

Provides the base schedule for task dates and duration calculations.

Global calendar

A reusable calendar available across charts, usually managed at the app or company configuration level.

Helps keep working time, holidays, and exceptions consistent between charts.

Company-wide configuration

Global app settings managed by an administrator that affect default behavior for new charts.

Provides standardized setup across the organization.

Custom view

A saved visual setup of a chart, such as selected columns, filters, grouping, or display options.

Makes it easy to switch between different working perspectives.

Impersonated view

A chart view opened or previewed as another user or role to verify what that person can see and do.

Helps validate permissions, sharing settings, and user-specific access.

(Chart) Manager

A chart role with the highest chart-level permissions, typically able to manage chart settings, sharing, and access.

Defines who can administer a chart and control its configuration.

(Chart) Editor

A chart role that can make permitted changes to chart data, such as editing tasks or schedule details, without full management rights.

Allows contributors to update plans while limiting administrative control.

(Chart) Viewer

A chart role that can open and view a chart but cannot make changes.

Supports safe read-only access for stakeholders.

Grouping

A way to organize tasks visually by one or more fields, such as assignee, project, or parent.

Improves readability for large charts.

Filter

A rule that narrows which tasks are shown on the chart.

Helps users focus on relevant work.

JQL filter

A filter based on Jira Query Language.

Useful for advanced task selection using Jira search logic.

Timeline

The right-side visual area of the chart where tasks, dates, links, markers, and planning elements appear over time.

The primary space for schedule visualization.

Multiselect

A feature that lets users select multiple tasks or items at the same time.

Speeds up bulk actions and editing across several tasks.

Gantt fields

Default fields provided by Gantt Suite for Jira. Some are native to the app and do not exist as Jira fields.

Help represent planning data not available in standard Jira.

Native Gantt field

A field managed internally by the app rather than directly stored as a Jira custom field.

Important for understanding what syncs to Jira and what stays in the app.

% Done

A Gantt field that shows overall completion of a parent task based on the statuses of its child tasks.

Provides quick progress visibility directly in the chart.

Start date

The planned beginning of a task. Depending on chart mode, it may sync with Jira or be handled internally.

Essential for placing tasks on the timeline.

End date

The planned finish of a task. Depending on chart mode, it may sync with Jira or be handled internally.

Essential for determining task span and delivery timing.

Internal task

A task that exists only inside Gantt Suite and is not linked to a Jira issue.

Useful for planning supporting work that should not live in Jira.

Embedded chart

A publicly shared chart displayed inside another page or site using embed code.

Useful for sharing plans outside Jira.

Chart URL

A public share link that allows others to view a shared chart in a browser.

Supports external reporting and collaboration.

Export

The process of generating chart output in another format such as CSV, Excel, Microsoft Project, or image.

Useful for reporting and sharing outside the app.

REST API

An interface that allows authorized users to interact programmatically with Gantt Suite features.

Supports automation and integrations.

API token

A user-generated token used to authenticate access to the REST API when permitted by an administrator.

Required for secure API usage.

Chart health

A diagnostic feature that helps identify issues or inconsistencies in the chart, such as violated constraints or other planning problems.

Useful for validating schedule quality.

Violated constraint

A situation where a task’s dates do not comply with its configured constraint.

Signals that the schedule needs review or correction.

HAR file

A browser-generated network log used for troubleshooting technical issues.

Useful for support investigations.

Console output

Messages captured in the browser developer console that can reveal client-side errors or warnings.

Helps diagnose loading, scheduling, or integration issues.