I've just joined a team who haven't refined their backlog in a long time and as such there's a whole bunch of tickets which are no longer relevant. Some don't need to be completed at all anymore, some are minor bugs or performance issues that haven't been raised at all since being created and some are things that have actually been done but not by us.
My question is what is the best way to deal with these tickets? I'm reluctant to mark them as done because they haven't actually been done by us and I don't want to delete them in case they get raised again and we lose the information contained on them that might be useful. My other idea was to create another sprint but not start it and stick them all in there but that doesn't feel quite right. Is there an alternative way to deal with them?
Hi Thomas,
When I've had something similar in the past, I closed them as "Won't Do". Then they are at the end of the workflow and not in your sprints, while at the same time, you can easily see the Resolution is "Won't Do", so they are not actually implemented.
Hope it helps,
Carolyn
I agree with @carolyn french this way you can track issues that also fall into these categories.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Happy to help! Best profile pic ever @Thomas Hind
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.