Ticket := (title, description, time, tags, links, *Comment)
Comment := (name, time, text)
…and everything else is culture or auxiliary tooling. It’s a schema as old as Web 2.0 and it works because most people just want to talk to each other and search for stuff they think or know is there.
100% of the time I just want to announce either what I want to do, or comment on something that’s in progress. The communication and progress tracking are the most important things for keeping me and my team aligned.
What does Jira get wrong? Bureaucracy. Modern day online triplicate form filling disguised as “agile” is still pen pushing.
Pro-forma for bugs is friction — I should be able to file a bug without having to think about how to categorise it. Have another tool / view for nagging me about that, not the create-bug workflow.
Epics / stories / tasks / sprints / bugs: what if I make a task when I wanted a bug? What if made a spike that’s really a task? Why does this matter so much at the top level of the “task” entity — it should just be a tag on a task and nothing more fundamental than that. Let me modify the structure of my task tree myself.
Clutter, of course. Jira has 15 fields of stuff per issue that could just all be tags once we’ve spent the first week shaking out what kind of patterns are appearing in our own team’s workflow.
Projects: why is it a three stage process to move an issue between projects, and why should the issue id change when it moves? What if a piece of work is small but spans two projects? Tagging not taxonomy please.
Jira feels like it was designed for contributors and teams with zero discipline. Tech teams with any kind of serious hiring bar and leadership structure should have zero problem with trusting their staff with being succinct and meaningful with communication, including with how they track tasks. If you need Jira to enforce this, then I feel sorry for you as I pass you by to join a different team who know how to and want to work together without form filling.
Comment := (name, time, text)
…and everything else is culture or auxiliary tooling. It’s a schema as old as Web 2.0 and it works because most people just want to talk to each other and search for stuff they think or know is there.
100% of the time I just want to announce either what I want to do, or comment on something that’s in progress. The communication and progress tracking are the most important things for keeping me and my team aligned.
What does Jira get wrong? Bureaucracy. Modern day online triplicate form filling disguised as “agile” is still pen pushing.
Pro-forma for bugs is friction — I should be able to file a bug without having to think about how to categorise it. Have another tool / view for nagging me about that, not the create-bug workflow.
Epics / stories / tasks / sprints / bugs: what if I make a task when I wanted a bug? What if made a spike that’s really a task? Why does this matter so much at the top level of the “task” entity — it should just be a tag on a task and nothing more fundamental than that. Let me modify the structure of my task tree myself.
Clutter, of course. Jira has 15 fields of stuff per issue that could just all be tags once we’ve spent the first week shaking out what kind of patterns are appearing in our own team’s workflow.
Projects: why is it a three stage process to move an issue between projects, and why should the issue id change when it moves? What if a piece of work is small but spans two projects? Tagging not taxonomy please.
Jira feels like it was designed for contributors and teams with zero discipline. Tech teams with any kind of serious hiring bar and leadership structure should have zero problem with trusting their staff with being succinct and meaningful with communication, including with how they track tasks. If you need Jira to enforce this, then I feel sorry for you as I pass you by to join a different team who know how to and want to work together without form filling.