General
-
8 votes
-
Add many clients/projects in a row
it might be nice to have the option to add multiple clients and multiple projects at once or in a row - rather than landing on the project dash for each project after it's created. I see this being helpful for initial setup.
7 votes -
Find a way to allow different billable rates in the same phase.
Right now we bill Dev, Test, and PM/BA all at different rates. For this to work in Burndown, I have to have 3 phases for every project, duplicating all the tasks in each phase.
I would like to be able to track time and work for my entire team in one "Phase" instead of needing to create many phases and duplicating data.
My first thought was to assign the billable rate to a Task Type instead of to a phase, then force all tasks to have a Type.
4 votes -
Instead of setting a user's password for them, just send an invite
Instead just ask for the name & email of the person you wish to invite. They click on a link and set their own password. This is a good idea for a number of reasons, including avoiding sending the initial password through insecure plain text email.
4 votes -
View burndown chart by person or resource type
Be able to breakdown the master burndown chart and view the resource load for a specific person, or at least by resource type (e.g. design, UX, interactive, identity, PM).
3 votes -
3 votes
-
Allow global phases with graphs
With our company we will be treating phases as departments. Design, Development, SEO, Project Management, etc. The problem is this system will only really work for one department, because not all employees have the same skill sets. If we have 200 hours of available development time a week, it's hard to see that in the graph when it's mixed with the entire company's time. Since the phases on each project are identical for us, we would prefer for them to be global, with the ability to see a graph for each phase/department.
2 votes -
Add openid/GoogleApps authentication
It would be nice for managing with google apps and it would help reduce password fatigue.
2 votes -
2 votes
-
Assign due date to a task
Assign a due date to a task, or import that due date from a bug tracker or Basecamp.
1 vote -
Give a client view so that clients can view their project status live.
It would need to prevent them from having access to other client projects. The export is handy but its still a manual process. For some clients it would be handy to give them direct access to their project so they can view each phase status on demand.
1 voteplanned ·
AdminJoel Meador
(Admin, Project Burndown)
responded
We do plan to add information access features like this.
On a scale of now to next year, how important is this to you?
-
Expose Project Actual Cost for use in exporting.
It was exposed at the phase, group, and task level but not at the project level. I need it for a summary page.
Currently estimated cost is exposed via {{ total_price }} but actual price is not.
1 vote -
Add an "On Hold" option to a phase so it doesn't appear in the Unscheduled Phases list.
Often we'll have items that are not part of the project plan at this time but are still worth noting because they may occur in a later phase. However this phase isn't planned at all right now and may never be planned.
I would like an option to keep these items tracked in Burndown but have the phase be "On Hold" so burndown does not expect me to schedule it.
Just about every project we do have items like this, (Our "Should" and "Could" items), so without a way to put them on hold the Unscheduled Phases feature of burndown… more
1 vote -
1 vote
-
Allow groups to be placed as children of groups.
Groups are just a container. I would like to be able to next my groups deeper then 1 level.
The way I typically organize Burndown for website development is the Group is the name of the Webpage. It would be nice if I could break down different type of work for each page further to assist in grouping tasks for say design, dev, pm, test, ba, etc.
1 voteunder review ·AdminMatt Gordon (Admin, Project Burndown) responded
This is something we’ve talked about on a few occasions, but shied away from due to usability concerns. We’ll take another look at it and see how this idea might fit into Project Burndown.
-
When adding a task automatically in Pivotal Tracker, the estimate should be "Unestimated", not "0".
If I build out a project first in Burndown and have Burndown automatically add the stories to Tracker, I would expect the stories to be unestimated so my developers can go in and add their estimates (by clicking the fancy buttons) instead of having to open each task and change the dropdown.
It also has the benefit of forcing them to estimate their stories without being able to start with and leave it at 0 points.
1 vote -
Deleted stories from PT should not factor into the automated check mark that appears in
I have a large project where every item in burndown has many PT items associated with it. If a PT item gets deleted, it stays associated with the burndown task as a deleted item (which is fine) but the status of the deleted PT item still factors into the 'check mark' calculation.
This has caused me to get on people about not getting their stuff done on time incorrectly due to the propagation of the unchecked tasks. On a large project it is very tedious to review every unchecked task to make sure there is no deleted PT item associated… more
1 vote -
1 vote
-
Don't automatically write stuff to the description of a PT story when I add it to a task.
A comment, maybe - but writing a text blob at the end of the description field (with no hard return, just put in at the end) of every story when I add it to a task is very invasive (and time consuming to go back and delete).
0 votes -
Show the times on the export page in local time
Each account can set the time in it's account profile. Or let the users set it individually?
0 votes