We're just starting to use Tracker after using FogBugz for a longtime. Pretty nice UI so far.
One question, is it possible print the listing of Stories in CURRENT? It would be very useful to us for planning but just hitting File>Print gives some pretty ugly results.
I've tried instead creating a Report for this, but can't get it to just include stuff in Current list not matter which combo of query parameters I try. It keeps including stuff not in current (I created a bunch current/non-current things on the same day so I can't just use date as the filter). Also, it doesn't respect the order they are in the Current box.
Going through stories, I love to be able to hover to check out new comments or read the descriptions. Lately, however, doing so causes the story list to re-scroll, thereby making the hover quickly appear and disappear, and leaving me lost (it leaves me scrolled to the top of the column--sometimes far from where I was). ARGH!
I can indirectly change the start date of an iteration by changing the starting day and the length but I can't seem to change it from Mon 2 Jun to Mon 9 Jun. Is there any way to correct an iteration start date?
I have had a couple times where it would be nice to be able to set the "first" iteration number. One, where I was setting up a team that had been doing iterations for two years, and I wanted an easy way to make project look like what they were used to. Another was when we needed to set up a second project within the same company-- basically forking the development. We needed separate tracker projects and priorities, but it would be nice to keep the numbering in sync. I know the trick of "back-dating" a story (and have done that twice), but just having a number would be easier.
Adding a 'remember me?' checkbox and storing the session in a cookie would be really helpful as I'm finding it a chore having to login each time. I use Fluid.app and so am opening and closing my Pivotal Tracker application all the time, but am required to re-enter my login details repeatedly, so this would be a great time saver.
We have our demo, retrospective and iteration planning on the same day (wednesday). The problem with that is that if we wait to press the accept button until after the demo, those stories become late and part of the new iteration which messes up our velocity.
A couple solutions that came to mind were to be able to set the time which the new iteration starts to a sat 2pm on iteration day that way the demo can be done in the morning and all stories are accepted before the new iteration starts.
Another solution would be to have an accept and demoed button where the accept marks the story as done as far as velocity calculations go.
Another way would be to set the iteration on Tracker to a day after our actual physical meetings but that would bastardize the tool.
If you go to the settings page and change the project name it saves 'immediately', but only if you click out of the text box on the same page. It took me four tries to figure this out. I think that an 'update' button would be useful in this context.
What time of day does the system close the iteration?
I noticed today, after the first week of playing with Tracker, that the iteration is automatically advanced by the system when it gets to the specified day. What time exactly does that happen? Is there any way to change the iteration start time?
We've been using weekly iterations, starting on Mondays at noon. This has worked for us, cause we get to close up some last minute things on Monday morning before breaking for our iteration planning session after lunch. Then the next iteration starts immediately after our Monday afternoon planning.
Seems like Tracker wants to start the iteration at the beginning of the day. It would be a nice customization to be able to change this.
On a story, click "Attach a file", then "Browse...", then pick a file. Then click "Save" (instead of "Upload"). This causes the attachment to be forgotten (never uploaded). Expected behavior would be for "Save" to cause the upload to happen or, perhaps, something like greying out save or some kind of error telling you to click upload or something. But the current behavior is confusing - it does not match what you'd expect based on what Save does for other fields.
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".
Within a project, search for a keyword. In the search results pane, "delete" a story. The story will not disappear. As a matter of fact you can re-delete it. The consequent deletions actually show up in the history panel.
Loading Profile...
Anand Agarawala
last replied
on July 01, 2008 16:25
Mark (Employee)
last replied
on July 08, 2008 14:56
DrewMc
last replied
on July 07, 2008 16:46
Peter Ferne
last replied
on July 07, 2008 16:23
Paul Zabelin (Employee)
last replied
on July 04, 2008 23:07
Bruno Miranda
last replied
on July 01, 2008 21:06
Arena (Employee)
last replied
on July 01, 2008 18:28
Heidi
last replied
on June 27, 2008 16:12
Curtis
last replied
on June 26, 2008 20:41
Sean (Official Rep)
last replied
on June 25, 2008 00:00
danp (Official Rep)
last replied
on June 24, 2008 04:36
EMPLOYEE
EMPLOYEE
