Content
General info
The "Publications List Filters" story enables CRM users to refine and customize the view of job publications within the Publications List View. This feature allows users to apply various filters based on different publication attributes such as status, date, company, categories, country, recruiter and publication name. By utilizing these filters, users can efficiently locate specific publications, manage large datasets, and enhance their workflow by focusing on relevant entries. The filters should support multiple criteria simultaneously and offer options to save, apply, and reset filter settings as needed.
User story
As a CRM user,
I want to apply and manage filters on the publications list,
So that I can efficiently locate and focus on specific job publications relevant to my needs.
Visual design:
https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=58474-57489&t=FF5QndosgWsPqja0-4
|
|
Acceptance criteria
|
|
|
01
|
Scenario: Opening the Filters panel Given I am on the publications 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
-
Status / Status
-
Creation Date / Erstellungsdatum
-
Rejected Applications / Abgelehnte Bewerbungen
-
Recruiter / Recruiter
-
Responsible Recruiter / Verantwortlicher Recruiter
-
Industry / Branche
-
Categories / Kategorien
-
Company / Unternehmen
-
Applications / Bewerbungen
-
Languages / Sprachen
-
OOS Market / Markt
|
|
|
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
|
|
|
6#
|
Filter Field
|
Acceptance Criteria
|
Query
|
|
https://api.staging.rockengroup.com/api-documentation-2000#/Publication/get_api_v1_publications
|
|
01
|
[OOS] Title
|
Scenario: User interact with the field Given user in upper search field, 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
|
[OOS] Keyword
|
Scenario: User applies a keyword filter. Given the user enters a custom keyword in upper search field,, When it is find info in any publications 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 publications
|
|
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
-
multi tags
-
search
-
suggestions
-
custom tags OOS
|
statuses[]
Available values :
|
|
04
|
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
|
|
05
|
Rejected Applications
|
Scenario: User applies a Rejected Applications filter. Given the user selects "yes" and "no" options, When the selection is “yes”, Then results are filtered by applications with status “rejection” only
When the selection is “no”, Then results are not filtered and show the defult order
|
|
|
06
|
Industry
|
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
|
should be added to API by backend developer
|
|
07
|
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[]
|
|
08
|
Company
|
Scenario: User applies a company filter. Given the user types a company name, When matches exist, Then suggestions are displayed.
Select type:
-
single select
-
single tag
-
search
-
suggestions
-
custom tags
|
companies[]
|
|
|
Responsible Recruiter
|
Scenario: User applies a Responsible recruiter filter. Given available Responsible recruiter option, When matches exist, Then Publications which are assigned to the Orders where the selected Responsible Recruiter is assigned are displayed
|
recruiters, HoR[]
|
|
09
|
Recruiter
|
Scenario: User applies recruiter filter. Given available recruiter option, When one recruiter is selected, Then results filter accordingly this user.
Select type:
-
single select
-
single tag
-
search
-
suggestions
-
custom tags OOS
|
recruiters, HoR[]
|
|
10
|
Applications
|
Scenario: User applies a with applications filter. Given Applications“, When Then results show publications without applications.
|
should be added to API by backend developer
-
With applications
-
Without application
|
|
11
|
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:
-
single select
-
single tag
-
search
-
suggestions
-
custom tags OOS
|
should be added to API by backend developer
|
|
12
|
Market 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 develope7
|
Leave a Reply
You must be logged in to post a comment.