Allow custom fields
Allow "Advanced" users to define custom fields for tasks and to define who can update their values (security restrictions, similar to the 'update own percentage' permission). Custom fields would be valid across all projects, not per project (otherwise you'll get into trouble trying to show all these with multiple projects on the Gantt chart - not worth the potential complications).
Each custom field would have a field name and a data type. I recommend the following custom-field data types:
- datetime fields (representing a specific point in time)
- duration fields (floating-point field with associated duration units of minutes, hours, days, weeks, months or years)
- number (integer and/or floating-point)
- choice list (the list entries are defined when the field is defined)
Regarding permissions: "Advanced users" (who are allowed to create new projects) should be allowed to create such custom fields, which then are available on all tasks in all projects. Within each project, users with rights to invite new project-users should be allowed to defined whether the project users can update custom fields or merely view them.
Each user who can view the Gantt should have the option of displaying the custom fields as columns on the left (like % complete). It should be possible to filter on these fields (e.g. 'show only tasks); active filters on custom fields would be ANDed with other filters such as the assigned resources.
This would also cover many other feature requests you will get later anyway, e.g. the ability to store Estimated Time and Time Spent for each task - these would just be two custom duration fields; or the ability to create task status categories such as 'paused', 'approved', etc.; or categories indicating which department is responsible for the task.
Custom fields of course need to be imported/exported when the Gantt is imported/exported.
Brooks Williams commented
This would be very helpful to be able to track activities that are outside the original scope of the project - so that we could show the impact of scope creep beyond the original scope. Just a checkbox would do it!
Absolutely... custom fields would launch TeamGantt way ahead of several close competitors. The ability to then sort/filter by custom fields (e.g., like tags, status, whatever) is the beauty of it all.
Fully agreed. Also as a competitive tool for catching up with your competitors.
I agree with George - it seems basic after your product was launched so long ago.
My user story - we want to be able to prioritize tasks better, by being able to sort and filter by our own KPIs
I agree that this would be incredibly helpful. For our organization, we run many of the same type of projects, and being able to categorize certain tasks (potentially using custom fields as above). This would also make cross project view much more powerful if I want to view all tasks belonging to a certain category across projects.
George Kotsakis commented
Come on guys. How difficult is it to have custom fields? We want basic fields like: "Status" (Under Development, QA, UAT, LIVE, Frozen, Cancelled,..) etc..
or a field like "Unit" to be able to filter tasks/projects by the units under me,
or RequestingUnit, etc ..
please put it in your next plans.
Also would be nice to be able to define simple lists under a task (like we have discussions and attachments)
Totally agree. I use custom field to track Outplan tasks (extra work), etc.
John Hunt commented
... (e.g. 'show only tasks having an estimated duration longer than 4 hours')...