Platypus - User Documentation
This space holds the end-user documentation for Platypus, the dependency date rescheduler for Jira. Start with How to get started, then see How to configure it for the full settings reference.
What is Platypus?
Platypus keeps your Jira due dates in sync. When you move the due date of an issue, Platypus automatically reschedules every issue that depends on it — across deep chains and even across projects — so your plan stays consistent without manual rework.
It is calendar-aware (it can skip weekends and holidays), it preserves each task's duration, and it can either apply changes automatically or hold them for your review with a preview-and-confirm step. Every change is recorded in a 60-day activity log.
Guides
How to get started — for everyone: link your issues, set due dates, and watch dependent dates cascade. Includes the preview-and-confirm flow.
How to configure it — for Jira admins: every global and per-project setting explained, plus the working calendar, anchors, and the activity log.
Key concepts at a glance
Term | What it means |
|---|---|
Predecessor / dependent | If issue A blocks issue B, then A is the predecessor and B is the dependent. When A's date moves, B is rescheduled. |
Gap | The spacing Platypus leaves between a predecessor's due date and its dependent's start (for example, +1 business day). |
Apply mode | Automatic applies changes immediately; Preview & confirm parks them for review first. |
Anchor | An issue you pin (with a label) so Platypus never moves its dates — useful for fixed deadlines. |
Cascade | The chain reaction of rescheduling that flows from a changed issue through all of its dependents. |
Updated: