Requirement Gathering

C

A

C

C

I

C

I

I

I

I

Backlog Management

C

A

R

I

I

C

I

I

I

I

Documentation Scope

C

A

R

C

I

C

I

I

I

I

Sprint Planning

C

A

R

I

R

I

R

R

R

R

Development (Backend)

A

C

I

С

C

I

R

С

I

I

Development (Front-end)

A

C

I

С

I

I

R

R

I

I

Manual Testing

A

C

I

С

I

I

C

C

R

R

Automation Testing

A

C

I

I

C

I

C

C

C

R

Design creation

C

A

C

R

I

C

C

C

I

I

Design Implementation

C

A

C

R

I

C

C

R

I

I

DevOps Activities

A

C

I

I

R

I

С

С

I

C

Release Management

C

A

R

I

R

I

R

R

C

C

Sprint Reviews

C

A

C

C

R

I

R

R

C

C

Retrospectives

I

A

R

C

C

I

C

C

R

R

Marketing Activities

C

C

I

C

I

A+R

I

I

I

I

Active search (default)

Active

Passive search (if manually switched by candidate)

Active

Offline

New, Rejection, In Progress, Interview, Offline

01

Scenario: Synchronizing Active Search Status
Given a profile is in "Active search" status in RT
When the profile is viewed in CRM
Then the CRM status should show as "Active."

02

Scenario: Synchronizing Passive Search Status
Given a profile is in "Passive search" status in RT
When the profile is viewed in CRM
Then the CRM status should show as "Active."

03

Scenario: Synchronizing Offline Status
Given a profile is in "Offline" status in RT
When the profile is viewed in CRM
Then the CRM status should be mapped to either "New," "Rejection," "In Progress," "Interview," or "Offline" based on the candidate’s latest action.

Active search (default)

Active

Passive search (if manually switched by candidate)

Active

Offline

New, Rejection, In Progress, Interview, Offline

01

Component

Scenario: User applies a title filter.
Given the user enters a title,
When the title exists,
Then suggestions are displayed.

Scenario: User applies a title not in suggestions.
Given the user enters a title,
When the user presses "Enter,"
Then the input is accepted as custom.

Select type:

• multi select OOS

• multi tags

• search OOS

• suggestions

• custom tags

titles[]

02

Keyword

Scenario: User applies a keyword filter.
Given the user enters a custom keyword,
When it is find info in any vacancy fields without suggestions
AND data matches with keyword ,
Then relevant results are displayed

Select type:

• multi select OOS

• multi tags

• search OOS

• suggestions OOS

• custom tags

keywords[]

Search by fields:

• Name of the vacancy

• Descriptions: Introduction, Description, Responsibilities

• Name of the Company

• Skills

• Locations

03

Status

Scenario: User applies a status filter.
Given the user selects a status,
When the selection is made,
Then the results reflect the selected status.

Select type: multi select, with search and suggestions, without custom tags

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

statuses[]

Options:

• New / Neu

• Active / Aktiv

• On hold / On hold

• Inactive / Inaktiv

• Rocked / Rocked

04

Business Unit

Scenario: User filters by business unit.
Given business units exist,
When one is selected,
Then results match the selection.

Select type: multi select, with search and suggestions, without custom tags

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

business_units[]

05

Consultant

Scenario: User applies a consultant filter.
Given consultant options exist,
When one is selected,
Then results show jobs managed by the consultant.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

consultants[]

06

Created Date

Scenario: User applies a date range.
Given the user selects "From" and "To" dates,
When dates are valid,
Then results are filtered by the date range.

date_range[]

Placeholders:

From / Von

To / Bis

07

Location

Scenario: User applies a location filter.
Given the user enters a location (city),
When matched cities exist,
Then suggestions are displayed.

Select type: single select, search and suggestions, without custom tags

Select type:

• single select

• single tag

• search

• suggestions

• custom tags OOS

location

08

Search Radius

