Quick mapping for unmapped tickets
Review unmapped work, assign the right Work Type, and switch between My Work and all unmapped tickets depending on whether you are mapping your own queue or cleaning up the project view.
Automatic setup
Creates or adopts the Jira Work Type field.
Dashboard
Shows the delivery mix across teams and time.
Quick mapping
Maps unmapped tickets without leaving the flow.
Issue side panel
Views and edits Work Type directly on an issue.
Business visibility
A Jira dashboard for the work mix leaders actually discuss.
Work Type Focus translates day-to-day tickets into capacity language. Instead of asking whether the team is busy, you can see what kind of work is consuming the system.
1
See focus percentage
Compare planned value work with interruptions, complexity work, capability improvement, and experimentation.
2
Review trend, not anecdotes
Use recent sprint history to spot whether the work mix is stabilizing, drifting, or getting more expensive.
3
Filter to the conversation
Focus the dashboard by team, sprint, or time range before planning, retro, portfolio, and leadership reviews.
Daily use
Map the work where teams already live.
The app is designed for lightweight classification. Admins install it, teams use the dashboard and quick mapping views, and individual contributors can update Work Type from the Jira issue side panel.
Issue side panel editing
View or update Work Type on the issue itself. If Jira screen or workflow configuration prevents edits, the app shows a clear read-only message instead of silently failing.
Work types
Complexity becomes business language.
A useful work taxonomy should make tradeoffs easier to discuss. Work Type Focus gives product, engineering, and leadership the same words for cost, risk, value, and learning.
Unstructured Innovation / Experimentation
Discovery work where the business is buying evidence before committing.
Add New Capabilities
New customer or market value that extends the product.
Enhance Existing Capabilities
Improving what customers already use so the product performs better.
Manage Complexity
Risk reduction, maintainability, simplification, technical debt, and future optionality.
Unplanned Work / Interruptions
Demand that bypasses the plan and exposes operational pressure.
The 1-10-100 rule for delivery focus
The earlier teams classify complexity, the cheaper it is to act. A small planning signal can prevent a larger delivery tradeoff and an even larger business constraint later.
Make complexity visible while it is still a management choice, not after it becomes a customer, reliability, or roadmap problem.
Well-being and AI focus
AI increases output. Focus decides whether that output compounds.
Code generation makes it easier to ship more change. Humans still need to decide which complexity is worth carrying, which interruptions are burning the plan, and where attention should go next.
AI delivery teams
Open the AI focus page
Shipping with AI? Read the business case.
Use Work Type Focus to keep generated output connected to portfolio choices, risk reduction, and sustainable delivery health.
Get Work Type Focus for your team
Install it in Jira and turn delivery data into management signal.
Start with an admin install from the Atlassian Marketplace. Work Type Focus automatically creates or adopts the Work Type field, then teams can use the project dashboard, quick mapping, and issue side panel.