01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then:

01

Scenario: Opening the Filters panel
Given I am on the application 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 such as

1. Title / Titel

2. Applicant / ???

3. Company / ???

4. OOS Keyword / Keyword

5. Status / Status

6. Recruiter / Recruiter

7. Creation Date / Erstellungdatum

8. Application Source / Bewerbungsquelle

9. Categories / Kategorien

10. OOS Country / Land

02

Scenario: User interact with the filter panel
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

https://api.staging.rockengroup.com/api-documentation-2000#/Application/get_api_v1_applications

01

Title

Scenario: User interact with the field
Given user in filter panel,
When search some items (publication title)
Then have common behaviour of the field described here: Story 1.0.12.6. CRM. Title field filter

titles[]

02

Applicant

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

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags

03

Company

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

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags

04

Keyword OOS

Scenario: User applies a keyword filter.
Given the user enters a custom keyword,
When it is find info in any application 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

search by all fields in applications

05

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

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

statuses[]

Available values :

• new / neu

• applied / beantragt

• rejected / abgelehnt

• interview / Vorstellungsgespräch

• unfinished / unvollständig

• not relevant / nicht relevant

06

Recruiter

Scenario: User applies recruiter filter.
Given available recruiter option,
When one recruiter is selected,
Then results filter accordingly this user.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

recruiters[]

07

Creation Date

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

from_date

to_date

08

Application Source

Scenario: User applies an Application Source filter.
Given the user types a source,
When matches exist,
Then suggestions are displayed.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

platforms[]

09

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[]

10

Country OOS

Scenario: User filters by country.
Given country options exist,
When one is selected,
Then only profiles 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

01

Scenario: Display application list table
Given the user is on the Applications List View page
When the page loads
Then the system should display a table with columns for "Status", "Date", "Applicant", "Current Position", "Publication" with country flag, "Categories", "Recruiter”, and "Platform".

01a

Scenario: Default pre-filter for "New"
Given a user accesses the Applications page
When the page loads
Then the pre-filter for the status "New" is automatically applied, showing only applications with this status.

01b

Scenario: Modify the pre-filter
Given the user views applications with the status "New"
When the user removes the pre-filter or selects additional statuses in the Filters panel
Then the page updates to display applications matching the updated filter criteria.

02

Scenario: Paginate application list
Given the user is viewing the Applications List Table
When there are more applications than can fit on a single page
Then the system should provide pagination controls to navigate through the list of applications.

03

Scenario: View application details
Given the user is viewing the Applications List Table
When the user clicks on an application row
Then the system should expand the detailed view of the selected application separated into tabs: Primary, Client brief, Personal, Applications

04

Scenario: Sort applications by column
Given the user is viewing the Applications List Table
When the user clicks on a column header (status, date, platform)
Then the system should sort the list of applications based on the selected column in either ascending or descending order.

05

Scenario: Filter applications by platform
Given the user is viewing the Applications List Table
When the user applies a filter for "Platform"
Then the system should display only the applications associated with the selected platform(s).

06

Scenario: View Rocken Jobs applications
Given the user is viewing the Applications List Table
When the list is loaded
Then the system should display only applications from Rocken Jobs.

07

Scenario: View primary tab in expanded application
Given the user has expanded an application
When the "Primary" tab is selected
Then the system should display two sections: "Publication Condition" and "Attachments".
And "Publication Condition" should include details like Experience Level, Position, Workload, Employment Type, Salary Range, Start Date, Age, Degree, and Travel.
And there should be a "Reject" button to reject the application.
And the section should include links to the Publication and Vacancy.
And in the "Attachments" section, the user should have the ability to attach files, delete files with a prompt, and view any attached files.

08

Scenario: View client brief tab in expanded application
Given the user has expanded an application
When the "Client Brief" tab is selected
Then the system should display three sections: "Requirement List", "General Cooperation", and "Order Timeline".
And the "Requirement List" should include details like Order Name, Direct Link, Company, Contact Person, Application By, Job Model, Remuneration, and Guarantee.
And the "General Cooperation" should include details like Idea of Collaboration, Expectations and No-gos, Where Particular Need, Process, Follow-up Projects, Seniority, Experience Level, Technologies, Work History, Salary Range, Team Size, Reason of Staffing, Additional Needs, and Important Human Qualities.
And the "Order Timeline" should include details like Current Step, Deadline, Next Task In, and a timeline link to a modal with the full timeline.
And there should be a "Reject" button to reject the application.

09

Scenario: View Personal tab in expanded application
Given the user has expanded an application
When the "Personal" tab is selected
Then the system should display details including Applicant Name, Gender, Current Position, E-mail, Phone Number, External Link, and a "Send SMS" button.
And the system should include a checkbox labeled "Active Source".
And there should be a "Reject" button to reject the application.

10

