This task provides corrections and follow‑up work related to PR IMP #104599.

## Expected Behavior After This Commit
1. Renamed the stat buttons in the Project form view to make their purpose clearer.
2. Corrected breadcrumb generation when accessing the Project form view from the top menu.
3. Adjusted the project update form view to remove excessive padding.
4. Added a graph to the project update view to visualize project progress over time.
5. Updated filters in the margin search view.
6. Improved billable type labels for better user clarity.
7. Ensured billable types are updated correctly when sale_timesheet is installed.
8. Added navigation from analytic lines to their parent record in the margin list view.
9. Added three colors (gray, green, red) to the Milestone stat button.
10. Improved the kanban view of projected margins.

## Additions

### Point 2 — Breadcrumb Fix
When navigating from the top menu to the Project Overview, breadcrumbs were not generated correctly. To resolve this, a multi‑step flow was implemented:

- Clicking the "Overview" button triggers the action `project_embedded_action_project_overview`.
- This action calls the Python method `action_open_project_form`, which then triggers the client action `project_top_menu_overview`.
- The client action uses the `doAction` service to open the Project form view.

This approach is required because:
- Breadcrumbs are generated correctly only when `doAction` is executed inside a client action.
- The "Overview" button cannot directly trigger a client action, making the Python intermediary necessary.

### Point 7 — Billable Type Synchronization
The `sale_project` module defines the `billable_type` field on `account_analytic_line`, including the generic types *Other Revenues* and *Other Costs*. The `hr_timesheet` module adds additional, more specific billable types.

A problem occurs when:
- `sale_project` is installed first, causing analytic lines that should belong to `hr_timesheet` billable types to be incorrectly classified under *Other Revenues* or *Other Costs*.
- When `hr_timesheet` is installed afterward, these analytic lines are not automatically updated.

This fix ensures that potentially misclassified analytic lines are corrected when both `hr_timesheet` and `sale_project` are installed.

## Task :
task-[5955934](https://www.odoo.com/odoo/project/4105/tasks/5955934)

This task provides corrections and follow‑up work related to PR : IMP #236971 .

## Expected Behavior After This Commit
1. Renamed the stat buttons in the Project form view to make their purpose clearer.
2. Corrected breadcrumb generation when accessing the Project form view from the top menu.
3. Adjusted the project update form view to remove excessive padding.
4. Added a graph to the project update view to visualize project progress over time.
5. Updated filters in the margin search view.
6. Improved billable type labels for better user clarity.
7. Ensured billable types are updated correctly when sale_timesheet is installed.
8. Added navigation from analytic lines to their parent record in the margin list view.
9. Added three colors (gray, green, red) to the Milestone stat button.
10. Improved the kanban view of projected margins.

## Additions

### Point 2 — Breadcrumb Fix
When navigating from the top menu to the Project Overview, breadcrumbs were not generated correctly. To resolve this, a multi‑step flow was implemented:

- Clicking the "Overview" button triggers the action `project_embedded_action_project_overview`.
- This action calls the Python method `action_open_project_form`, which then triggers the client action `project_top_menu_overview`.
- The client action uses the `doAction` service to open the Project form view.

This approach is required because:
- Breadcrumbs are generated correctly only when `doAction` is executed inside a client action.
- The "Overview" button cannot directly trigger a client action, making the Python intermediary necessary.

### Point 7 — Billable Type Synchronization
The `sale_project` module defines the `billable_type` field on `account_analytic_line`, including the generic types *Other Revenues* and *Other Costs*. The `hr_timesheet` module adds additional, more specific billable types.

A problem occurs when:
- `sale_project` is installed first, causing analytic lines that should belong to `hr_timesheet` billable types to be incorrectly classified under *Other Revenues* or *Other Costs*.
- When `hr_timesheet` is installed afterward, these analytic lines are not automatically updated.

This fix ensures that potentially misclassified analytic lines are corrected when both `hr_timesheet` and `sale_project` are installed.

## Task
task-[5955934](https://www.odoo.com/odoo/project/4105/tasks/5955934)



---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr