Heidi's dashboard

Heidi reported a problem in Pivotal Labs on March 13, 2008 22:00:

Application Error when making changes

Application error happened and it rolled back some changes.

1. Entered a bug and saved it.
2. Deleted the bug.
3. Got this error message: An application error has occured. Some of your changes have been rolled back.
4. Then my bug re-appeared in the icebox.
5. Then I deleted it again and it was gone.

PS - occurred is misspelled in your error message. It should have 2 cs and 2 rs.

PSS - we have also seen this error occur when adding a comment and saving, entering a new story and saving, we think it has to do with any type of edits.

Heidi reported a problem in Pivotal Labs on February 20, 2008 23:19:

Another deadlock - 3:18pm

Jon just got a deadlock when he was trying to accept a story. Looks like his story did get accepted.

BTW I know you guys are working on these so thanks!

Heidi replied on February 20, 2008 21:45 to the question "When you click Done, load past sprints in "closed" view" in Pivotal Labs:

Hi - I never noticed the collapse all. Thanks for pointing that out.

I'm not sure if it is working properly. It doesn't collapse all for me. Many of the sprints show two stories and the ones at the bottom are open. (I expanded all and collapsed all a few times)

Heidi replied on February 20, 2008 17:49 to the problem "Inodb - Index range exclusive lock issue" in Pivotal Labs:

Great. Thanks.

Heidi reported a problem in Pivotal Labs on February 20, 2008 01:20:

ThreadManager caught an exception

Hi. 3 of us just got the below threadManager exception. We weren't doing anything in tracker. The message just popped up. However, Jon was entering a new story at the same time.

ThreadManager caught exception in thread Flash.update():TypeError:_586 has no properties

Heidi reported a problem in Pivotal Labs on February 20, 2008 01:17:

Inodb - Index range exclusive lock issue

We saw an error message with a MYSQL deadlock moments ago. Maybe your Inodb configuration needs tweaking.

In your app, should the transaction duration and index lock range be reduced?

This is a mysql performance blog with inodb index stuff in it:
http://www.mysqlperformanceblog.com/

I have a screenshot of the deadlock error message we saw but I"m not sure if it is useful to send or not.

Heidi asked a question in Pivotal Labs on February 20, 2008 00:01:

When you click Done, load past sprints in "closed" view

0. Start Tracker
1. Click on Done
2. Currently I see sprints 1-18 in closed state.
3. Sprints 19-21 are open.
Is there a reason for that? Why aren't they all just closed by default?

Heidi replied on February 19, 2008 18:40 to the problem "When clicking on a story link from an email, dont open new window if there is an existing tracker window open" in Pivotal Labs:

Thanks Mark that makes sense.

Heidi reported a problem in Pivotal Labs on February 19, 2008 05:32:

Deadlock: was creating new story as chore

9:30PMish
1. 3 panes open
2. Filled out form to create a new chore and clicked to submit that.
3. Was waiting for it to show up at top of icebox.
4. Got deadlock error.
Error: Mysql::Error: Deadlock found when trying to get lock; try restarting transaction: UPDATE project......etc...some of your changes have been rolled back.
5. After clicking ok on that error i noticed that my chore was entered twice. I don't think I did that twice but i'm not sure.
6. Strange. I moved one of the stories to the icebox. I tried to delete the remaining one in the icebox. That deleted the one in the backlog. Now I have the remaining chore in the icebox and it is white, and not blue like the rest of the icebox.

Heidi reported a problem in Pivotal Labs on February 18, 2008 22:16:

When clicking on a story link from an email, dont open new window if there is an existing tracker window open

1. Have no tracker windows open in your browser.
2. Click on link to tracker story in email. Wait and let the story load in your browser.
3. Go back to email and click on link again.
4. It opens a new tracker tab in firefox open to the story.
5. Edit the story in the 2nd window and save it. Now go back to the story in the 1st window. You get the error "another user made a change to a story you were editing. Any changes you may have made since your last save have been lost. I wasn't editing the story in the first window though.
6. I think the performance also degrades with multiple tracker windows open in firefox.
7. This isn't a huge deal but I thought I'd report it anyway.

