Documentation
WriteBack Gantt for Jira (Date Synchronization & Error Handling)
Jira project managers cannot plan dependencies on a Gantt chart they can trust: the incumbent app intermittently fails to write date and link changes back to Jira, so schedules silently drift and resource planning stalls.
Overview
Jira project managers cannot plan dependencies on a Gantt chart they can trust: the incumbent app intermittently fails to write date and link changes back to Jira, so schedules silently drift and resource planning stalls.
Key Features
- After listing, a Jira site admin can install the app from the Atlassian Marketplace and open it in a project; the Gantt renders that project's issues and dependency links from Jira issue links.
- Dragging a Gantt bar or editing its date fields writes the new start/due date back to the linked Jira issue, and the saved value is still shown after the app reloads.
- If a Jira write fails because of permissions or rate limits, the app shows an inline error that names the issue and lets the user fix or retry without losing the unsaved date change.
- For any app route (including /gantt and /export), a request authenticated as tenant A returns only tenant A's issues and links; tenant B cannot read or mutate that data by direct URL, API call, export token, or shared cache.
- Uninstalling the app deletes the installation's Forge storage, and a support request can produce an export or erase of one person's data.
Getting Started
Install the app into your Jira instance from the Atlassian Marketplace.
Stuck
Ask a person.
If this guide does not answer your question, email us and a human answers. Name the product, what you were doing, and what happened instead. That is genuinely all we need to start.