Category: ROCKEN Documentation

  • Story 1.3.2.1. CRM. Order view mode. Header

    Content

    General info

    The Order View Mode Header provides an overview of the order, including its status, key dates, and personnel involved. It also includes functionalities for changing the order status and accessing additional information through direct links and timeline details.

    User story

    As a CRM user
    I want to see a comprehensive header for each order
    So that I can easily access important information and manage the order effectively.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=32435-146022&t=N2sPFZGmKVrtA1Fu-4

    Acceptance criteria

    01

    Scenario: View order header
    Given the user is on the Order View Mode page
    When the page loads
    Then the header should display the title of the order, status, change status button, notes icon, start date, and end date.

    AND order get information about the market from the Company

    image-20250221-130313.png

    02

    Scenario: View first section
    Given the user is on the Order View Mode page
    When the user views the order header
    Then first sections should display:
    – Sales/Account Manager (single selection, Roles: sales, consultant, admin, HoD, mandatory)
    – Management consultant (single selection, All CRM users in select, not mandatory),
    – Responsible Recruiter (single selection, recruiters and HoR in select, not mandatory),

    03

    Scenario: View second section
    Given the user is on the Order View Mode page
    When the user views the direct link section
    Then second section, there should be options to copy the link and open it in a new tab.

    04

    Scenario: View third section
    Given the user is on the Order View Mode page
    When the user views the current step section
    Then the section should display Current Step, Deadline, Next Task In, and a link to see the timeline.

    05

    Scenario: Edit Team Button
    Given the user is on the Order View Mode page
    When the first section (Sales/Account Manager, Management Consultant, Responsible Recruiter) is not filled out fully / has to be edited
    Then a "Edit Team" button should be displayed.

    image-20250218-073924.png

    06

    Scenario: Click on Edit Team Button
    Given the user is on the Order View Mode page
    When the first section (Sales/Account Manager, Management Consultant, Responsible Recruiter) is not filled out fully / has to be edited
    Then the user clicks on an "Edit Team" button and can select the assigned in a popup

    image-20250217-170322.png

    07

    Scenario: Make a Vacancy and Make a Publication Buttons
    Given the user is on the Order View Mode page
    When the second section (Direct Link) is not filled out fully
    Then "Make a Vacancy" and "Make a Publication" buttons should be displayed in that section.

    image-20240904-150913.png

  • Epic 1.3.2. CRM. Order view mode

    Content

    General info

    Epic focuses on enhancing the Order View Mode, allowing users to view detailed information about a specific order. This includes a comprehensive header with key details, as well as organized sections that provide insights into various aspects of the order, including personnel involved, direct links, and task timelines.

    Epic ticket:

    User stories

    Visual design

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=30960-132534&t=Hj6EIWi3xA7e3iA3-4

  • Story 1.3.1.3. Order list CRUD

    Content

    General info

    User story

    As a …

    I want …

    So that …

    Visual design:

    Acceptance criteria

    01

    Given:

    When:

    Then:

    02

    Given:

    When:

    Then:

    03

    Given:

    When:

    Then:

  • Story 1.3.1.2. CRM. Order list filters

    Content

    General info

    The Order List Filters functionality allows users to refine their view of the order list by applying various filters. This helps users to quickly locate and manage orders based on specific criteria such as status, company, and more.

    User story

    As a CRM user
    I want to filter the order list based on different criteria
    So that I can quickly find and manage orders that meet specific conditions.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=58304-37795&t=NY0lewCIDbekeS63-1

    Acceptance criteria

    01

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

    2. Company / Unternehmen

    3. Sales/Account Manager / Sales/Account Manager

    4. Responsible recruiter / Responsible recruiter

    5. Management consultant / Management consultant

    6. Created date / Erstellungsdatum

    7. Market / Markt

    image-20250217-162814.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

    Query

    https://api.staging.rockengroup.com/api-documentation-2000#/Order/get_api_v1_orders

    01

    Title

     

    Scenario: User interact with the field
    Given user in upper search field,
    When search some items (Order name)
    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 Orders 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 Orders

    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 OOS

    • suggestions OOS

    • custom tags OOS

    statuses[]

    Available values :

    • in progress /

    • active /

    • inactive /

    04

    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

    • multi tags

    • search

    • suggestions

    • custom tags

    companies[]

    06

    Sales/Account manager

    Scenario: User applies a Sales/Account manager filter.
    Given Sales/Account manager exist,
    When one or several are selected,
    Then results show jobs managed by the Sales/Account manager.

    Select type:

    • multi select

    • multi tags

    • search

    • suggestions

    • custom tags OOS

    sales_manager[]

    07

    Responsible Recruiter

    Scenario: User applies Responsible recruiter filter.
    Given available recruiter option,
    When one recruiter is selected,
    Then results show Orders where the selected user is saved as a Responsible recruiter.

    Select type:

    • multi select

    • multi tags

    • search

    • suggestions

    • custom tags OOS

    recruiters, HoR []

    08

    Management Consultant

    Scenario: User applies a Management consultant filter.
    Given consultant options exist,
    When one is selected,
    Then results show Orders where the selected user is saved as a Management consultant.

    Select type:

    • multi select

    • multi tags

    • search

    • suggestions

    • custom tags OOS

    all CRM users[]

    09

    Created 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

    10

    Market

    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

  • Story 1.3.1.1. Order list table

    Content

    General info

    The Order List Table provides a comprehensive view of all orders in the CRM system. Users can view detailed information about each order and navigate through pages of data using pagination controls. The table includes columns for essential order details to facilitate easy tracking and management.

    User story

    As a CRM user
    I want to see a table of all orders with relevant details
    So that I can efficiently manage and track the orders in the system.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=30738-77636&t=N2sPFZGmKVrtA1Fu-4

    Acceptance criteria

    01

    Scenario: Display order list table
    Given the user is on the Order List View page
    When the page loads
    Then the table should display columns for Status, Created at, Order name, Direct link, Company with Country, Sales, Recruiter, and Consultant.

    02

    Scenario: Prefilter by country
    Given the user is on the Order List View page
    When the page loads
    Then the table should prefilter orders by the user’s country, showing only orders relevant to that country.

    03

    Scenario: Pagination
    Given the user is on the Order List View page
    When there are multiple pages of orders
    Then the user should be able to navigate between pages using pagination controls.

  • Epic 1.3.1. CRM. Order list view

    Content

    General info

    This epic focuses on the Order List View within the CRM system. The goal is to provide users with a clear, organized table view of all orders. This includes relevant columns for order details and functionality for pagination to handle large volumes of orders efficiently.

    Epic ticket:

    User stories

    Visual design

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=30738-77636&t=Hj6EIWi3xA7e3iA3-4

  • Story 1.2.3.7. CRM. Vacancy edit mode. Tab Benefits

    Content

    General info

    This feature allows recruiters to add, edit, and organize the benefits associated with a vacancy within the CRM system. The Benefits tab provides a dropdown list, which the recruiter can select and specify further with detailed descriptions. This information helps to attract candidates by clearly listing what benefits the company provides for the role.

    User story

    As a CRM user,
    I want to add and customize benefits for a vacancy,
    So that candidates can see the perks associated with the job, making it more attractive.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=18464-78277&t=K9IerXSbmyGoD1Su-4

    Acceptance criteria

    01

    Scenario: Accessing the Benefits Tab
    Given the recruiter is in the vacancy edit mode,
    When they select the "Benefits" tab,
    Then an interface should be displayed that allows them to add, edit, and delete benefits for the vacancy.

    image-20241101-161936.png

    02

    Scenario: Adding a New Benefit
    Given the recruiter is in the Benefits tab,
    When they click on "Add benefit,"
    Then a new benefit entry should appear with a dropdown to select the benefit type and an optional field to add specific details.

    03

    Scenario: Selecting a Benefit Type
    Given a new or existing benefit entry,
    When the recruiter clicks on the benefit dropdown,
    Then they should see a list of predefined benefits, such as "Flexible working hours," "Company car," etc., to choose from.

    04

    Scenario: Adding Benefit Details
    Given a benefit is selected from the dropdown,
    When the recruiter enters text in the "Details" field,
    Then the entered details should be saved along with the benefit and displayed when viewed.

    05

    Scenario: Deleting a Benefit
    Given a benefit entry is added,
    When the recruiter clicks on the trash icon for that entry,
    Then the benefit should be removed from the list without affecting other entries.

    06

    Scenario: Saving Changes in Benefits
    Given the recruiter has added or modified benefits,
    When they click "Save 1 change,"
    Then the changes should be saved and displayed in the vacancy’s benefits section when viewed in public mode.

    07

    Scenario: Canceling Changes in Benefits
    Given the recruiter has made changes to the Benefits tab,
    When they click "Cancel,"
    Then no changes should be saved, and the previous benefit list should remain intact.

    08

    Scenario: Restricting Duplicate Benefits
    Given the recruiter has already added a specific benefit,
    When they attempt to add the same benefit again,
    Then the system should display a validation message indicating that duplicate benefits are not allowed.

    09

    Scenario: Preventing Unintended Data Loss
    Given the recruiter has entered or modified text in the Benefits tab without saving,
    When they attempt to navigate away from the page,
    Then a confirmation dialog should appear, prompting them to save or discard changes.

    10

    Scenario: Displaying Benefits in Vacancy Listing
    Given the recruiter has added benefits to a vacancy,
    When the vacancy is viewed in public mode,
    Then all listed benefits with their details should be displayed for the candidate to review.

  • Story 1.2.3.6. CRM. Vacancy edit mode. Tab Qualifications

    Content

    General info

    This story involves allowing recruiters to add and edit the qualifications required for a vacancy in the CRM system. The Qualifications tab provides a rich text editor, enabling recruiters to list educational requirements, professional experience, and skills necessary for the position. This information helps candidates understand the prerequisites for applying to the vacancy.

    User story

    As a CRM user,
    I want to input and edit the qualifications for a vacancy,
    So that candidates understand the requirements and assess their eligibility for the position.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=18464-78277&t=K9IerXSbmyGoD1Su-4

    Acceptance criteria

    01

    Scenario: Accessing the Qualifications Tab
    Given the recruiter is in the vacancy edit mode,
    When they select the "Qualifications" tab,
    Then a rich text editor should be displayed for them to input or modify the qualifications of the vacancy.

    image-20241101-155146.png

    02

    Scenario: Entering Qualifications
    Given the recruiter is in the Qualifications tab,
    When they start typing in the rich text editor,
    Then they should be able to format text with options like bold, italics, bullet points, headers, and links.

    03

    Scenario: Saving Changes in Qualifications
    Given the recruiter has entered or modified qualifications,
    When they click "Save 1 change,"
    Then the changes should be saved and displayed in the vacancy’s qualifications section.

    04

    Scenario: Cancelling Qualifications Changes
    Given the recruiter has made changes in the Qualifications tab,
    When they click "Cancel,"
    Then the changes should not be saved, and the previous qualifications should remain as is.

    05

    Scenario: Qualification Format Validation
    Given the recruiter has completed a list of qualifications,
    When they submit the form,
    Then the system should validate that the qualifications are well-structured without empty or redundant formatting tags.

    06

    Scenario: Ensuring Text Editor Consistency
    Given the rich text editor is used in the Qualifications tab,
    When the recruiter applies specific formats (e.g., bullet points),
    Then these formats should appear consistently in the public vacancy listing view.

    07

    Scenario: Formatting Restrictions
    Given the recruiter is formatting the qualifications,
    When they use the text editor tools,
    Then only the allowed formatting options (e.g., font size, bullet points) should be accessible to maintain a consistent design.

    08

    Scenario: Preventing Unintended Data Loss
    Given the recruiter has entered or modified text in the Qualifications tab without saving,
    When they attempt to navigate away from the page,
    Then a confirmation dialog should appear, prompting them to save or discard changes.

  • Story 1.2.3.5. CRM. Vacancy edit mode. Tab Responsibility

    Content

    General info

    This story focuses on enabling recruiters to define and edit the responsibilities associated with a vacancy in the CRM system. The Responsibilities tab includes a rich text editor that allows recruiters to format and structure responsibility descriptions clearly. This enables candidates to get a better understanding of the role’s duties and expectations, helping them assess whether they are a good fit for the position.

    User story

    As a CRM user,
    I want to enter and edit the responsibilities for each vacancy,
    So that candidates can understand the role’s duties and expectations more clearly.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=18464-78277&t=K9IerXSbmyGoD1Su-4

    Acceptance criteria

    01

    Scenario: Accessing the Responsibility Tab
    Given the recruiter is in the vacancy edit mode,
    When they select the "Responsibility" tab,
    Then a rich text editor should be displayed for them to input or modify the responsibilities of the vacancy.

    image-20241101-154912.png

    02

    Scenario: Entering Responsibilities
    Given the recruiter is in the Responsibility tab,
    When they start typing in the rich text editor,
    Then they should be able to format text with options like bold, italics, bullet points, headers, and links.

    03

    Scenario: Saving Changes in Responsibility
    Given the recruiter has entered or modified responsibilities,
    When they click "Save 1 change,"
    Then the changes should be saved and displayed in the vacancy’s responsibilities section.

    04

    Scenario: Cancelling Responsibility Changes
    Given the recruiter has made changes in the Responsibility tab,
    When they click "Cancel,"
    Then the changes should not be saved, and the previous responsibilities should remain as is.

    05

    Scenario: Ensuring Text Editor Consistency
    Given the rich text editor is used in the Responsibility tab,
    When the recruiter applies specific formats (e.g., bullet points),
    Then these formats should appear consistently in the public vacancy listing view.

    06

    Scenario: Formatting Restrictions
    Given the recruiter is formatting the responsibilities,
    When they use the text editor tools,
    Then only the allowed formatting options (e.g., font size, bullet points) should be accessible to maintain a consistent design.

    07

    Scenario: Preventing Unintended Data Loss
    Given the recruiter has entered or modified text in the Responsibility tab without saving,
    When they attempt to navigate away from the page,
    Then a confirmation dialog should appear, prompting them to save or discard changes.

  • Story 1.2.3.4. CRM. Vacancy edit mode. Tab Descriptions

    Content

    General info

    Enhance the CRM system by implementing a "Description" tab within the vacancy edit mode. This tab will allow recruiters to add and edit detailed descriptions for each vacancy. This feature aims to provide recruiters with a space to elaborate on the role, responsibilities, and any additional information that helps to attract suitable candidates.

    User story

    As a recruiter,
    I want to add and edit a comprehensive description for a vacancy in a dedicated "Description" tab,
    So that I can provide detailed information about the role, making it more appealing and informative for potential candidates.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=18464-78277&t=K9IerXSbmyGoD1Su-4

    Acceptance criteria

    01

    Scenario: Accessing the Description tab
    Given the recruiter is in vacancy edit mode
    When they navigate to the "Description" tab
    Then they should see a rich-text editor where they can input and format a detailed job description.

    image-20241101-152128.png

    02

    Scenario: Using Rich Text Editor
    Given the recruiter is in the "Description" tab
    When they use the editor tools (e.g., bold, italic, underline, bullets, numbered list)
    Then the editor should apply the respective formatting to the selected text.

    03

    Scenario: Adding Title to Description
    Given the recruiter is in the "Description" tab
    When they input a title using the title dropdown menu
    Then the title should be formatted accordingly and saved as part of the job description.

    04

    Scenario: Formatting Text with Headings
    Given the recruiter is in the "Description" tab
    When they select a heading level (e.g., Title 1, Title 2)
    Then the selected text should be formatted as a heading and appear visually distinct in the description.

    05

    Scenario: Inserting Links
    Given the recruiter is in the "Description" tab
    When they add a hyperlink to selected text
    Then the link should be saved as part of the description, making the text clickable.

    06

    Scenario: Saving Changes
    Given the recruiter has made changes in the "Description" tab
    When they click "Save 1 Change"
    Then all entered details should be saved, and a confirmation message should appear.

    07

    Scenario: Canceling Changes
    Given the recruiter is in the "Description" tab
    When they click "Cancel"
    Then no changes should be saved, and the system should return to the previous view without updating the description.

    08

    Scenario: Viewing the Updated Description in Vacancy Details
    Given the recruiter has saved a description
    When they view the vacancy in normal mode
    Then the saved description should appear formatted exactly as it was in the editor.