Heidi's dashboard

A comment on the problem "Import/Export between projects deletes attachments" in Pivotal Labs:

OK - thanks for the response – Heidi, on July 21, 2009 21:29

Heidi reported a problem in Pivotal Labs on July 20, 2009 23:58:

Import/Export between projects deletes attachments

Exporting stories from one project and importing into another deletes attachments associated with stories.

I think this used to work.

Heidi marked one of Mark's replies in Pivotal Labs as useful. Mark replied to the question "Import selected from one project to another giving error".

Heidi replied on July 15, 2009 16:52 to the question "Import selected from one project to another giving error" in Pivotal Labs:

The problem is solved. Thanks so much!

Heidi replied on July 09, 2009 14:45 to the question "Import selected from one project to another giving error" in Pivotal Labs:

Hi - I emailed the file. Thanks Mark!

Heidi asked a question in Pivotal Labs on July 08, 2009 23:50:

Import selected from one project to another giving error

STR:
-Selected 3 stories in icebox. All three are unestimated bugs, unstarted.
-Exported selected stories
-Went to destination project and imported the file
-Got this error: Import FAILED: Invalid CSV format: Validation failed: Stories in the accepted state must be estimated.
-I tried this twice with the same result. Please advise as I'd rather not recreate these stories from scratch!
Thanks, Heidi

Heidi replied on June 23, 2009 13:19 to the question "Autofill of twitter username/pw on settings" in Pivotal Labs:

Thanks Dan. I can turn it off in the meantime.

Heidi asked a question in Pivotal Labs on June 22, 2009 14:10:

Autofill of twitter username/pw on settings

Autofill of twitter username and password should be removed from the settings page.

If you go to settings to do something else like I did, you error out each time since the username and password put in there is not correct for twitter. I had to erase them and then save that page each time I made a change to settings.

Also, could someone accidentally make stuff available on twitter when not intending to do so if the email and password you prefill there is the same as their twitter account?

Heidi started following the idea "How about custom point values" in Pivotal Labs.

Heidi started following the idea "Possibility of specifying tasks for each story, and estimating them in hours" in Pivotal Labs.

Heidi started following the idea "It would be great to add tasks to a story" in Pivotal Labs.

Heidi marked one of danp's replies in Pivotal Labs as useful. danp replied to the question "Moving stories "out" of iteration".

Heidi asked a question in Pivotal Labs on March 05, 2009 14:44:

Moving stories "out" of iteration

When you are nearing a release and there are some stories that you are not going to do (in order to make your date) are we supposed to leave them in Current and just ignore them? I feel like we want to "move them out" so our customer doesn't think they are going to be part of our release. What is the Tracker best practice with this situation?

Heidi replied on February 20, 2009 18:48 to the problem "Stories are moving on their own from bottom of backlog to top of current." in Pivotal Labs:

Thanks. This has not been happening lately and I was wondering if you fixed it. I don't understand the condition that creates this bug. Anyhow, thanks for your work on it!

Heidi replied on February 20, 2009 01:50 to the problem "Stories are moving on their own from bottom of backlog to top of current." in Pivotal Labs:

Did you implement this solution?

Heidi replied on February 11, 2009 18:30 to the problem "Stories are moving on their own from bottom of backlog to top of current." in Pivotal Labs:

I don't think two people are moving the story at the same time, but I could be wrong.

I think you should try flashing the message and leaving the story where it was originally as the next step. Then we can see if that solves this problem.

By the way, we have seen this problem with more than one story. I added a second story with ID 410845 under the original story 403672. Then we can see if the second story also moves.

Thanks again for your help.

Heidi replied on February 10, 2009 14:35 to the problem "Stories are moving on their own from bottom of backlog to top of current." in Pivotal Labs:

There is one story doing this now, since the rest are in the icebox. It's called
Points to Break 403672 It moved to the top of current. If you look in its history it says that it was unscheduled. But it is not in the icebox.

Heidi replied on February 10, 2009 01:28 to the problem "Stories are moving on their own from bottom of backlog to top of current." in Pivotal Labs:

This is happening again today so I just moved everything from the backlog into the icebox to try to control the problem. I look in history and it looks like a bunch of the stories were changed to unscheduled - what does that mean? Do you guys have any leads on how to fix this?

Heidi replied on February 06, 2009 17:17 to the problem "Stories are moving on their own from bottom of backlog to top of current." in Pivotal Labs:

Hi - they move on their own sometime after they are moved to the bottom of the backlog. IE not immediately - not sure when or if there is a specific trigger. We go about our work and then find that the bugs are at the top of current again. Thanks for investigating!!

Heidi reported a problem in Pivotal Labs on February 06, 2009 01:11:

Stories are moving on their own from bottom of backlog to top of current.

Stories are moving on their own from *bottom* of backlog to *top* of current.
It's a set of stories. We moved them a few times out of current and back to the bottom of the backlog, but they kept going back to the top of current. We now moved them to the top of the icebox so hopefully they will not go to the top of current again.