Story 1.2.1.2. CRM. Vacancy list filters

Content

General info

This story focuses on the functionality to filter the vacancy list based on various criteria, such as status, process type, company, category, consultant, etc. Users can apply multiple filters simultaneously to narrow down the list of vacancies.

Feature: CRM – Vacancy List Filters
Scope: Allow users to apply specific filters to narrow down vacancy results based on various criteria in the new design.

Investigation: 2024-08 Search Queries for Candidate Search

User story

As a CRM user,
I want to filter the vacancy list using various criteria,
So that I can quickly find relevant vacancies based on specific requirements.

Visual design:

https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=57218-10562&t=aLfLqWjgjni4WYGn-4

Acceptance criteria

01

Scenario: Opening the Filters panel
Given I am on the Vacancy 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. Keyword / Keyword

  3. Status / Status

  4. Business Unit / Business Unit

  5. Consultant Responsible / Consultant Verantwortlich

  6. Management Consultant / Management Consultant

  7. Created date from-to / Erstellungsdatum

  8. Location / Standort

  9. Search radius / Suchradius

  10. Company / Unternehmen

  11. Industries / Branchen

  12. Categories / Kategorien

  13. Skills / Skills

  14. Experience Level / Erfahrung

  15. Employment type / Beschäftigungsart

  16. Degrees / Abschlüsse

  17. Process Type / Prozessart

  18. Job Model / Arbeitsmodell

  19. Salary range / Gehaltsspanne

  20. Start date / Anfangsdatum

  21. Remote work / Fernarbeit

  22. Position / Stelle

  23. Leading experience / Führungserfahrung

  24. Languages / Sprachen

  25. Workload / Arbeitspensum

  26. CRM users/SPOC / CRM-Benutzer/SPOC

  27. Reserved / Reserviert

  28. Without Publications / Ohne Publikationen

  29. OOS Market / Markt

image-20241112-130339.png

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

#

Filter Field

Acceptance Criteria

Select data

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

01

Title

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

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

Responsible

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

Select type:

  • multi select

  • multi tags

  • search

  • suggestions

  • custom tags OOS

consultants[]

06

Management Consultant

Scenario: User filters by Management consultant.
Given Management consultant is assigned through the order,
When one is selected,
Then results match the selection.

Management consultant

07

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

08

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

09

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

10

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

11

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

12

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

13

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

14

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

15

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

16

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

17

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

18

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

19

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

20

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

21

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

22

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

23

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

24

Languages

Scenario: User filters by language.
Given language options exist,
When one is selected
AND the order of languages should follow the specified sequence: Deutsch, Englisch, Französisch, Italienisch, and others alphabetically.
Then results reflect vacancies requiring that language.

Select type:

  • multi select

  • multi tags

  • search OOS

  • suggestions OOS

  • custom tags OOS

languages[]

25

Workload

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

workload[]

0-100%

26

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

27

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

28

Without Publications

Scenario: User filters for Vacancies that have no/any Publications.
Given a reserved filter fields,
When selected “yes”,
Then only Vacancies that have no related Publications are displayed.

When selected “no”,
Then only Vacancies that have related Publications are displayed.

Options:

  • yes / ja

  • no / nein

29

OOS Market

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

Comments

Leave a Reply