Scenario: User filters by search radius.
Given a numeric input field,
When a radius is entered,
Then results match the specified area that related to selected “Location“.

search_radius

09

Company

Scenario: User applies a company filter.
Given the user types a company name,
When matches exist,
Then suggestions are displayed.

Select type: multi select, with search and suggestions, without custom tags

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

companies[]

10

Industries

Scenario: User applies an industry filter.
Given the user types an industry,
When matches exist,
Then suggestions are displayed.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

industries[]

11

Category

Scenario: User applies a category filter.
Given the user types a category,
When matches exist,
Then suggestions are displayed.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

categories[]

12

Skills

Scenario: User applies a skill filter.
Given the user enters a skill,
When matches exist,
Then suggestions are displayed.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

skills[]

13

Experience Level

Scenario: User filters by experience level.
Given experience levels,
When one or more levels are selected,
Then results show matching requirements.

Select type: multi select, without search and suggestions, without custom tags

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

experiences_level[]

Options:

• Junior / Junior

• Professional / Professional

• Senior / Senior

• Executive / Executive

14

Employment Type

Scenario: User filters by employment type.
Given available options,
When a type is selected,
Then results reflect the chosen type.

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

employments[]

Options:

• Full time / Vollzeit

• Permanent / Festanstellung

• Part-time / Teilzeit

• Temporary / Temporär

15

Degrees

Scenario: User filters by degree type.
Given degree options exist,
When one or more are selected,
Then results show relevant vacancies.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

degrees[]

Options:

• Master / Master (Hochschule)

• Bachelor / Bachelor (Hochschule)

• Diploma DAS / Diploma of Advanced Studies DAS

• Gymnasium / Gymnasium

• Federal Professional Certificate / Eidg. Fachausweis

• Certificate CAS / Certificate of Advanced Studies CAS

• Master MAS / Master of Advanced Studies MAS

• Doctorate / Doktorat

• Secondary technical school / Fachmittelschule

• Basic vocational training (apprenticeship) EFZ / Berufliche Grundbildung (Lehre) EFZ

• Higher technical college HF / Höhere Fachschule HF

• Federal Diploma / Eidg. Diplom

• Vocational Baccalaureate / Berufsmaturität

• MBA / MBA

16

Process Type

Scenario: User applies process type filter.
Given process types exist,
When one is selected,
Then results match the selection.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

No API, just Front Enum options

Options:

• Email / E-Mail

• Download / Download

17

Job Model

Scenario: User applies a job model filter.
Given job models exist,
When one is selected,
Then results match the selected model.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

No API, just Front Enum options

Options:

• Default / Standard

• PaaS / PaaS

• Executive / Executive

18

Salary Range

Scenario: User filters by salary range.
Given the user inputs "From" and "To" values,
When valid,
Then results show jobs in the range.

salary_range_from

salary_range_to

Placeholders:

From / Von

To / Bis

19

Start Date

Scenario: User filters by start date.
Given a valid date picker,
When a date is selected,
Then jobs starting after the date are displayed.

start_date

20

Remote Work

Scenario: User filters for remote jobs.
Given remote work options,
When selected,
Then only remote type jobs are shown.

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

remote_work_types[]

Options:

• Undefined / Undefiniert

• Home office / Home office

• Remote Work / Remote

• Hybrid / Hybrid

• On-Site / On-Site

21

Position

Scenario: User applies a position filter.
Given position options exist,
When one is selected,
Then it filters jobs with that position.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

No API, just Front Enum options

Options:

• Specialist / Fachposition

• Professional / Führungsposition

• Executive / Executive

22

Leading Experience

Scenario: User applies a leadership experience filter.
Given experience levels exist,
When one is selected,
Then relevant jobs are displayed.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

There is API: leading_experience
BUT using: Front Enum options

Options:

• None / Keine

• Professional guidance of employees / Fachliche Führung von Mitarbeitenden

