Content
General info
This story focuses on managing and displaying the full forecast for processes in the CRM system. The aim is to ensure that forecasts are displayed comprehensively, without partial splits by business unit, responsible person, or recruiting team. Users should be able to view and adjust the forecast as needed.
Just as we have it right now:

Display the full forecast in the NA processes without splitting by BU / responsible / recruiting
User story
As a CRM user,
I want to view and manage the full forecast for processes,
So that I can get an accurate and comprehensive overview of the process forecasts without unnecessary splits or limitations.
RT-3078
–
Получение подробных данных проблемы…
СТАТУС
Visual design:
https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=44550-97243&t=joKloVDyECpjWNPb-4
|
|
Acceptance criteria
|
|
|
01
|
Scenario: Accessing the Forecast Field Given: Processes list page in CRM When: Click on the field “Forecast” Then: Have the ability to change it
|
|
|
02
|
Scenario: Changing the Forecast by admin Given: Open editor of the field forecast as admin When: Change the number And: Click apply  Then: Forecast is changed
|
|
|
03
|
Scenario: Changing the Forecast by responsible Given: Open editor of the field forecast as responsible When: Change the number And: Click apply  Then: Forecast is changed
|
|
|
04
|
Scenario: Changing the Forecast by NOT responsible Given: process list page as consultant When: click on forecast where you not responsible Then: there is not possibility to change it
|
|
|
05
|
Scenario: Changing the Forecast by business manager Given: Open editor of the field forecast as business manager of responsible unit When: Change the number And: Click apply  Then: Forecast is changed
|
|
|
06
|
Scenario: Changing the Forecast by business manager but for NOT responsible from your unit Given: process list page as business manager When: click on forecast from responsible of other unit Then: there is not possibility to change it
|
|
|
07
|
Scenario: Changing the Forecast by division Given: Open editor of the field forecast as division of responsible group When: Change the number And: Click apply  Then: Forecast is changed
|
|
|
08
|
Scenario: Changing the Forecast by division but for NOT responsible from your group Given: process list page as division When: click on forecast from responsible of other division Then: there is not possibility to change it
|
|
|
09
|
Scenario: Default Budget Display Given: Processes list page in CRM Then: See the budget calculated by default from Desired salary (green numbers)
|
|
|
09a
|
Scenario: show Job model “Default” forecast Given: Processes list page in CRM When: see process with “Default“ Job model vacancy Then: see green numbers calculated by formula:
18%: desired salary <= 100000 20%: 100000 < desired salary <= 130000 25%: desired salary > 130000
Example 1: desired Salary 9000 Then Default = 9000*0.18
Example 2: desired Salary 110000 Then Default = 110000*0.2
Example 3: desired Salary 150000 Then Default = 150000*0.25
|
|
|
09b
|
Scenario: show Job model “PaaS” forecast Given: Processes list page in CRM When: see process with “PaaS“ Job model vacancy Then: see green numbers calculated by formula:
18%: desired salary <= 100000 20%: 100000 < desired salary
Example 1: desired Salary 50000 Then Default = 50000*0.18
Example 2: desired Salary 120000 Then Default = 120000*0.2
|
|
|
09c
|
Scenario: show Job model “Executive” forecast Given: Processes list page in CRM When: see process with “Executive“ Job model vacancy Then: see green numbers calculated by formula:
desired salary * 33%
Example: desired Salary 50000 Then Default = 50000*0.33
|
|
|
10
|
Scenario: Forecast calculation starts from Interview 2 status Given the process status has changed to "Interview 2," When the candidate reaches this stage, Then the forecast calculation starts from this moment as it’s more likely that the candidate has a good chance to be rocked (calculating based on desired salary).
|
|
|
11
|
Scenario: Current salary field must not mandatory Given the candidate is filling out their details in interview or RT, When they are prompted for their salary details, Then the "Current salary" field should still be visible and optional in CRM, Rocken Talent, and Interviews (current salary is not in the formula of forecast).
|
|
|
12
|
Scenario: Desired salary field remains mandatory Given a candidate is filling out personal information, When they are asked to provide their salary expectations, Then the "Desired salary" field should be mandatory in CRM, Rocken Talent, and Interviews.
|
https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=63570-75948&t=fUEcewBHWR0XzBA4-4
|
Leave a Reply
You must be logged in to post a comment.