Chris's dashboard

Chris replied on February 03, 2010 16:37 to the question "What happens to an existing project if you change point systems?" in Pivotal Labs:

Thanks Mark. Is there a way to then automate mapping that scale to something else? e.g. if we want all our 1's to become 2's and our 2's to become 4's, etc.? Probably just need to write a script and use the API?

Chris asked a question in Pivotal Labs on February 03, 2010 03:53:

What happens to an existing project if you change point systems?

I'm interested in changing point systems. We currently use linear (1/2/3) and are interested in switching to power of two. If we do, what happens to completed, in-progress, and not-yet-started stories?

Chris replied on January 23, 2010 00:38 to the question "What are the point scales available besides Fibonaci?" in Pivotal Labs:

Now that we can change our existing point scale to a new one, what happens to done stories, in progress stories, and upcoming stories? e.g. we're using the linear point scale right now, but are interested in switching to Powers of Two, and I'm curious what happens (especially since for example Linear has a "3" point, but PoT does not.

A comment on the question "How can I see individual member velocity?" in Pivotal Labs:

Right, just want to see what a particular developer is doing in points each week. There are multiple reasons. Anyway, ya, I couldn't find a way either, and just did that (looked in Done, and tallied each week's up). – Chris, on January 21, 2010 20:34

A comment on the question "How can I see individual member velocity?" in Pivotal Labs:

For us it doesn't work that way. Generally speaking only one person works on a particular story. We are a small company, and don't have many different people doing different parts of each feature, etc., so for us, it is pretty much a one to one relationship (developer to Tracker story). – Chris, on January 20, 2010 23:12

Chris asked a question in Pivotal Labs on January 19, 2010 09:18:

How can I see individual member velocity?

Is there a way to see what the velocity of each team member, or a particular team member is for each iteration, and/or on average? I'd like to be able to look at how each member's velocity changes over time and so on.

Chris replied on January 08, 2010 16:54 to the idea "Delete or compress comments" in Pivotal Labs:

I would really like to see the "compress" notion. We sometimes get stories that have tons of comments (think 5 screens of scrolling worth). On stories this active with comments, it gets to be a pain to open up the story, and scroll down. I'd love to see a feature where say if a tory had more than 10 comments, that all but maybe the last 2-3 comments were in a disclosure box, and closed/hidden by default (but clicking the disclosure triangle obviously would then reveal them). This would be a true improvement on user experience.

Chris started following the idea "Delete or compress comments" in Pivotal Labs.

Chris started following the idea "Edit comments on stories" in Pivotal Labs.

Chris replied on January 06, 2010 21:29 to the question "Mass stories changed from accepted to finished, and all comments emailed again" in Pivotal Labs:

Thank you so very much! It looks cleaned up. I haven't gone back to see if they all got put in the right iterations (I don't really have a good way to tell), so it's probably fine. Velocity looks about right, so I think we're good. Thanks again, much appreciated.

Chris replied on January 06, 2010 16:48 to the question "Mass stories changed from accepted to finished, and all comments emailed again" in Pivotal Labs:

Sure, that'd be great, please do run it. Thanks!

Chris replied on January 05, 2010 21:44 to the question "Mass stories changed from accepted to finished, and all comments emailed again" in Pivotal Labs:

Mark, that'd be great, is that something you can do fairly soon? Is it a script I can then run using my API token or something? e.g. we aren't 100% sure this will not happen again, so it might be good to have on hand.

Chris replied on January 05, 2010 21:22 to the question "Mass stories changed from accepted to finished, and all comments emailed again" in Pivotal Labs:

Mark, would your script be able to move the affected stories back to their prior iteration that they had been accepted in? This has kinda hosed things in terms of prior points, velocity, and so on.

Chris replied on January 05, 2010 05:22 to the question "Mass stories changed from accepted to finished, and all comments emailed again" in Pivotal Labs:

We do use the GitHub post receive hook, and in fact, I wrote the Tracker-Github post receive hook server that we're running. However, this hasn't been touched for quite some time, so it's unclear why this would happen, and why it'd continue to happen. But, you're right, it appears to be triggered by a commit. I'll look into it on my end, thanks.

Chris replied on January 05, 2010 03:54 to the question "Mass stories changed from accepted to finished, and all comments emailed again" in Pivotal Labs:

I have now seen the following error twice, and wonder if it's related:

Error executing a stale command: TypeError: Result of expression 'this._story' [null] is not an object. (queue contents are: [])
Please click 'OK' to reload Tracker.

Upon clicking OK to this, Tracker sent all the same emails as before again (so, about 50 stories times one email per comment per story). Thus, clearly seems connected.

Chris asked a question in Pivotal Labs on January 05, 2010 01:30:

Mass stories changed from accepted to finished, and all comments emailed again

At around 4:30pm pacific time today (4 Jan 2010), we got 100+ emails about comments on stories. These all appear to be on old stories (I believe all of them were accepted already), and I now see that they're back in my Current and set to Finished. 50+ stories, and there were often multiple emails per story. From what I can tell, I got an email for each comment that exists on a story.

We have no idea how this happened or what could do that. I'm left wondering if something went wrong with Tracker, or how this could happen. This is for project 559 (DealBase).