Background & Objectives
Atlassian JIRA is really just a ticketing system at heart. While there are a number of agile-ish workflows and plugins available to the system, the fundamental design of the tool is to enforce assignment of tickets to individuals rather than groups.
From an agile perspective (and specifically from a SAFe 4.5 perspective), I would much rather see issues assigned to affinity groups than individuals. Actually, I’d rather see them assigned to product queues rather than teams, but that may be a step too far for the tool.
Atlassian offers several kludges for trying to work around this issue, but they all feel a bit...well, suboptimal. Even the “Unassigned” queue or the custom group picker option seem to require bypassing a large number of built-in reporting and tracking capabilities of JIRA, and I don’t want to recommend a workaround that results in reduced value from other standard features of the tool.
How can I most effectively use JIRA to communicate the values of collective team ownership, pairing, and swarming within JIRA without making it impossible to use the standard dashboards and reports?
- Tool selection was a business decision above my pay grade. I can’t enforce CodeGnome’s Law or First Corollary, and have to do my best to work within the tool’s constraints.
- I’m really looking for a process answer, but workflows, practices, JIRA plugins, or custom reporting are certainly within scope.
- I want to be crystal clear that I’m looking for a framework-centric solution that takes the tool limitations into account, rather than seeking software recommendations.