• Management of project teams / Führung von Projektteams

• Personal leadership experience / Personelle Führungserfahrung

23

Languages

Scenario: User filters by language.
Given language options exist,
When one is selected,
Then results reflect vacancies requiring that language.

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

languages[]

24

Workload

Scenario: User filters by workload.
Given Slider exist,
When select some workload,
Then results match the range.

workload[]

0-100%

25

CRM users/SPOC

Scenario: User applies CRM user / SPOC filter.
Given available CRM user / SPOC option,
When one Single person of contact or CRM user is selected,
Then results filter accordingly this user.

Select type:

• single select

• single tag

• search

• suggestions

• custom tags OOS

spoc[]

26

Reserved

Scenario: User filters for reserved jobs.
Given a reserved filter fields,
When selected “yes”,
Then only reserved jobs are displayed.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

reserved

Options:

• yes / ja

• no / nein

27

OOS Country

Scenario: User filters by country.
Given country options exist,
When one is selected,
Then only jobs in that country are displayed.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

should be added to API by backend developer

Options:

• Switzerland / Schweiz

• Germany / Deutschland

01

Scenario: User applies a title filter.
Given the user enters a title,
When the title exists,
Then suggestions are not displayed.

02

Scenario: User applies a custom title
Given the user enters a title,
When the user presses "Enter,"
Then the input is accepted as custom.

03

Scenario: User interact with the field
Given user in filter panel,
When clear/add/search some items
Then have common behaviour of the field described here: Story 1.0.12.5. CRM. Filter panel

01

Scenario: Opening the Filters panel
Given I am on the List page
When I click on the "Filters" link
Then the filters panel should open on the right side of the screen, displaying filter options

01a

Scenario: Closing Filters panel
Given I opened filters panel
When hover on the arrow icon or “Filters“ text
AND click on icon or on the text
Then the filters panel should closer

02

Scenario: Applying filters
Given the filters panel is open
When I select values in filter fields (e.g., entering keywords, selecting skills)
Then the list should update to show only information that match the selected filter criteria.
AND I can see a spinner before the page is reacted to the filter

03

Scenario: Applying non-suggested keywords
Given I have entered a keyword that is not part of the suggested list
When I press the "Enter" key
Then the filter should accept this keyword, and the list should update accordingly.

https://cheitgroup.atlassian.net/wiki/spaces/RD/pages/845152315/Story+1.0.12.1.+CRM.+Filter+component.+Select+with+autosuggest?atl_f=PAGETREE

04

Scenario: Clearing individual filter tags
Given I have applied filters
When I hover on the tag
AND click "x" on the tag or on tag
Then that specific filter should be removed, and the list should update accordingly.

05

Scenario: Clearing individual filters
Given I have applied filters
When I click "Clear" next to any filter field
Then that specific filter should be removed, and the list should update accordingly.

05a

Scenario: Appear Clearing individual filters
Given I don’t have applied tags/filters in the component
When applied at least one tag/filter
Then see the “clear“ link next the field in the component

06

Scenario: Clearing all filters
Given I have applied multiple filters
When I click "Clear all" at the top of the filters panel
Then all applied filters should be removed, and the list should reset to display all vacancies.

06a

Scenario: Appear Clearing all filters
Given I don’t have applied any filters on the page
When applied at least one filter
Then see the “clear all“ link in filter section

07

OOS Scenario: Persistent Filters

Given: I have applied filters to the list table,

When: I navigate away from the page and return later,

Then: the previously applied filters should persist,

AND the table should display the filtered list as per the last set.

08

Scenario: Apply date range filter
Given I am on the list page
When I set a date range using "From-To" component
Then the system displays information that were created within the selected date range.

https://cheitgroup.atlassian.net/wiki/spaces/RD/pages/853475329/Story+1.0.12.3.+CRM.+Filter+component.+Simple+Date+Picker+From-To?atl_f=PAGETREE

