---
title: "Jira integration: Gantt chart and issues in two-way sync"
description: "Every task in the plan becomes an issue in Jira Cloud. Planitude owns dates and dependencies; Jira owns status and assignee."
url: https://planitude.app/integrations/jira
language: en
---

# Jira integration: Gantt chart and issues in two-way sync

Every task in the plan becomes an issue in Jira Cloud. Planitude owns dates and dependencies; Jira owns status and assignee.

Available · Free, included in every account · Work management

## Jira integration: the Gantt chart and the issues stay aligned

Each task becomes an issue in the Jira project you choose, and every change travels on its own within seconds. Planitude decides the plan, Jira decides who works on what and how far along it is.

### Where it helps

- The PMO plans the phases in the Gantt chart while developers work only in Jira.
- Delivery dates stay those of the plan, even when the team closes issues.
- Dependencies between issues become visible on the critical path.

### What travels where

**From Planitude to Jira Cloud**

- Task name and notes → Issue summary and description (Planitude decides)
- Start and finish → Start date and due date (Planitude decides). A date changed in Jira is set back to the plan
- Finish-to-start dependencies → “blocks” links between issues

**From Jira Cloud to Planitude**

- Issue status → Task progress (Jira Cloud decides)
- Assignee → Person assigned to the task (Jira Cloud decides)

## Connect it in three steps

1. **Connect Jira Cloud**: From the project, open Integrations → Jira and sign in with Atlassian. Planitude acts with your Jira account and your permissions.
2. **Choose the project**: Pick the Jira project and the issue type, check how statuses map to progress and who is who. Then export the plan to Jira, import the existing issues, or both.
3. **Keep working as usual**: Move a bar in the Gantt and the issue changes; close an issue in Jira and the task reaches 100%. Conflicts and errors are listed on the integration page.

## Requirements

- **Plan**: Free. Every integration is included in every Planitude account.
- **Who can connect it**: Owner or editor of the Planitude project; viewers see the connection status.
- **What you need**: A Jira Cloud account with the Browse projects, Create issues, Edit issues, Transition issues, Assign issues and Link issues permissions on the Jira project. No administrator permissions are required.

## Good to know

- Nothing is ever deleted automatically: a deleted task leaves the issue in Jira with the label planitude-unlinked, and a deleted issue leaves the task in the plan.
- Summary tasks can become Epics, with the issues of the phase underneath.
- Jira Cloud only; Jira Data Center and Server are not supported.

## Guides and documentation

- [Gantt and Jira: how to keep the plan and the work aligned](https://planitude.app/blog/gantt-jira-sync): Syncing a Gantt chart with Jira Cloud: who owns dates and status, dependencies as Blocks links, conflicts and deletions. A step-by-step guide with Planitude.
- [The tools to connect to Planitude: a guide to integrations](https://planitude.app/blog/planitude-integrations-guide): Planitude integrations: Jira, Azure DevOps, Slack, Teams, calendars, ChatGPT, Claude and Gemini via MCP, API and webhooks, .mpp and .xer files. Which to choose.

## Frequently asked questions about Jira Cloud

### Can I change dates directly in Jira?

You can, but the change is set back to the plan’s value and logged, because dates are calculated from dependencies and calendars. To move a task, you change it in Planitude and the issue updates on its own.

### What happens to the issues if I disconnect the project?

Planitude deletes the webhooks and the credentials. The issues stay in Jira with their label, and no task in the plan changes.

### Do the integrations cost anything?

No. Every integration is included in Planitude, which is free. You only need your own access to the other tool (for example a Jira, Slack or Microsoft 365 account) under its own terms.

## Related integrations

- [Azure DevOps Boards](https://planitude.app/integrations/azure-devops): Two-way sync between tasks and work items, with a Microsoft account or a personal token.
- [Slack](https://planitude.app/integrations/slack): Project updates in a channel and the /planitude status command.
- [Microsoft Teams](https://planitude.app/integrations/teams): Updates in a channel through Workflows and a tab with the Gantt chart.
- [Google Calendar](https://planitude.app/integrations/google-calendar): Subscribe to your private calendar link.

## Connect Jira Cloud to Planitude

Create a free account, open a project and choose Integrations from the ⋯ menu. It takes two minutes.

[Create a free account](https://planitude.app/signup)

*The trademarks mentioned (Jira, Azure DevOps, Slack, Microsoft Teams, Microsoft Outlook, Microsoft PowerPoint, Microsoft Project, Visual Studio Code, Google Calendar, Gemini, Apple Calendar, ChatGPT, Codex, Claude, Cursor, Zapier, Make, n8n, Primavera) belong to their respective owners; Planitude is not affiliated with or endorsed by them.*