3 ms·
> 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. Make
by 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.