Get started

Install and open the chart

A Jira administrator installs the app once. There is nothing to connect: every project gets a Gantt tab that reads the dates your issues already have.

1. Install the app

  1. Open the listing

    In Jira, go to Apps → Explore more apps and search for YTI Gantt, or open the app on the Atlassian Marketplace.
  2. Install

    Choose Get it now (a free trial on paid tiers) and confirm the permissions.

2. Open the Gantt tab

Open any project. Gantt appears in the project's navigation, next to the board, backlog and the other project pages (on company-managed projects it can sit under Apps or More). The chart loads the project's issues in board rank order, with subtasks under their stories and stories under their epics. For plans across projects there is also a Gantt page in Jira's Apps menu (see Filters, views and links).

The first time you open the chart, a short card shows the four things to know: drag a bar to move it, drag the dot at its end onto another bar to link them, click an issue for its details, and Ctrl + mouse wheel to zoom. The ? button in the toolbar (or the ? key) shows it again, with all keyboard shortcuts.

No setup needed for most sites

The app looks for Jira's Start date field and uses Due date as the end. If your site has a Start date field, the chart works as soon as it opens.

3. Check the date fields

Each bar runs from the issue's start date to its end date, both inclusive.

FieldDefaultNotes
StartStart dateFound by its name the first time the app runs, in any Jira language. A Jira admin can choose another date field.
EndDue dateOr any other date field, for example Target end.

An issue with only a due date shows as a one-day bar on that date; one with no dates gets an empty row you can draw on. To use other fields, or if the chart says that no start date field is set, see Settings for Jira admins.

4. Who can do what

ToA person needs
See the chartBrowse projects permission. Issues they cannot see in Jira are not on their chart.
Change datesEdit issues permission (and Schedule issues for the due date, as in Jira).
Rename an issue in the details panelEdit issues permission.
Change the assignee or the statusAssign issues or Transition issues permission; the workflow decides which statuses come next.
Add or remove dependenciesLink issues permission.
Create issues from the chartCreate issues permission.
Save or delete a baselineEdit issues or Schedule issues permission.
Change the app's settingsJira administrator.

Every change is made as the person making it, so Jira's history shows who moved what. Next: your first plan in ten minutes, or read the chart first.