Content
General info
To provide flexibility in managing vacancies, Orders should be made non-mandatory fields. This change will allow for the creation and management of vacancies without requiring an Order field, streamlining processes where an Order might not be applicable. Specific actions related to Vacancies and Publications should be reviewed to ensure consistent handling of the Order field when it is not provided.
Review these actions:
-
ChangeVacancyOrder
-
CloneVacancy
-
CreateVacancy – if Admin/BusinessManager creates -> should be send from the Front
-
Consultant/DivisionHead (if consultant in order than get from the order)
-
CreatePublicationFromVacancy
-
CreatePublication
-
ChangePublicationRecruiter – there is a order check (you can’t change the recruiter if there is a order) when you change the recruiter in the order changes for all publications
-
ChangePublicationVacancy – just changes (no order checks and does not change the recruiter as in the previous action)
User story
As a CRM user
I want to create/manage vacancies and publications without requiring the Order field
So that I have more flexibility in handling vacancy- and publications-related actions where an Order might not be necessary, and add vacancies and publications to companies without order
Visual design:
–
|
|
Acceptance criteria
|
|
|
01
|
Scenario: Create Vacancy Given CRM user is creating a vacancy When they see field Company (mandatory) AND don’t see field Order AND select company Then see the field Order below the company field (not mandatory) AND order field include only orders related to this company
|
currently:

|
|
02
|
Scenario: Create Publication Given CRM user is creating a publication When they see field Company (mandatory) AND disabled Order and Vacancy AND select company Then see the field Order below the company field (not mandatory) AND see the field Vacancy below the Order field (not mandatory) AND order field include only orders related to this company AND vacancy field include only vacancies related to this company
|
currently:

|
|
03
|
OOS Scenario: Change Order in Vacancy edit mode Given a user wants to change the Order for a vacancy When they open vacancy edit mode AND see disabled company field (if ould clone or create new vacancy) AND open dropdown with orders that related to the company in the vacancy AND select other order of this company AND save the vacancy Then order field is updated in the vacancy
|
currently:

|
|
04
|
OOS Scenario: Change Order in Publication edit mode Given a user wants to change the Order for a publication When they open publication edit mode AND see disabled company field (ld create new publication) AND open dropdown with orders that related to the company in the publication AND select other order of this company AND save the publication Then order field is updated in the publication
|
|
|
05
|
OOS Scenario: Change Publication related to a Vacancy with Order Given a publication is linked to a vacancy with Order When the user changes the order in publication AND click save changes Then the publication should be updated AND vacancy shation
|
currently:

|
|
06
|
OOS Scenario: ADD Publication related to a Vacancy without Order Given a publication is linked to a vacancy without an Order
AND click save changes Then the publication should be updated AND vacancy should remain without the order as it was before creating the publication
|
currently:

|
|
07
|
OOS Scenario: Clone Vacancy without Order Given a user is cloning a vacancy that does not have an Order When the CloneVacancy action is performed Then the vacancy should be cloned successfully, inheriting the same non-mandatory status for the Order field.
|
|
|
08
|
OOS Scenario: Change company during cloning of the Vacancy with order Given a user is cloning a vacancy with intention to create the same vacancy but for other company When the CloneVacancy action is performed AND user can select other company Then order field is cleared because user should select only orders from new selected company
|
|
|
09
|
Scenario: Change Recruiter in Publication with Order Given a publication has an assigned Order and recruiter When a user tries to change the recruiter AND save changes Then current error should be shown as it is
|
Currently:

|
|
10
|
Scenario: Change Recruiter in Publication without Order Given a publication without Order has an assigned recruiter When a user tries to change the recruiter Then recruiter can be successfully changed
|
|
Leave a Reply
You must be logged in to post a comment.