didn’t do this component, we are using date picker for apply ranges

09

Scenario: Filter no results 

Given the user inputs invalid data into a filter field (e.g., end date before start date) or enter not matching data

When the filters are applied automatically

Then the system should display an appropriate message on a page

10

OOS Scenario: Prefilter by your country

Given: I German CRM user,

When: I open the list page

Then: see only information from Germany (prefilter) with a flag close to the name

11

Scenario: Displaying applied filters
Given I have applied filters,
When I view the List page,
Then the applied filters should be displayed directly under the title of the page.

12

Scenario: Clearing all filters
Given I have applied filters,
When I click the "Clear all" option,
Then all filters should be cleared and the page should display all entities without any applied filters.

13

Scenario: Clearing a single filter
Given I have applied multiple filters,
When I click the “x“ (clear) option for a single filter,
Then only that specific filter should be cleared, and the other filters should remain applied.

https://api.staging.rockengroup.com/api-documentation-2000#/Vacancy/get_api_v1_vacancies

01

Title

Scenario: User applies a job title filter.
Given the user enters a title,
When the title exists,
Then suggestions are displayed.

Scenario: User applies a title not in suggestions.
Given the user enters a title,
When the user presses "Enter,"
Then the input is accepted as custom.

Select type:

• multi select OOS

• multi tags

• search OOS

• suggestions OOS

• custom tags

titles[]

02

Keyword

Scenario: User applies a keyword filter.
Given the user enters a custom keyword,
When it is find info in any vacancy fields without suggestions
AND data matches with keyword ,
Then relevant results are displayed

Select type:

• multi select OOS

• multi tags

• search OOS

• suggestions OOS

• custom tags

keywords[]

Search by fields:

• Name of the vacancy

• Descriptions: Introduction, Description, Responsibilities

• Name of the Company

• Skills

• Locations

03

Status

Scenario: User applies a status filter.
Given the user selects a status,
When the selection is made,
Then the results reflect the selected status.

Select type: multi select, with search and suggestions, without custom tags

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

statuses[]

Options:

• New / Neu

• Active / Aktiv

• On hold / On hold

• Inactive / Inaktiv

• Rocked / Rocked

04

Business Unit

Scenario: User filters by business unit.
Given business units exist,
When one is selected,
Then results match the selection.

Select type: multi select, with search and suggestions, without custom tags

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

business_units[]

05

Consultant

Scenario: User applies a consultant filter.
Given consultant options exist,
When one is selected,
Then results show jobs managed by the consultant.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

consultants[]

06

Created Date

Scenario: User applies a date range.
Given the user selects "From" and "To" dates,
When dates are valid,
Then results are filtered by the date range.

date_range[]

Placeholders:

From / Von

To / Bis

07

Location

Scenario: User applies a location filter.
Given the user enters a location (city),
When matched cities exist,
Then suggestions are displayed.

Select type: single select, search and suggestions, without custom tags

Select type:

• single select

• single tag

• search

• suggestions

• custom tags OOS

location

08

Search Radius

Scenario: User filters by search radius.
Given a numeric input field,
When a radius is entered,
Then results match the specified area that related to selected “Location“.

search_radius

09

Company

Scenario: User applies a company filter.
Given the user types a company name,
When matches exist,
Then suggestions are displayed.

Select type: multi select, with search and suggestions, without custom tags

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

companies[]

10

Industries

Scenario: User applies an industry filter.
Given the user types an industry,
When matches exist,
Then suggestions are displayed.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

industries[]

11

Category

Scenario: User applies a category filter.
Given the user types a category,
When matches exist,
Then suggestions are displayed.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

categories[]

12

Skills

Scenario: User applies a skill filter.
Given the user enters a skill,
When matches exist,
Then suggestions are displayed.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

skills[]

13

Experience Level

Scenario: User filters by experience level.
Given experience levels,
When one or more levels are selected,
Then results show matching requirements.

