pixelperfect's dashboard

pixelperfect replied on March 10, 2010 22:49 to the praise "I *heart* Pivotal Tracker!" in Pivotal Labs:

I think you want some of these

A comment on the problem "Bugs should be caterpillars" in Pivotal Labs:

I like this idea – pixelperfect, on March 09, 2010 18:59

pixelperfect marked one of Stacy Maddocks Cronin's replies in Pivotal Labs as useful. Stacy Maddocks Cronin replied to the problem "Bugs should be caterpillars".

pixelperfect replied on March 09, 2010 17:28 to the idea "Add a 'Blocked' status" in Pivotal Labs:

It sounds like some people need states that other people wouldn't want (I don't think I would enjoy a "blocked" state, but I can see why some do).

+1 for custom states

pixelperfect replied on March 08, 2010 23:42 to the idea "Add a 'Blocked' status" in Pivotal Labs:

To preface this request, my stories are a little bigger and more nebulous than typical tracker stories since I'm doing design instead of development.


I often find that I have a lot of progress on a story but then priorities change and I need to set it aside for a while. It's "started" but not really in progress, it's effectively "paused"


It would be very nice to have the differentiation between not-yet-started and started-but-not-in-progress

This reply was created from a merged topic originally titled
pause a started story.

pixelperfect replied on March 08, 2010 22:58 to the idea "iphone version" in Pivotal Labs:

for the first version all I want to do is add stories and read what's in the backlog

This reply was created from a merged topic originally titled
I still want an iPhone app.

pixelperfect marked one of Jan Nelson's replies in Pivotal Labs as useful. Jan Nelson replied to the idea "more acceptance states to support testing on multiple environments".

pixelperfect replied on February 17, 2010 19:57 to the question "Moving multiple stories at once within a release" in Pivotal Labs:

just thought I would add this request while we are dragging 50 stories that just got imported one-by-one

This reply was created from a merged topic originally titled
move selected stories to release.

A comment on the idea "more acceptance states to support testing on multiple environments" in Pivotal Labs:

I would have made the next post a comment, but i can't upload an image. Thanks for adding activity to this topic... I really want this workflow feature so that we can have clearer communication on our team. – pixelperfect, on February 17, 2010 19:10

pixelperfect replied on February 17, 2010 19:09 to the idea "more acceptance states to support testing on multiple environments" in Pivotal Labs:

@nathan s

just because I need to think of everything visually... are suggesting that you want this:

pixelperfect replied on February 12, 2010 20:17 to the idea "more acceptance states to support testing on multiple environments" in Pivotal Labs:

yes! great suggestion!

pixelperfect replied on February 12, 2010 19:50 to the idea "more acceptance states to support testing on multiple environments" in Pivotal Labs:

May i suggest an incremental approach to custom workflows where it's possible to turn on these extra steps that we've requested.

And if I can suggest the ui design, you wouldn't even need different buttons ... just a letter by the accept | reject buttons like this:


This would save us a ton of hassle and time and make our customer feel so much better about the "what's going on, and what's actually delivered to users??" question.

Thanks for responding!!

pixelperfect replied on February 12, 2010 19:32 to the problem "scroll bar getting reset after viewing a description bubble" in Pivotal Labs:

ok -- so we'll use firefox for reading stories and chrome for moving stories and hope that firefox gets faster and chrome gets less weird. and really hope that it doesn't go the opposite way for either browser.

...I found a workaround
the scroll bar doesn't disappear if the panel is wider than the bubble, so hiding some panels and/or widening the browser window alleviates the problem.

pixelperfect shared an idea in Pivotal Labs on February 11, 2010 00:29:

more acceptance states to support testing on multiple environments

we are feeling frustrated by a lack of communication because tracker lacks a few states that are integral to our workflow. We need to be able to communicate when something has been accepted on our demo server, on staging and finally on production.

- not yet started
- started
- finished
- delivered
- accepted (on demo)
- rejected (on demo)
- accepted (on staging)
- rejected (on staging)
- accepted (on production)
- rejected (on production)

pixelperfect reported a problem in Pivotal Labs on February 11, 2010 00:11:

scroll bar getting reset after viewing a description bubble

unexpected scrolling to the top of the backlog after hovering over a description

steps to reproduce: (steps recorded using chrome 4.0.249.49 on a mac)
1. open a tracker project with a substantial number of stories in the backlog... enough that you have a scrollbar.
2. scroll half way down the backlog (in my case I combine the current and the backlog in the same panel)
3. hover over a description bubble
4. un-hover and use the scroll wheel on the mouse to scroll down more

expected:
that you will scroll down more when you use the scroll wheel on the mouse

actual:
scroll bar is reset and you end up at the top of the panel (your place is lost)

there are no workarounds to this, it also happens when you click on the scroll bar instead of using the scroll wheel.

pixelperfect replied on January 19, 2010 23:48 to the question "when you merge a topic, do users following that topic automatically start following the new topic?" in Get Satisfaction:

thanks for the reply

pixelperfect replied on January 19, 2010 10:11 to the question "when you merge a topic, do users following that topic automatically start following the new topic?" in Get Satisfaction:

I guess I find it a little insulting/annoying that my version of the topic gets deleted and I am automatically subscribed to get email notifications about the canonical topic. To be honest, I care more about people responding to me than the actual problem, especially if it was minor and has been solved and people are just sort of chatting (but I'm no longer part of the thread).

I can see why you guys designed this the way you did, to eliminate clutter, but why delete people's content, why not append it all together.

I think the part that gets me the most is the phrase "you have this problem too" indicating that I clicked a button that I didn't. Maybe just add some more context to that, letting me know that my topic was rolled into the canonical topic and then explain how the canonical topic is picked (first, most popular, best information... etc. ?)