[IMP] Recruitment: Velocity analysis

closes odoo/documentation#14429

X-original-commit: 011a4503eb
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Signed-off-by: Lara Martini (larm) <larm@odoo.com>

content/applications/hr/recruitment.rst

@@ -393,7 +393,7 @@ appears in the chatter.
    - :doc:`recruitment/refuse_applicant`
    - :doc:`recruitment/applicant_analysis`
    - :doc:`recruitment/source_analysis`
-   - :doc:`recruitment/time_in_stage`
+   - :doc:`recruitment/velocity_analysis`
    - :doc:`recruitment/team_performance`
 
 .. toctree::
@@ -407,5 +407,5 @@ appears in the chatter.
    recruitment/refuse_applicant
    recruitment/applicant_analysis
    recruitment/source_analysis
-   recruitment/time_in_stage
+   recruitment/velocity_analysis
    recruitment/team_performance

content/applications/hr/recruitment/velocity_analysis.rst

@@ -1,21 +1,21 @@
-======================
-Time in stage analysis
-======================
+=================
+Velocity analysis
+=================
 
-The *Time In Stage Analysis* report provides information on how long applicants stay in each stage
-of the recruitment process. This is important, as every job position has specific :ref:`process
-details <recruitment/new_job_position/edit>` that state the length of time applicants should expect
-to wait between specific stages.
+The *Velocity Analysis* report provides information on how long applicants stay in each stage of the
+recruitment process. This is important, as every job position has specific :ref:`process details
+<recruitment/new_job_position/edit>` that state the length of time applicants should expect to wait
+between specific stages.
 
 Knowing how long applicants remain in each stage can help highlight possible bottlenecks. Analyzing
 this data allows the recruitment team to assess each stage, identify any issues, and pivot their
 strategies to move applicants through each stage, within the expected time interval.
 
-Time in stage analysis report
-=============================
+Velocity analysis report
+========================
 
-To access the report, navigate to :menuselection:`Recruitment app --> Reporting --> Time in Stage
-Analysis`. By default, the report displays data from all job positions, with the stages populating
+To access the report, navigate to :menuselection:`Recruitment app --> Reporting --> Velocity
+Analysis`. By default, the report displays data for all job positions, with the stages populating
 the x-axis, and the number of days populating the y-axis, in a :icon:`fa-line-chart`
 :guilabel:`(Line Chart)`.
 
@@ -25,24 +25,23 @@ days.
 Hover over a stage in the line chart to reveal a popover window listing all the job positions within
 it, and the average number of days each job position sits in each stage.
 
-For a more visually digestible view of the information in the :guilabel:`Time In Stage Analysis`
-report, click the :icon:`fa-bar-chart` :guilabel:`(Bar Chart)` icon in the upper-left corner. This
-displays all the information in a bar chart.
+For a more visually digestible view of the information in the :guilabel:`Velocity Analysis` report,
+click the :icon:`fa-bar-chart` :guilabel:`(Bar Chart)` icon in the upper-left corner. This displays
+all the information in a bar chart.
 
 In this view, it is easier to visualize the differences between the job positions, regarding how
-long applicants stay in each stage. From this view, recruiters can more easily determine which job
-positions have delays or bottlenecks at certain stages.
+long applicants stay in each stage. From this view, recruiters can determine which job positions
+have delays or bottlenecks at certain stages.
 
-.. image:: time_in_stage/bar-chart.png
-   :align: center
-   :alt: The bar chart view of the Time In Stage Analysis report.
+.. image:: velocity_analysis/bar-chart.png
+   :alt: The bar chart view of the Velocity Analysis report.
 
 Use case: comparing times by month
 ----------------------------------
 
-With the :guilabel:`Time In Stage Analysis` report, it is possible to see if there are certain
-months where applicants take longer to be moved through the pipeline. To view this data, switch to
-the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view in the upper-right corner.
+With the :guilabel:`Velocity Analysis` report, it is possible to see if there are certain months
+where applicants take longer to be moved through the pipeline. To view this data, switch to the
+:icon:`oi-view-pivot` :guilabel:`(Pivot)` view in the upper-right corner.
 
 This presents the data in a detailed pivot table, with the rows representing the different job
 positions, and the columns representing the stages. The average :guilabel:`Days in Stage` populates
@@ -52,9 +51,8 @@ the various boxes.
    If a field is empty, it indicates no applicant has been in that stage. Instead, all applicants
    moved from a previous stage without being placed in the stage with an empty field.
 
-.. image:: time_in_stage/time-pivot.png
-   :align: center
-   :alt: The pivot table view of the Time In Stage Analysis report.
+.. image:: velocity_analysis/time-pivot.png
+   :alt: The pivot table view of the Velocity Analysis report.
 
 Click :icon:`fa-minus-square-o` :guilabel:`Total` above the job position rows to collapse the
 information. Next, click :icon:`fa-plus-square` :guilabel:`Total` again, revealing a drop-down menu.
@@ -64,8 +62,7 @@ further grouping options. Click :guilabel:`Start Date` from the expanded list.
 After doing so, the data presented is grouped with the various months from the previous 365 days for
 the rows, leaving the :guilabel:`Days In Stage` as the columns.
 
-.. image:: time_in_stage/time-dates.png
-   :align: center
+.. image:: velocity_analysis/time-dates.png
    :alt: The pivot table showing the months averages for times in stage.
 
 In this example, :guilabel:`July 2024` had the longest time that applicants spent in each stage, on