Select type: multi select, without search and suggestions, without custom tags

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

experiences_level[]

Options:

• Junior / Junior

• Professional / Professional

• Senior / Senior

• Executive / Executive

14

Employment Type

Scenario: User filters by employment type.
Given available options,
When a type is selected,
Then results reflect the chosen type.

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

employments[]

Options:

• Full time / Vollzeit

• Permanent / Festanstellung

• Part-time / Teilzeit

• Temporary / Temporär

15

Degrees

Scenario: User filters by degree type.
Given degree options exist,
When one or more are selected,
Then results show relevant vacancies.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

degrees[]

Options:

• Master / Master (Hochschule)

• Bachelor / Bachelor (Hochschule)

• Diploma DAS / Diploma of Advanced Studies DAS

• Gymnasium / Gymnasium

• Federal Professional Certificate / Eidg. Fachausweis

• Certificate CAS / Certificate of Advanced Studies CAS

• Master MAS / Master of Advanced Studies MAS

• Doctorate / Doktorat

• Secondary technical school / Fachmittelschule

• Basic vocational training (apprenticeship) EFZ / Berufliche Grundbildung (Lehre) EFZ

• Higher technical college HF / Höhere Fachschule HF

• Federal Diploma / Eidg. Diplom

• Vocational Baccalaureate / Berufsmaturität

• MBA / MBA

16

Process Type

Scenario: User applies process type filter.
Given process types exist,
When one is selected,
Then results match the selection.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

No API, just Front Enum options

Options:

• Email / E-Mail

• Download / Download

17

Job Model

Scenario: User applies a job model filter.
Given job models exist,
When one is selected,
Then results match the selected model.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

No API, just Front Enum options

Options:

• Default / Standard

• PaaS / PaaS

• Executive / Executive

18

Salary Range

Scenario: User filters by salary range.
Given the user inputs "From" and "To" values,
When valid,
Then results show jobs in the range.

salary_range_from

salary_range_to

Placeholders:

From / Von

To / Bis

19

Start Date

Scenario: User filters by start date.
Given a valid date picker,
When a date is selected,
Then jobs starting after the date are displayed.

start_date

20

Remote Work

Scenario: User filters for remote jobs.
Given remote work options,
When selected,
Then only remote type jobs are shown.

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

remote_work_types[]

Options:

• Undefined / Undefiniert

• Home office / Home office

• Remote Work / Remote

• Hybrid / Hybrid

• On-Site / On-Site

21

Position

Scenario: User applies a position filter.
Given position options exist,
When one is selected,
Then it filters jobs with that position.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

No API, just Front Enum options

Options:

• Specialist / Fachposition

• Professional / Führungsposition

• Executive / Executive

22

Leading Experience

Scenario: User applies a leadership experience filter.
Given experience levels exist,
When one is selected,
Then relevant jobs are displayed.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

There is API: leading_experience
BUT using: Front Enum options

Options:

• None / Keine

• Professional guidance of employees / Fachliche Führung von Mitarbeitenden

• Management of project teams / Führung von Projektteams

• Personal leadership experience / Personelle Führungserfahrung

23

Languages

Scenario: User filters by language.
Given language options exist,
When one is selected,
Then results reflect vacancies requiring that language.

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

languages[]

24

Workload

Scenario: User filters by workload.
Given Slider exist,
When select some workload,
Then results match the range.

workload[]

0-100%

25

CRM users/SPOC

Scenario: User applies CRM user / SPOC filter.
Given available CRM user / SPOC option,
When one Single person of contact or CRM user is selected,
Then results filter accordingly this user.

Select type:

• single select

• single tag

• search

• suggestions

• custom tags OOS

spoc[]

26

Reserved

Scenario: User filters for reserved jobs.
Given a reserved filter fields,
When selected “yes”,
Then only reserved jobs are displayed.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

reserved

Options:

• yes / ja

• no / nein

27

OOS Country

