3 ms·
It is definitely a collaboration problem; someone created the ticket with the intention of the team doing it at some point. My question is how to deal with it b
by ironmagma 3y ago
It is definitely a collaboration problem; someone created the ticket with the intention of the team doing it at some point. My question is how to deal with it beyond just ignoring the problem.
- codingdave 3y agoSounds like you may not have a shared understanding of why tickets are created. On the teams I've worked, a ticket is simply an idea - maybe we'll do it, maybe we won't. We toss the ticket up to discuss it, which results in sometimes doing it, sometimes backlogging it, and sometimes just closing it because it is a duplicate of another ticket, is handled via another ticket, or is simply something that will never be done.
- ironmagma 3y agoYeah, I find that conception a bit silly. Ideas are ideas. If you go to the trouble of making a ticket, it means you think it’s good enough of an idea to pitch to the team. If most of the tickets are closed, that’s not okay. It means the team isn’t very good at creating tickets, or whoever is in charge isn’t allowing the team to do most of the valuable work.