Time Labels Color(s)

[nelsonic]

At present our Time (estimation) Labels are different colors: https://github.com/dwyl/labels/labels

This makes it hard difficult to scan through a list of issues e.g: https://github.com/emfoundation/ce100-app/milestone/3 and see which ones have a time estimate label applied.

@iteles please remind us why the labels have different colors... was it to signify a "scale" e.g. darker pink is more time...?

for the record I think they should all be the same color so its easy to glance at the list of issues and see Time Estimate. or if we are going for a "range", we should first agree on what "levels" of time estimation we are going to do and then could go on http://www.color-hex.com/color/f7c6c7 and select different (but still v. similar and thus "scannable") tones of the same color for the "spectrum of effort"...

[iteles]

The thinking behind having two shades of pink for the time labels was so that tasks under half a day were easily identifiable should the person wanting to contribute have a smaller time block on their hands.

It doesn't seem to be working though, let's get it sorted. 👍

[nelsonic]

@iteles stories/issues/tasks should only be estimated when they are going to be included in the milestone (or started immediately) preferably by the people/person who is going to do the work.

If people never start working on another issue/task before estimating it again, I really don't mind what colors are used for the labels. The reason I opened this issue was because I see milestones ("sprints") with quite a few issues which are unestimated ...

[iteles]

This has been changed in this repo. Could you please check and close this issue @nelsonic ?

It should be noted that as a person who has to answer a lot of client questions on timelines, I find it incredibly useful to have a quick understanding of which tasks are 'quick' tasks (under and hour) and which ones extend into half a day plus.

I was in the situation today where when sprint planning I was able to quickly scan the backlog and pick out a couple of small but high value features quickly to add more value to the sprint (we'd estimated the next highest priority in the backlog and it was too large for the time available in the sprint so I was looking for smaller pieces). It also allows me to have a good idea at a glance of how full a sprint really is (lots of dark pinks vs lots of light pinks).

I'm happy to be outvoted on this one as it seems people find it more unhelpful than helpful, but wanted to document the above for future reference once the issue is closed.

[nelsonic]

@iteles I prefer the lighter pink.

Dark pink with black text is not great. 😕

[iteles]

Done.

[nelsonic]

I should have phrased that better... but thanks for changing them. 👍