Scenario: User filters by country.
Given country options exist,
When one is selected,
Then only jobs in that country are displayed.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

should be added to API by backend developer

Options:

• Switzerland / Schweiz

• Germany / Deutschland

01

Scenario: Reassigning an applicant
Given a recruiter or Head of Recruiting is viewing an applicant’s profile in the CRM
When they select the option to reassign the applicant
Then a modal with dropdown available to select recruiters.

02

Scenario: Selecting a new recruiter
Given the dropdown of recruiters is displayed
When the user selects a new recruiter
AND click button “Save”
Then the system updates the applicant’s assigned recruiter to the selected individual.

03

Scenario: Cancel selection
Given the dropdown of recruiters is displayed
When the user selects a new recruiter
AND click button “Cancel”
Then the modal is closed without any updates

04

OOS Scenario: Notification of reassignment
Given an applicant is reassigned to a new recruiter
When the reassignment is completed
Then the new recruiter receives a notification in the CRM about the reassignment.

05

Scenario: Audit trail
Given an applicant is reassigned
When the reassignment is saved
Then the system logs the change in the applicant’s history, including the previous recruiter, new recruiter, and timestamp (Profile – Primary – Activity)

06

OOS Scenario: Reassigning multiple applicants
Given a recruiter or manager is managing a list of applicants
When they select multiple applicants and use the bulk reassign option
Then the system updates all selected applicants to the new recruiter.

07

OOS Scenario: Default recruiter validation
Given an applicant is in "New" or "Reapplied" status
When they are not assigned to any recruiter
Then the system defaults the assignment to the Head of Recruiting.

08

Scenario: Role-based access
Given a user is attempting to reassign applicants
When they do not have the required permissions (HoR role or Admin)
Then the system don’t show reassignment functionality.

09

OOS Scenario: Undo reassignment
Given an applicant has been reassigned
When the user realizes a mistake
Then the system allows them to undo the reassignment and restore the previous recruiter within a limited timeframe (e.g., 1 minute).

01

Scenario: Status options displayed
Given a recruiter is managing an applicant in the CRM
When they open the status selection dropdown
Then the following status options are displayed: "New," "Unfinished," "Reapplied," "In Progress," "Interview," "Rejection," and "Rejection Deletion."

02

Scenario: Default status “New”
Given a new applicant submits their application
When the application is added to the CRM
Then the default status is set to "New."

03

OOS Scenario: Status update manually
Given a recruiter is reviewing an application
When they change the applicant’s status
Then the system saves and displays the updated status in the application list and details view.

04

Scenario: Filtering by status
Given multiple applications in the system
When a recruiter uses the status filter in the applications view
Then they can filter applications based on all available statuses, including the newly added ones.

05

Scenario: Unfinished status
Given a candidate applies on Rocken Jobs
When the application is submitted without attached documents
Then the system automatically assigns the status "Unfinished."

06

Scenario: New status
Given a candidate applies on Rocken Jobs
When the application is submitted with all required documents attached and all steps are completed
Then the system automatically assigns the status "New."

07

Scenario: Reapplied status
Given a candidate has been previously rejected
When they apply to the same position again using the same email
Then the system automatically assigns the status "Reapplied."

08

Scenario: In Progress status
Given a recruiter starts the hiring process for an applicant
When they move the applicant to the next step in the CRM (send interview)
Then the system assigns the status "In Progress."

09

Scenario: Interview status
Given a recruiter schedules or conducts interviews as part of the hiring process
When the applicant complete interview
Then the system assigns the status "Interview."

10

Scenario: Rejection status
Given a recruiter decides to reject an applicant
When they select a rejection reason in the system
Then the system assigns the status "Rejection" and logs the reason for future reference.

11

Scenario: Rejection Deletion status
Given an applicant has been rejected
When the recruiter deletes the application from the system
Then the system assigns the status "Rejection Deletion" and logs the action for audit purposes.