Heidi reported a problem in Pivotal Labs on February 15, 2008 22:40:

Improve indication that internet connection isn't working

Last night Jon spent a lot of time "accepting" stories to only discover that his internet connection wasn't working properly and the changes weren't saved by tracker. (and he looked in the history and his changes weren't in their either).

Maybe the visual indication that the connection is lost or unstable - whatever is in the upper right corner - could be made a bit more prominent?

Heidi replied on February 14, 2008 17:27 to the problem "Deadlock -one user was moving stories. the other was editing an unrelated story" in Pivotal Labs:

Thanks for being so responsive to this! We really appreciate it. -Heidi

Heidi shared an idea in Pivotal Labs on February 13, 2008 18:01:

Display sprint start AND end dates in sprint markers

-The sprint markers show you the Start date of the sprint. If you mouse over that, you can see the start and end dates of the sprint.

-We use those sprint markers to help us see when our supposed "end" date is going to be for our release however we have misinterpreted the date that is shown. Its easy to think that it is the end date. We look at that date to see the impact of the stories we've added to the predicted end date of our release.

-I think it would be clearer for users if the start and end date are shown in a short form, maybe like this: Apr 15-28. That would only be 3 more characters so it shouldn't clutter up the UI and then no one could misinterpret the date. Just an idea for your consideration.

Heidi shared an idea in Pivotal Labs on February 13, 2008 17:54:

Calculation used to mark sprint start-end in backlog should include rate of adding features to backlog

1. We have our backlog filled up with the stories we must do for our next release. Those stories are estimated.
2. We like how tracker uses our velocity to try to predict when we will be "done" and how much work should go into each future sprint.
3. However, we just realized that the calculation used by tracker doesn't take into account the rate at which we are adding new stories to that backlog.
4. It would be a more realistic projection if that was considered.

Heidi reported a problem in Pivotal Labs on February 13, 2008 17:49:

Deadlock -one user was moving stories. the other was editing an unrelated story

1. I was moving a series of stories from the backlog to the icebox and then back to the backlog again. (that is how I move stories up or down in a column)
2. Jennifer was editing an unrelated story.
3. A deadlock was shown on her screen. Then she got an error that someone else was editing the same story that she was editing. But that was not true. No one was editing her story.

Do you have enough logs or whatever to diagnose problems like this? Let me know if you need more information.

Heidi shared an idea in Pivotal Labs on February 08, 2008 21:53:

Show user progress indicator after clicking on story link in an email

1. Send yourself a link to a tracker story via email (cut and paste the URL from the bottom of the story)
2. When you get the email, click on the link.
3. It opens a browser page and shows tracker but you have no indication that tracker is working to open the particular story.

-You might show the user a message, change the cursor or show a spinner so the user knows that tracker is doing something.
-it takes a long time for tracker to bring up the stories

Heidi replied on January 30, 2008 18:48 to the problem "500 Internal Server Error" in Pivotal Labs:

Cool. Thanks Mark.

Heidi reported a problem in Pivotal Labs on January 30, 2008 18:18:

500 Internal Server Error

I just got a 500 internal server error when trying to change the name of a story.

Status: 500 Internal Server Error Content-Type: text/html
Application error (Apache)

Heidi replied on January 30, 2008 14:26 to the idea "Always take me to my project on login, never land me on the dashboard" in Pivotal Labs:

When I log in I always go to my project and never go to the dashboard. I like going directly to my project. (Maybe I shouldn't be telling you this?)

Heidi replied on January 30, 2008 14:23 to the idea "I would like to be able to set the starting iteration number" in Pivotal Labs:

I like this idea. Also, if you are starting a new product release it would be nice to start from 1 instead of 265!