Gantt chart for Jira Cloud Runs on Atlassian
Several projects on one Gantt, dependencies from your Jira links. Nothing is written until you review the diff.
Two to six projects on one chart, "blocks" links drawn as dependencies across projects. No Premium, no Plans, no extra app.
Every drag is a draft. Apply opens a line-by-line diff with tick boxes. Undo any apply for 30 days. No delete scope, nothing written at install.
First reply within 24 business hours, from the person who wrote the code. Every reproduced bug becomes a test before it is fixed.
Cross-project
Pick projects or a saved JQL filter. Rows follow the Jira parent field: Epic, Story, Sub-task, and any level above Epic your site has.
Your "blocks" links are drawn as arrows, across projects. No Premium plan, no Plans, no extra app.
Drag and cascade
Drag, resize, or move with the keyboard. Every dependent issue is rescheduled in the draft so that the constraint still holds. A dashed ghost keeps the original position in view.
Working days, hours and holidays are set by an admin. Minimum duration is one hour, not one day. Rows you moved yourself stay where you put them.
Review and apply
Nothing is grouped or hidden. What you see is exactly what will be sent. Untick a line and it stays in the draft.
When the panel opens, the app re-reads every issue. A line whose issue changed in Jira since you loaded it is unticked and flagged. A value already equal in Jira is skipped, so the Updated date of untouched issues never moves.
Undo for 30 days
History lists each apply with the exact lines written. Undo restores the previous values through the same diff, with the same permission checks.
Before restoring a value, the app reads the issue again. If someone changed it in between, the line is shown as a conflict and "Undo anyway" is your call.
Critical path and baseline
Turn on Critical path: zero-float rows are highlighted, the others greyed, a Float column appears and a banner tells you how many tasks drive the end date.
Take a baseline and a "Vs baseline" column shows the slip per issue, with a thin bar under each current bar. Kept by the app only, nothing written to Jira.
Dependencies
Drag from a bar to another row to create a "blocks" link. The app refuses cycles and tells you where the cycle is.
Jira only stores that A blocks B. Crosslane lets you refine each link as finish-to-start, start-to-start, finish-to-finish or start-to-finish, with a positive or negative working-time lag. Stored by the app per view; Jira keeps its plain link.
Order and export
Drag a row among its siblings, or Alt + arrow. The order is part of your view and is never written to Jira.
Export takes the current view: PNG of the whole chart, paginated A3 PDF, CSV with a BOM and your locale separator, roll-up dates and slip included. Generated in your browser, nothing sent anywhere.
Built for trust
The install prompt is the whole story. What the app cannot do is enforced by Atlassian, not by a promise.
| Scope | Used for |
|---|---|
read:jira-work | Load issues, links, fields, projects and filters |
read:jira-user | Check group membership when an admin restricts who can write |
write:jira-work | Write the lines you ticked in Review and apply, as you |
storage:app | Drafts, views, baselines, the 30-day journal, in your site's region |
| No delete scope | Jira itself refuses any delete call from the app |
The Permissions section of the settings page, as shipped.
Fast on real sites
Measured on the test site. The app fetches issue ids first, then fields in batches of 100. The last result is kept in the browser and shown while a fresh load runs.
The grid is virtualised and the chart is a single 2D canvas: scrolling and zooming stay smooth at that size.
| Issues on the test site | 5,135 |
| Dependency links | 4,000 |
| Full load | under 4 s |
| Minimum task duration | 1 hour |
| Draft autosave | every 2 s |
Pricing
Billed by Atlassian through the Marketplace, with standard tiering. Trial, invoicing and refunds follow Atlassian's rules.
0 USD
Sites with up to 10 users
1 USD per user per month
Sites with 11 users or more, Atlassian tiering applies
FAQ
All questions, including the ones from support tickets
Longer answers, sourced and dated: Gantt chart for Jira Cloud, native or app, cross-project Gantt without Premium, critical path, baseline, dependencies and lag, safe rescheduling. All guides.
Support
Write to hello@crosslane.app with the issue keys involved, the view (global or project) and the text of the error. First reply within 24 business hours, Monday to Friday, from the developer who wrote the code.
Every reproduced bug becomes a test before it is fixed. The scheduling engine is covered at 100 percent and the data-loss scenarios (network drop mid-write, concurrent edits, undo after a third-party change) are covered end to end.