ProjectTRACKER Help - Naming Conventions

Date Format

To overcome country specific date formats, and make date queries and filtering easy, the ProjectTRACKER uses the following date convention:


YYYY 4 digit year
MM 2 digit month
DD 2 digit day


Date ProjectTRACKER date
4th July 2008 20080704
02.04.2010 20100402
03-22-2009 20090322

Group Format

ProjectTRACKER allows a hierarchical definition of resource and task groups. The group name format must match the regular expression:




The first mandatory letter is called Top Level Group. A '.' defines a Summary Group. ProjectTRACKER automatically shows these groups in a summarized form, e.g. calculates the sum of all efforts belonging to this group, e.g.:

'E1', 'E2', 'E3' are belonging to the Summary Group 'E.' and 'E11', 'E12', 'E13' are belonging to the Summary Groups 'E1. and 'E.'.


  • Input to summary groups is restricted (e.g. fields are greyed). In case you changed a group by fault to a Summary Group, just change it back to a normal group.
  • Users are restricted to start their task groups with certain letters depending on the settings in User Groups - a warning in the form 'Task group must start with: ???' is shown in case you selected the wrong letter.
  • When appending a '#' to the group name (e.g. E1#) ProjectTRACKER will automatically calculate the next available group name (e.g. E14). When the group name level is not existing yet a '0' will be added. For Tasks a multi digit increment can be done with several '#', e.g. E1##1.

Group Name Notations

In order to keep overview over complex program and task structures, it is highly recommended to use rigid task and user group name notations. With this you can easily reduce the view to a certain group of tasks and users by using the Task Group and User Group filter function of the ProjectTRACKER.

For project-oriented companies e.g. the following task group notations could be used:

Top Level Group Description
B Customer billable project / work / service.
N Customer non-billable project / work / service.
M Mapping tasks1).
O Operations, e.g. holidays, absence, training, self-management.
S Scrum tasks2).
T Template tasks3).

For product-oriented companies e.g. the following task group notations could be used:

Top Level Group Description
A Software amortization / capitalization planning.
E Engineering new development program.
I Installed base program, e.g. a patch or a service pack.
O Operations, e.g. holidays, absence, training, self-management.
M Mapping tasks4).
P Portfolio planning.
S Scrum tasks5).
T Template tasks6).

Note: The visibility of Top Level Groups to users is depending on the settings in User Groups.

Tasks groups are further refined by program / project releases, e.g.:

Task Group Notation Description
X7)A12 Product A release 1.2.
X8)B0921 Project for customer id #21 2009.
X9)C09 Common Component development tasks in 2009.

Note: The version info is most probably redundant to the Programs name, but as groups are independent of programs it is recommended to use this notation. Task groups are also very useful in the case of tasks belonging together but associated to several programs, e.g. the Common Component development tasks C0901, C0902 etc. could be filtered via the Task Group filter C09.

Groups on patch or service pack level could be e.g. named with:

Task Group Notation Description
X10)A12PA Product A release 1.2 patch A.
X11)A12S3PA Product A release 1.2 service pack 3 patch A.

The task groups should be then further refined according to the Program Breakdown Structure (PBS), e.g.:

  • EA12.
    • EA1201.
      • EA1201A
      • EA1201B
      • EA1201C.
        • EA1201C1
        • EA1201C2
      • EA1201D
    • EA1202.
    • EA1299.
1) , 2) , 3) , 4) , 5) , 6)
Letter is configurable by the ProjectTRACKER PHP administrator
7) , 8) , 9) , 10) , 11)
One of the Top Level Group letters
  • tracker/naming.txt
  • Last modified: 2012/09/23 16:57
  • (external edit)