Handoff for Jira

📋 Overview

Handoff for Jira is an Atlassian Forge app installed directly inside Jira Cloud. It gives each team member a personal, priority-ordered ticket queue, a structured workflow for passing work between teammates, a shared blocker visibility system, and a team management view — all without leaving Jira or switching to external tools.

📘 Full Guide

Installing the App

1. Go to the Atlassian Marketplace and search for Handoff for Jira.
2. Click Get it now and select your Jira Cloud site.
3. Accept the required permissions: read & write Jira work items, read Jira user profiles.
4. Once installed, open any Jira project and find Handoff for Jira in the left-side Apps menu.

My Queue

Every user has a personal ordered list of up to 25 Jira tickets that serves as their daily work list.

• Issue Key — Clickable link that opens the Jira ticket
• Type Badge — Bug / Story / Epic / Task / Sub-task
• Priority — Color-coded dot and pill (Highest, High, Medium, Low, Lowest)
• Status Badge — Current Jira status of the ticket
• Assignee — Avatar and display name

Tickets that are blocked (🚫) or blocking another ticket (🔗) show an inline expand icon. Click to reveal the related ticket details without leaving the queue.

Queue Visibility Settings

• Private (default) — Only you can see your queue
• Shared with specific teams — Select which teams can view your queue
• All teams — Anyone in your Jira instance can view your queue

Browse & Add

Search across all open Jira tickets in your instance and add them to your queue directly from the browse table.

• Search by issue key (e.g., PROJ-123), keyword, or project prefix
• Filter by issue type: Bug, Story, Epic, Task, Sub-task
• Filter by status: 🚫 Blocked / 🔗 Blocking / ✓ In your queue
• Sort by issue key or last updated

Visual Row Highlights

• Red row — Ticket is blocked
• Yellow row — Ticket is blocking another ticket
• Blue row — Ticket is already in your queue

Handoff

Let one or more teammates know which tickets to focus on — send up to 10 tickets in a single structured handoff. Recipients can then add some or all of those tickets to their personal queue.

Sending a Handoff

1. Select up to 10 tickets from your queue or the browse view.
2. Drag ticket chips to set the priority order for the recipient.
3. Choose one or more recipients from your Jira instance.
4. Write a required note with context, priorities, and dependencies.
5. Toggle per-ticket 📣 / 🔇 to post or suppress a Jira comment on each ticket.
6. Send — recipients get a NEW-badged card in their Inbox.

Receiving a Handoff

• Accept — Choose to add some or all of the tickets to your personal queue, in the priority order suggested by the sender. A "✓ accepted this handoff" comment is posted on the first Jira ticket.
• Decline — The handoff is rejected; the sender is notified.
• Archive — Move the handoff to your archive/history without accepting.

Blocker Alert

When work is stuck, fire a Blocker Alert. It surfaces the blocked work to the whole team and posts a timestamped comment directly on the Jira ticket — no more blockers buried in someone's DMs.

Creating a Blocker Alert

1. Select the blocked ticket(s) — the tickets that are stuck (up to 5).
2. Select the blocking ticket(s) — the tickets causing the block (up to 5).
3. Select the team members responsible — each gets an alert card in their Inbox.
4. Leave a comment with context — automatically posted on the Jira ticket.
5. Submit — the blocker is added to a shared global list visible to everyone on the instance.

Resolving a Blocker

When you want to resolve the blocker, add the tickets involved, along with the people, then leave a comment — it updates the Jira ticket automatically.

1. Open the Resolve Blocker modal from the active blocker list.
2. Add the tickets involved in the resolution.
3. Add the people to notify — they receive a resolution card in their Inbox.
4. Leave a resolution comment — a "✅ Blocker resolved" comment is auto-posted on the Jira ticket.

Team View

Organize your Jira users into named teams for queue visibility sharing and collaboration.

• Create a team with any name and add members by user search (no invite step — members are added directly).
• Added members receive a "Got it" notification card in their Inbox.
• Creators can delete their team; admins and creators can manage membership.

In My Queue, set your visibility to "Shared with specific teams" and select which teams can view your queue. Managers and teammates can then see your workload without you needing to share anything manually.

Inbox

The Inbox is your central notification hub for everything happening in Handoff for Jira.

What Lands in Your Inbox

• 📥 Incoming handoffs from teammates
• 🚫 Blocker alerts where you are assigned as responsible
• ✅ Blocker-resolved notifications
• 👥 Team membership notifications

Inbox Tabs

• Received — Active incoming cards awaiting action
• Sent — Handoffs you sent and their delivery status
• Archive (History) — All past handoffs and notifications

Each Inbox card shows: sender avatar (initials), timestamp, ticket list, note, and action buttons (Accept / Decline / Archive). Unread cards display a badge count on the Inbox tab that clears when you open it.

🔧 Technical Specifications

System Requirements

• Active Jira Cloud instance (Jira Software or Jira Work Management)
• Modern web browser (Chrome, Firefox, Safari, Edge)
• Active internet connection
• Appropriate Atlassian Marketplace license

Permissions Required

• Read and write Jira work items (to fetch tickets and post ADF comments)
• Read Jira user profiles (for assignee display, team search, and @mentions)

🔐 Privacy & Security

• Data Privacy: DataPingo Privacy Policy
• Security: DataPingo Security Policy
• Data Storage: All app data is stored in Atlassian Forge KV Storage — no data is sent to or stored on external DataPingo servers
• Jira Comments: Posted only when explicitly toggled on per ticket (📣); off by default (🔇) can be set per ticket
• GDPR: Personal data reported weekly to Atlassian's Personal Data Reporting API
• Compliance: Follows Atlassian security standards and Forge platform security framework

💬 Support & Contact

For technical support, feature requests, or general questions about Handoff for Jira:

• Email: support@datapingo.com
• Response Time: 24–48 hours for technical issues
• Support Scope: App functionality, configuration, and technical issues