Heidi's dashboard

Heidi replied on January 30, 2008 14:18 to the idea "I would like current and backlog columns merged into one" in Pivotal Labs:

I like having current and backlog in two columns.

Current uses your velocity to predict how much stuff you can get done in the current sprint. Anything else bubbles over to the backlog.

I think having them separate is a more obvious reminder of your velocity. If they were in one column they would just blend together.

And I like it when we get ahead of our velocity and work from the next column!

Heidi replied on January 30, 2008 14:06 to the problem "Exception in thread flash update" in Pivotal Labs:

Hi - I haven't seen this since I reported it.

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

Exception in thread flash update

Thurs 1/24 1:16PMish

I have 3 panels/columns open. one story is open in the icebox. I got this error:

The page at http://www.pivotaltracker.com says:

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

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

Arrows to collapse/expand sprint content aren't working consistently

I have a backlog with about 5 sprints in it. I like to collapse all of the sprints so I can see the total number of points in each sprint. I sum that up and keep track of how our points go up and down.

Anyway, I keep running into the issue of having the sprint open or in "expanded" state, but the arrow is showing as if the section is "collapsed".

I will send a screenshot.

Heidi replied on January 24, 2008 17:49 to the problem "Error: Mysql::Error: Deadlock" in Pivotal Labs:

Hello, I just got another deadlock.
Date: 1/24/08
Time: 9:41AM

Three of us were actively using tracker. Two of us were moving stories between the icebox and the backlog. The other person was editing a story.

I'll email the screenshot.

Heidi replied on January 23, 2008 15:07 to the idea "Add ability to "hide" top 1.5 inches of tracker window" in Pivotal Labs:

It's not a super high priority in my opinion but I thought I would report it anyway. You might have a "full screen" view at the story level that lets you edit the story easier. (IE click on a link or something from near the story that expands it to cover the whole screen?)

Heidi replied on January 23, 2008 15:02 to the problem "Error: Mysql::Error: Deadlock" in Pivotal Labs:

Thanks. It happened yesterday 1/22. I took the screenshot at 3:31pm.

Heidi replied on January 23, 2008 14:58 to the problem "When you enter a new story, you lose your place in the Backlog" in Pivotal Labs:

Thanks!!

Heidi reported a problem in Pivotal Labs on January 22, 2008 00:35:

When you enter a new story, you lose your place in the Backlog

1. Open the backlog and scroll down midway, for example. (the icebox should be closed and not visible)
2. Now click on New story
3. Notice that when opening the icebox, the backlog is reloaded and it has scrolled back to the top so you lose your place

This one is pretty frustrating since you have to scroll back down to where you want to "drag" your new story.

Heidi shared an idea in Pivotal Labs on January 22, 2008 00:30:

Add ability to "hide" top 1.5 inches of tracker window

It would be nice to be able to "hide" the top 1.5 inches of the tracker window just like you do when you want to hide the navigation buttons or field, or bookmarks in your browser.

We often view tracker on the wall with a projector and then we edit stories in our sprint planning meeting, for example.

Even though we are able to make the description field bigger vertically (thanks for that change), it is still sometimes a challenge to have enough room to do the edits.

Hope I explained that clearly.

Heidi reported a problem in Pivotal Labs on January 22, 2008 00:02:

Error: Mysql::Error: Deadlock

I can't remember exactly what I was doing but I got a deadlock error (and so did my co-worker). I have a screenshot. This tool doesn't have the ability to upload screenshots, does it? Pls tell me where to send the screenshot. Thx, Heidi

Heidi replied on January 17, 2008 19:20 to the problem "Error executing stale command" in Pivotal Labs:

Thanks!!

Heidi replied on January 17, 2008 19:19 to the problem "Unresponsive Script Error in Firefox" in Pivotal Labs:

Hi - thanks! I'll let you know if I experience this again.

Heidi replied on January 17, 2008 19:15 to the problem "Suggestion: delete question marks at top of columns to left of X's used to close panels" in Pivotal Labs:

Hey thanks for being so responsive. I really like the delay you added!

Heidi replied on January 17, 2008 02:34 to the problem "Unresponsive Script Error in Firefox" in Pivotal Labs:

This just happened again when trying to move a "revealed" search result into the backlog....with 4 columns open.

Heidi reported a problem in Pivotal Labs on January 16, 2008 23:41:

Unresponsive Script Error in Firefox

This is a frequent error that we see. I just got it again so I thought I'd add it to satisfaction so I can follow it.

I think this is what happened with this instance. I think it has something to do with having multiple panels open and using search??

1. I had the backlog and the icebox open.
2. I clicked on search.
3. I pulled up a search result.
4. I clicked reveal on the search result.
The story was in the icebox.
5. I tried to move the revealed story from the icebox into the backlog. Then I got this error from Firefox.

Warning: Unresponsive script
A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Using Firefox v2.0.0.11

I have already done this to Firefox which Mark M told me to do before:
In the short term you can adjust the Firefox unresponsive script timeout limit by following the steps below.

1. Type about:config in Firefox's address bar.
2. Filter down to the value for dom.max_script_run_time.
3. Double-Click the field and in the pop-up, change the value to something higher than the default, like 25

Heidi shared an idea in Pivotal Labs on January 16, 2008 22:38:

Add ability to put template into description of story

It would be nice to be able to add your own "template" into the description section of a story.

For example, when Alex was at AppFolio he helped us develop a template for writing bug descriptions.

It would be nice to click a button to have that template pre-loaded or something. Since then we also have a template for writing features.

What we do as a workaround is create a story and call it "user story template" for example, and we keep it at the top of the icebox. To use the template you have to open the description of the story and copy the template which you then paste into your new story. We do the same things for bugs.

Heidi reported a problem in Pivotal Labs on January 16, 2008 22:01:

Error executing stale command

I got this error yesterday from tracker: Error executing a stale commands: TypeError: this._resource has no properties (queue contents are: []) Please click 'OK' to reload Tracker.

I can't remember what I was doing when it happened.

Note also that the error message needs some editing: should be command and not commands

Heidi replied on January 14, 2008 18:09 to the problem "Suggestion: delete question marks at top of columns to left of X's used to close panels" in Pivotal Labs:

Hi - Just got back from vacation. I like the way the question marks look, that's not it. I don't like accidentally mousing over them and then having the pop up message cover up the X that I was trying to push. So that was the annoyance.

I've heard other people around here voice annoyance at the fly-overs in general. It would be a nice feature to be able to turn those off via a setting. But it's not high priority in my opinion. (Getting stats is more important!)

I like the fly-overs that show you the description of a story. That saves me time from having to open up a story.

Changing the fly over delay as Dan suggested would be a great next step.

Thanks, Heidi

Heidi reported a problem in Pivotal Labs on January 08, 2008 00:59:

Suggestion: delete question marks at top of columns to left of X's used to close panels

At the top of tracker you have question marks which tell you the definition of Current, Backlog and Icebox (for ex).

I often find myself mousing over these by accident when I'm trying to close a panel. It gets pretty annoying.

Those question marks are useful when you first start using Tracker, but after you know how to use tracker they are not helpful. Do they deserve that real estate?

If you need to define the columns you could show the tooltips when you mouse over the words themselves.

Or, if you must keep the question marks, maybe you can re-orient the tooltip so it doesn't cover up the X.