5 ms·
- it wouldn't assume that problems map 1-to-1 with solutions. A reported problem might require several things to solve, and a solution might handle multiple pr
by mcphage 8y ago
- it wouldn't assume that problems map 1-to-1 with solutions. A reported problem might require several things to solve, and a solution might handle multiple problems.
- it would make it easier to collaborate. Most issue trackers have a single person assigned to a ticket, but I would want multiple: the person working on it, the person testing it. Other people brought in to answer a single question. A person brought in to do code review. Playing pass-the-baton about who's currently assigned to the ticket is frustrating.
- it would have a more loose issue life cycle. Sometimes a ticket is in a clean state—in progress, finished, deployed. Sometimes it's not. Maybe it got deployed then reverted. Maybe it's waiting on something else. Maybe it's in branch somewhere. Most systems either offer nothing, or require you to set up a rigid set of states and transitions.
- alangibson 8y ago> Most issue trackers have a single person assigned to a ticket, but I would want multiple Totally agree here. Having a single assignee is total nonsense. Makes you wonder if the people building the tool use it. > rigid set of states and transitions I think the whole idea of a set workflow is a relic from the 90's that has little basis in reality, especially in an agile development team.
- Karunamon 8y agoI have to disagree with multiple assignees here for two reasons: - Accountability. If it’s everyone’s job, it’s nobody’s job. This is project management 101, every task needs a single person who is responsible for ensuring that task is done. - Scope. If you feel like you need multiple assignees, this can be a signal that your task is too high-level and needs broken down into smaller units of work (which will generally have one assigned). Something like Jira offers epics, stories, and any other custom issue type you can imagine for doing this.
- mcphage 8y ago> every task needs a single person who is responsible for ensuring that task is done. Indeed. But "done" means different things to different people—to the developer, to QA, to deploy engineers, to devops, to the stakeholder. And more goes into a ticket than done/not done, that needs other people to chime in.
- cimmanom 8y agoWe just add fields to the ticket in Jira to track those various responsibilities and use a hook to auto-update them as part of status transitions.