Context gets lost in the handoffs between teams. (Sketch was founded largely to address this problem.) A support ticket gets escalated to engineering without the error logs. A product idea gets approved but the development team never sees the business case. The receiving team starts from scratch because nobody carried the details over.
These breakdowns add up. Atlassian’s State of Teams 2024 report found that Fortune 500 companies alone lose 25 billion work hours every year to ineffective collaboration. Part of the problem is that more than half of all knowledge workers reported working on projects only to discover another team was already doing the same thing.
Automated work routing in Jira solves this by creating tickets in the right space, for the right team, with the right context attached. No copy-paste. No Slack messages asking for details. In this post, we walk through two methods: one using Jira automation, and one using Jira Product Discovery (JPD). You can also see both demonstrated step by step in this video:
Method 1: Jira automation for cross-team routing
This approach uses Jira’s built-in automation engine to create a new work item in a different project when a ticket transitions to a specific status. It works well for any scenario where work originates in one space and needs to be delivered by a team working in another.
How it works
In the demo, we start with an intake item in a shared request space. When we transition the item to “Accepted,” a transition screen appears with a custom field called “Route to team.” This field lets the person accepting the request choose which team should handle the work.
Once the transition completes, automation takes over. It creates a new work item in the destination team’s project and links it back to the original intake item with an “implements / is implemented by” relationship.
How context is preserved
This is the part that matters most. The original intake item may have custom fields filled in by the requester, such as business impact, problem statement, or priority level. Rather than adding those same custom fields to the delivery team’s screens (which clutters their view), automation copies the values into a formatted table in the new ticket’s description field.
The table is collapsible. The delivery team can expand it when they need context and collapse it when they don’t. This keeps the delivery ticket clean while making sure nothing is lost in the handoff.
What you can customize
The specifics of this process are flexible. The trigger status can be anything in your workflow: “Accepted,” “Escalated,” “Support needed,” or any status that represents work being handed off. The routing field can include as many teams as you need. And the field mapping in the automation rule determines exactly which values get carried over to the new ticket.
Method 2: Jira Product Discovery for idea-to-delivery routing
If your team uses Jira Product Discovery for ideation and prioritization, you already have built-in routing features. That means no new automation rules are necessary.
Creating delivery items from ideas
In JPD, each idea has a Delivery tab. From there, you can either link to an existing Jira work item or create a new one. When creating a new item, you select the destination project and issue type. JPD auto-populates the summary from the idea title.
The key feature here is the checkbox: “Embed the idea description and fields into the work item.” When checked, JPD copies the idea’s description and all pinned fields into the new Jira ticket’s description. All formatting is preserved, including info panels, emojis, and structured content. The pinned fields (such as status, impact, and problem statement) appear as a formatted block in the ticket.
Tracking delivery progress from JPD
Once a delivery item is linked, JPD provides visibility into its progress directly from the idea. You can see the status category of the linked work item, and if it has subtasks, JPD shows a progress bar tracking how many are in To Do, In Progress, or Done.
In the JPD list view, you can add delivery-related fields as columns. The delivery status field shows a count of linked items by status category. The progress bar column gives you a quick visual of how far along each idea’s implementation is. You can also link additional delivery items or create new ones directly from the list view.
Use cases beyond intake and ideation
Both methods apply to more than just product intake. This demo highlights three additional scenarios where cross-team routing is useful:
- Cross-team work handoff. Work originates with a product, support, or operations team and needs to move to platform or engineering. Automation creates the delivery ticket in the right space and links it back to the original request.
- Support escalation to engineering. A customer support ticket needs engineering attention. Instead of manually creating a new ticket and copying details, automation handles the transfer and preserves the customer context, error details, and SLA information.
-
Compliance and legal review. A ticket in a security or compliance space needs input from legal. Automation routes a linked ticket to the legal team’s project, keeping both tickets connected for audit trail purposes.
Which method should you use?
If your team already uses JPD for product discovery and ideation, the second method is low-hanging fruit. It requires no setup and provides built-in delivery tracking. If you don't have JPD, or if your routing needs go beyond idea-to-delivery (such as support escalation or compliance handoffs), use the first method with Jira automation.
Both methods accomplish the same core goal: getting work to the right team with the right context, without manual copying or cluttered ticket screens.
Getting started
Before setting up either method, make sure you have Jira admin permissions for the projects involved and a clear understanding of your team structure and workflows. If you need help with Atlassian configuration basics, Sketch offers training across the full Atlassian tool set.
Start with a single use case. Pick the handoff that causes the most friction today, configure it, and test with a few sample tickets before expanding to other teams. Document your routing logic and field mappings so the setup is easy to maintain and scale.
Need help configuring Jira workflows?
As an Atlassian Solutions Partner, Sketch configures solutions like this for enterprises every day. Our 100% US-based team can design and implement custom routing, automation, and cross-team workflows for your organization. We're happy to prove it, too, which is why we offer free consultations.
Schedule a free Jira workflow assessment or just drop me a note. The team and I are happy to talk shop.
Atlassian