Auto-reassign on leave start
The Forge app reads scheduler events and reassigns the user's open issues to the configured coverer when leave begins.
The Forge app reads scheduler events and reassigns the user's open issues to the configured coverer when leave begins.
Each reassigned issue gets a comment with leave dates and a link to the Vacation App request, so the coverer has context.
Toggle reassignment off on individual requests when handover is unnecessary.
When leave ends, issues unchanged by the coverer are reassigned back. Issues edited by the coverer stay with them.
From Atlassian Marketplace, or via `forge install`.
Match Jira users to Vacation App members by email — one click.
Reassignment fires automatically when leave starts.
Every scope we ask for, and exactly why.
Pricing. Jira integration is included on the Premium plan ($4/user/month). See full pricing →
| Scope | Type | Why we need it |
|---|---|---|
read:jira-work | oauth | Find the user's open issues to reassign at leave start. |
write:jira-work | oauth | Reassign tickets and add a coverer comment with leave dates. |
read:jira-user | oauth | Match Jira users to Vacation App members by email. |
Still stuck? Email [email protected]. We respond within 24 hours.
Cloud only — Atlassian Forge is a Cloud-only platform.
Issues edited by the coverer stay assigned to them. Untouched issues are reassigned back to the original assignee on return.
Yes. The leave request form has a per-request toggle to disable Jira reassignment.
We store only issue keys and assignment events for audit. Issue content stays in Jira.
Atlassian admin → Apps → Vacation App → Uninstall. All Forge tokens are revoked instantly.