search

coderly / process

The Coderly team's process documentation.
4 stars 1 forks source link

When does a task get checked off? #58

Closed joshsmith closed 8 years ago

joshsmith commented 9 years ago

The process right now indicates that something can have its label changed to merged. But when does the task get checked off? Who checks it off?

begedin commented 9 years ago

It might be useful to check them off at the end of a sprint. That way, we have an overview of what's done. Just an idea.

venkatd commented 9 years ago

Yeah I agree. When a task disappears for a sprint I think it's no good to hide it since it's out of sight and out of mind.

joshsmith commented 9 years ago

Just to play devil's advocate here, everything seems much more cluttered when completed tasks aren't marked as completed.

If we want an overview of what's done, you can look at the following:

screen shot 2015-03-23 at 11 05 46 am

venkatd commented 9 years ago

What if it they were completed at the end of the day?

joshsmith commented 9 years ago

A task that's merged is no longer actionable except by marking it complete. I'm fine with user stories staying unchecked since that's a good high-level overview, but we're going to have a lot of detritus in there if we don't check off the broken down tasks.

venkatd commented 9 years ago

Ok I'm fine with it. Let us see if there's an issue with it and revisit if checking off becomes a problem.

joshsmith commented 9 years ago

Completed by whom at the end of whose day? If we're async and spread across timezones, that seems problematic.

venkatd commented 9 years ago

Nvm about that comment. I'm on board with just checking off right away.

joshsmith commented 9 years ago

I guess then the question is really: what benefit does the merged label have if we're checking it off immediately?