![]() | ![]() | ![]() | ![]() |
||||||||||||||
|
Start with ProjectForge ProjectForge® 2012 | ![]() | ||||||||||||||||
![]() |
| ![]() |
|||||||||||||||
|
|||||||||||||||||
| 1 | Recommended access management for team members. |
| 2 | Recommended task structure of a project. |
| 3 | Gantt charts. |
Hint
You can use the action links while reading this tutorial and create the objects of this tutorial by simply clicking on those action links (in the html version of this tutorial). You can change the tutorial data (user names etc.) like you want. The tutorial only needs the reference names placed in the description fields.
Hint
After the creation of the users you can use the wizard of the task tree page to generate groups and access rights very quickly. Follow this tutorial to understand the things behind the wizard...
| Username | Description (team role) | Assigned groups | Action link | |
|---|---|---|---|---|
| linda | Project manager | l.evans@javagurus.com | PF_ProjectManager | {actionLink|createUser|linda}create{/actionLink} |
| dave | Developer | d.jones@javagurus.com | - | {actionLink|createUser|dave}create{/actionLink} |
| betty | Developer | b.brown@javagurus.com | - | {actionLink|createUser|betty}create{/actionLink} |
| Task name | Parent task | Action link |
|---|---|---|
| JavaGurus Inc. | ProjectForge®'s root task | {actionLink|createTask|JavaGurus}create{/actionLink} |
| Group name | Assigned members | Action link |
|---|---|---|
| JavaGurus employees | Linda, Dave, Betty. | {actionLink|createGroup|JavaGurusEmployees}create{/actionLink} |
| Group name | Assigned members | Action link |
|---|---|---|
| ACME web portal team | Linda, Dave, Betty. | {actionLink|createGroup|ACME-WebPortal-Team}create{/actionLink} |
[Shift]
or
[Ctrl]
for assigning them at once.
| Task name | Parent task | Action link |
|---|---|---|
| ACME web portal | Root (select parent task by clicking on the hierarchy icon and simply select Root). | {actionLink|createTask|ACME-WebPortal}create{/actionLink} |
Hint
You can change the hierarchy and the names of your tasks (e. g. for organizing your projects per customer) later, so start with your project as top level task. Also user names, group names etc. can be changed any time you want without loosing any references in the system.
| Task | Group | Recursive | Description | Access rights | Action link |
|---|---|---|---|---|---|
| JavaGurus Inc. | JavaGurus employees | yes | The employee's main task for books, addresses, for time sheets not assigned to projects such as ill-ness, holiday, research and development etc. | Choose template 'employee'. | {actionLink|createAccess|JavaGurusEmployees}create{/actionLink} |
| ACME web portal | ACME web portal team | yes | The top-level task for the ACME web portal project. | Choose template 'employee'. | {actionLink|createAccess|ACME-WebPortal}create{/actionLink} |

| Figure 1: | Recommended access management for team members. |
Hint
If they're are any labels or text fields with italic letters (such as the label 'recursive') you'll get a tool-tip explaning the component when you place your mouse over such elements.
| Level | Type | Description |
|---|---|---|
| Top level | Customer | e. g. ACME. This is useful for grouping a lot of projects per customers. You can start without this level and can insert it later, if needed. |
| Level two | Project name | Simply the name of your project, e. g. ACME web portal |
| Level three | Release | Your project will have hopefully several releases, so you can group your activities per release. In non-IT projects the release can be something such as e. g. year for annual conferences etc. |
| Level four | Phases | Your project consists of several phases, e. g. akquisition, specification, build, maintenance. |
| Level five | Work packages | For large projects (more than 10 md) it's useful to break down your packages. |
| Level six | Issues | For very large projects it's useful to break down your packages in issues. If you're using the issue tracking system JIRA it's recommended to link the JIRA-Issues to your tasks and/or time sheets.. |

| Figure 2: | Recommended task structure of a project. |
Hint
You can add sub tasks by selecting your the parent task and pressing the button 'create sub task'. A more convenient method to organize the task structure of your project is by using the menu entry Gantt.
Hint
Please choose yourself as the user in the calendar view by simply clicking on the smiley at the right top, for displaying all your time sheets you have already booked.

| Figure 3: | Gantt charts. With the Gantt chart view you can easily create and modify Gantt charts. This view is also recommended, if you want to create your task structure of your project. |
config.xml.
PF_FINANCE
and the right "cost *" is set to read/write, same for projects.