Project Milestones
Package: PROJECTS
1. General
The Project Milestones module serves – in conjunction with the Projects module – to plan and manage project milestones. Milestones divide the project process into stages with verifiable interim goals, thus facilitating the planning and control of project progress.
A software development project is divided into three milestones: Development Phase, Internal Test Phase and External Test Phase. A separate record is created for each milestone, linked to the project and a target date is set. As soon as a phase is completed, the Is Milestone toggle can be activated to mark the milestone as reached.
A project is divided into three billing phases. A milestone is created for each phase. As soon as a milestone is reached, the Billing Status in the linked project is manually set to the corresponding value and the invoice is created via the Invoices module.
This section only describes special fields or functionalities of the module, as all general brainX functionalities are described elsewhere in the manual.
2. List View
The list view in the Project Milestones module has the usual functionalities of a list view. For more detailed information, see the section Structure/Layout – List View.
2.1. Actions
In the list view, general actions are available depending on the module. An overview and description of all general actions can be found in the section Actions (List View).
There are no module-specific actions in this module.
3. Detail View
3.1. Fields
The following table describes required fields and fields with non-obvious functions. All other fields are self-explanatory.
Basic Data Block
| Field | Description |
|---|---|
| Title * | Name of the project milestone |
| Project * | Linked Project |
| Is Milestone | When activated, the record is marked as a reached milestone |
| Type |
|
*Required field
3.2. Actions
The following actions are available in the detail view:
3.2.1. General Actions
- PDF Export
- Recommend
- Copy
- Delete
- Change Tracking
For detailed information on the actions, see the section Actions (Detail View).
3.2.2. Module-Specific Actions
There are no module-specific actions in this module.
4. Practical Examples
1 – Planning the Phases of a Software Development Project as Milestones
A software development project is to be divided into clearly defined phases to track progress in a structured way. In the Project Milestones module, three records are created: Development Phase, Internal Test Phase and External Test Phase. Each milestone is linked to the corresponding project, assigned the appropriate Type and given a target date.
As soon as a phase is completed, the Is Milestone toggle is activated to mark the milestone as reached. The status of the linked project is updated accordingly. This keeps project progress transparent and traceable for all parties at all times.
2 – Using Billing Milestones for Milestone-Based Billing
A customer project is divided into three billing phases. A milestone is created for each phase in the Project Milestones module and linked to the project. The target dates of the individual milestones are based on the contractually agreed delivery dates.
As soon as a milestone is reached – e.g., after acceptance of the first project phase by the customer – the Is Milestone toggle is activated. Subsequently, the Billing Status in the linked project is manually set to the corresponding value and the partial invoice is created in the Invoices module. Through the close link between milestone, project and invoice, the billing status remains traceable at all times.
3 – Managing the Milestone Overview for All Projects in the List View
A project manager supervises several parallel customer projects and wants to maintain an overview of all upcoming milestones. In the list view of the Project Milestones module, a custom view is created that shows all milestones sorted by target date and filtered by the field Is Milestone = not activated.
This gives the project manager a clear overview of all outstanding milestones across all projects – without having to switch to each project record individually. Completed milestones are hidden from the filtered view by activating the Is Milestone toggle.
5. Frequently Asked Questions
In which package is the Project Milestones module available?
The Project Milestones module is available in the Projects package – together with the Projects module, with which it closely cooperates.
Can a milestone be created without a link to a project?
No. The Project field is a required field. Every milestone must be linked to an existing project.
What does the "Is Milestone" toggle do?
When the toggle is activated, the record is marked as a reached milestone. This serves for status tracking and can be used as a filter criterion in the list view to distinguish completed from outstanding milestones.
How are milestones added to a project?
Milestones can be created directly from the project via the module-specific action New Milestone – they are automatically linked to the project. Alternatively, a new milestone can be created directly in the Project Milestones module and the project manually selected in the required Project field.
Are there module-specific actions in the Project Milestones module?
No. There are no module-specific actions available in the detail view of the Project Milestones module. Only the general actions PDF Export, Recommend, Copy, Delete and Change Tracking are available.
How is the billing status of a project updated after a milestone is reached?
The Billing Status field in the linked project is not automatically updated – it must be set manually or via an automation to the corresponding value after a milestone has been marked as reached.