Scenario: View Applications tab in expanded application
Given the user has expanded an application
When the "Applications" tab is selected
Then the system should display a table of other applications made by the candidate.
And there should be a "Reject" button to reject the application.

11

Scenario: Displaying Notes tab
Given I am in the Application section,
When I view the application,
Then I should see 5th Notes tab.

Story 1.5.5.10. CRM. Application. Tab notes

01

Scenario: Display editable fields in Section 1
Given the user is in the Publication Edit Mode, Tab Primary
When the user views Section 1
Then the system should display editable fields for "Company/Order" (that related to Country), "Client (Company)", and "Staff".

02

Scenario: Display editable fields in Section 2
Given the user is in the Publication Edit Mode, Tab Primary
When the user views Section 2
Then the system should display editable fields for "Vacancy", "Publication Name", "Recruiter", and "Industries".

03

Scenario: Save changes
Given the user has made edits to the fields in the Tab Primary
When the user clicks the "Save" button
Then the system should save the changes and update the publication information accordingly.

04

Scenario: Cancel changes
Given the user is editing the Tab Primary
When the user clicks the "Cancel" button
Then any unsaved changes should be discarded, and the publication details should remain unchanged.

05

Scenario: Validate required fields
Given the user is saving changes in the Tab Primary
When any required fields are left empty
Then the system should prompt the user to fill in the missing information before saving.

06

Scenario: Attach vacancy only with the same order
Given publication has an order
When I want to add or change the vacancy
Then see in the dropdown only vacancies with the same order

07

Scenario: Display all active vacancies when no order is attached
Given a publication has no attached order,
When I open the publication in edit mode,
Then I should see all active vacancies of the company in the dropdown for vacancy selection.

08

Scenario: Automatically attach order when adding vacancy with an order
Given a publication is in edit mode and I add a vacancy with an order,
When I select a vacancy that has an order,
Then the order should automatically be attached to the publication.

01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then:

01

Scenario: Employment type selection
Given the recruiter is in the Employment Conditions section
When they select employment types such as Full-Time, Part-Time, Temporary, or Permanent
Then the selected types are saved and displayed in the publication.

02

Scenario: Workload range
Given the recruiter is editing the Workload field
When they adjust the range using the slider
Then the selected workload range is saved and displayed as a percentage (e.g., 80–100%).

03

Scenario: Salary range
Given the recruiter is editing the Salary Range field
When they input minimum and maximum values
Then the salary is displayed in the format CHF/Year (e.g., 100,000–120,000 CHF/Year).

04

Scenario: Start date
Given the recruiter is editing the Start Date field
When they select a date using the calendar or mark Immediate Start
Then the start date is saved and displayed in the publication.

05

Scenario: Position selection
Given the recruiter is selecting the Position
When they choose options such as Specialist, Professional, or Executive
Then the selected position is saved and reflected in the publication.

06

Scenario: Experience level
Given the recruiter is selecting the Experience Level
When they choose options such as Junior, Professional, Senior, or Executive
Then the selected experience level is saved and displayed.

07

Scenario: Travel preferences
Given the recruiter is setting Travel preferences
When they select options such as Switzerland, DACH Region, Europe, or Worldwide
Then the travel requirements are saved and displayed.

08

Scenario: Working model
Given the recruiter is selecting the Working Model
When they choose options such as Home Office, Remote Work, Hybrid, or On-Site
Then the working model is saved and reflected in the publication.

09

Scenario: Leading experience
Given the recruiter is selecting the Leading Experience
When they choose options such as None, Professional Guidance of Employees, or Management of Project Teams
Then the selection is saved and displayed.

10

Scenario: Locations
Given the recruiter is editing the Locations field
When they choose a specific location or select All Cities
Then the selected location(s) are saved and displayed.

11

Scenario: Degree selection
Given the recruiter is selecting Degrees
When they choose options such as Bachelor, Master, or Federal Diploma
Then the selected degrees are saved and reflected in the publication.

12

Scenario: Default selection for team size
Given the recruiter is editing the Team Size field
When they open the field
Then the default selection is "Unknown" (EN) / "Unbekannt" (DE).

13

Scenario: Updating team size
Given the recruiter has selected a specific team size (e.g., 1–15, 30+)
When they save the publication
Then the selected team size is saved and displayed in the publication.

14

Scenario: No display for "Unknown" in publication preview
Given the team size is set to "Unknown"
When the publication is displayed in the Publication Preview in RJ
Then the Team Size field is hidden and not shown.

15

Scenario: Display for defined team sizes
Given a specific team size is selected
When the publication is displayed in the Publication Preview in RJ
Then the selected team size is displayed as part of the publication.

16

Scenario: Language addition
Given the recruiter is adding Languages
When they click + Add Language and input language details
Then the selected languages are saved and displayed in the publication.

01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then:

01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then:

01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then:

01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then: