Recently active topics in Pivotal Labs

I would like to know how many points are in icebox's stories (just like in current or backlog, an small counter in it's header is enough) so I can have an idea of how much works remains to be done

We frequently have multiple tasks/stories associated with a larger task that is being split into more granular steps. It's one thing to split a task into 2 or 3 discrete tasks, but it would be great to be able to associate tasks together. Right now we do this by using a title prefix, e.g. "Such and Such: Specific Task", so that we can search for "Such and Such" tasks and associate them together. I don't think labels make sense for this, as these are a set of related tasks within a larger release; they don't have some innate or inherent property, like "splitme". Some kind of task association, or the definition of a meta-task which contains, or from which are derived, multiple granular tasks, would be great.

It would be nice to be able to log hours on specific cards and have a report to show weekly what tasks were done and the hours logged.

I would like to use a different email for each account.

I would like to use one email address for work projects, and another for other projects.

hotkeys are VERY badly needed: http://www.acunote.com/open-source/ja...

Hey Guys,

I LOVE the product! Why not create a simple demo video with Screenflow or another screencast tool? That would help us to understand the process of using Pivotal Tracker in our companies.

Would be so nice if users could set an option in their profile so that their default view is "My Work" instead of the whole project view. It's difficult for a developer to sort through the noise and just view the items assigned to him/her.

When code is complete assign to QA, with notification, for testing to begin. Notify developer and owner when QA marks as accepted or rejected.

This is what a viewer sees when looking at a story:


I understand that those controls are there for people who can actually change the values and it's easy to just disable them if the user doesn't have suitable permissions, but disabled form inputs aren't the best way to view information.

I think it'd be best to start with the description (especially if it's in "Dan North format"), since that's the meat of the story. The rest of the information is extra. I don't have the answer for what would be the best way to present all of it, but I have the feeling the way to get there is to come up with something that works really well for viewers (people who cannot change any of the values) and then add controls (regular form inputs, something else) for the users with permissions, not start with an edit form and then disable inputs.

It would be of tremendous help to have an iPhone-compatible version.

Not something very sophisticated, but allowing to see all the pending stories.
Yes, it's possible to do project management over lunch ;-)

We'd love to show burn-up report that counts items that are marked as "delivered" rather than only those that are "accepted". Since our customers only accept items every few days rather than immediately upon delivery, we get into this situation where we can't see our iteration velocity until our customers accept our items. Obviously, we still need the burn-down/burn-up charts that measure only accepted items - but this report (possibly called "delivered burn-down" as opposed to "accepted burn-down") would be super-useful

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.

I'd love to be able to set different scales based on the project type. So one project might have 1-10 scale, while another would have 0-2. This would allow me to make Tracker best fit my existing processes.

Format the dates the API returns as numbers instead of using the short (english) month.
As it is, the API returns the dates in the following format: Sep 16, 2008. While I can ask the DateTime library to parse it according to English Culture rules, I think it's a bit frail, and we would be better served with a more culture-agnostic format for the dates.
Ideally I think the dates would come ISO formatted, with timezone information if it includes time, but YYYY/MM/DD would be better nonetheless.