EvilPuppetMaster's dashboard

I'm with Scott. Notifying everyone is much too scattershot. I still think a free text field (with autocomplete) would be the best solution. Checkboxes sound a bit clunky.

Hey again,

So you changed this and then you changed it back again. Was JLM the only opinion you used to make this decision? It seems there are a lot more voices in favour than against in this thread. But ultimately it seems it would be best as a preference of some kind.

JLM, fair enough if that is how you like to use the labels, you are lucky to have stories that can be so neatly packaged up into single groups.

In most projects stories aren't really that easy to categorise, and the whole beauty of being able to add labels is that you can add as many as you like and combine labels in order to make groups most appropriate to whatever your task at the time requires.

For example, we use labels not just to group stories into larger features, but also to track statuses that pivotal doesn't support (eg. marking a story as 'blocked'), and into the areas of the team which will have to deal with them (middleware, frontend, design etc).

You can then create a custom search combining labels in order to see a list of stories that are 'blocked' for the 'middleware' team for example.

But what this means is that we end up with stories that have long lists of labels and with the labels on the left, it really does gets very cluttered.

You would probably say 'well just be more disciplined and use one label only', and this is what the pivotal 'best practice' seems to be in their help docs. However I would argue this is missing the whole point and flexibility of what labels can actually be used for. You may as well just have single categories.

BTW if you need to see a list of stories that have a particular label, such as your 'facebook' stories you can just click the label. So is not having the labels on the left really that much of a loss?

Anyway Pivotal, make it an option please!

Cheers
Tom

This seems to be a common issue for me as well.

The offline thing will just flash up, quite frequently. Usually refreshing the page makes it go away, so obviously I'm not ACTUALLY offline.

THanks very much!

Some more info, it turns out this is because the task had a % character in it. Once I remove the %, I can save.

Interestingly, getSatisfaction added that closing wbr tag for me! – EvilPuppetMaster, on August 13, 2009 04:19

This wouldn't be such an annoyance except that it seems to automatically add in <wbr> tags for you in some cases, which when you edit the task become visible and then in turn get html encoded.</wbr>

The problem for me is less the small alignment issue you point out, but rather the fact that the labels cause the alignment of the main story title to be all over the place.

The main title is unarguably more important than the labels.

I can't figure out why Pivotal chose to do it that way.

Thanks for replying Mike.

Yep that is a good suggestion. I will use labels for now.

I still think a special status that made the story highlighted red would be useful, you need that info really in your face, a label can be glossed over pretty easily. You would have to intentionally go searching for blocked stories to really find them, they won't stand out in a long list.

I have already become pretty practiced at ignoring the labels, since they bump the alignment of the heading out, you have to sort of develop a blind spot for them.