📋 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, and a team management view — all without leaving Jira or switching to external tools.

💡 No context switching: Everything lives inside Jira. No Slack threads, no spreadsheets, no DMs. Handoffs and queue updates post rich ADF comments so the history lives on the ticket.
📋

My Queue

Personal priority-ordered ticket list. Drag to reorder. Add any Jira ticket via the search bar.

Handoff

Notify teammates which tickets to focus on — send up to 10 tickets with a note and optional Jira comments.

👥

Team View

Create named teams, add members, and see all team members' queues side by side.

∞
Tickets per personal queue
10
Tickets per handoff
0
External servers — data stays in Atlassian

📘 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.
💡 Adding tickets to your queue: The quickest way is to use the search bar at the top of My Queue — search by key or keyword and add any ticket in one click. You can also add from a Jira issue directly: open the issue actions menu (•••) and click “Add to My Queue in Handoff”.
Add to My Queue in Handoff — issue action menu

My Queue

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

  • Issue Key — Clickable link that opens the Jira ticket
  • Summary — The ticket name/title
  • 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
💡 Drag to reprioritize: Drag and drop any ticket row to reorder your queue. Your order is saved instantly.
My Queue — personal ticket list inside Jira

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. Search any Jira ticket or select from your queue — queue matches appear first.
  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 notification in their My Queue.
Handoff tab — inline form to search tickets, pick recipients and add a note

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.
💡 Audit trail: Every accepted handoff posts a rich ADF comment (with @mentions and hyperlinks) directly on the Jira ticket — so the handoff history lives on the ticket, not in a chat tool.
Handoff comment posted on Jira ticket

Team View

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

  • Create a team with any name and add members by user search (no invite step — members are added directly).
  • Added members receive a notification in their My Queue.
  • Creators can delete their team; admins and creators can manage membership.
Team View — see teammates' queues and manage teams

🔧 Technical Specifications

Detail Value
Platform Atlassian Forge (Cloud only)
Product Jira Software & Jira Work Management
Installation Atlassian Marketplace
Licensing Paid — Marketplace Licensing
Queue Limit Unlimited
Handoff Limit 10 tickets per handoff
Data Storage Forge KV Storage — no external servers, data stays in Atlassian cloud
Jira Permissions Read & write Jira work items; read Jira user profiles
Jira Comments Rich ADF format with @mentions and hyperlinks
GDPR Personal data reported weekly to Atlassian's Personal Data Reporting API
Current Version 3.3
Last Updated May 2026

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)
⚠️ Cloud only: Handoff for Jira is built on Atlassian Forge and runs exclusively on Jira Cloud. Jira Server and Jira Data Center are not supported.

🔐 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
📚

Documentation

Browse docs for all DataPingo products

Browse Docs →
🎫

Support Portal

Submit tickets and track issues

Open Ticket →
💼

Atlassian Community

Join discussions with other Jira users

Visit Community →