Category: ROCKEN Documentation

  • Story 2.1.2. RT. Company preview page

    Content

    General info

    The Company Preview page provides detailed information about a company, its values, benefits, and open vacancies. The page is designed to give potential applicants a comprehensive understanding of the company’s background, work culture, and benefits, as well as offering insights into available positions at the company.

    User story

    As a job seeker,
    I want to view the company preview page,
    So that I can learn about the company’s history, values, benefits, and available job opportunities before applying for a position.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=48364-161434&t=MzN8BNa2y3FjeZ54-4

    #

    Acceptance Criteria

    01

    Scenario: Display Company Title and Profile
    Given I am on the Company Preview page,
    When I view the page,
    Then I should see the company’s name, logo, and a brief introduction, along with the location and number of employees.

    image-20250206-082148.png

    02

    Scenario: Display Company Overview Section
    Given I am on the Company Preview page,
    When I view the company profile,
    Then I should see a section titled "Unser Selbstverständnis" (Our Philosophy) and "Unsere Werte" (Our Values) describing the company’s mission, values, and approach to work.

    image-20250206-082258.png

    03

    Scenario: Display Company History Section
    Given I am on the Company Preview page,
    When I view the company profile,
    Then I should see a section titled "Geschichte" (History) explaining the company’s background and its journey.

    image-20250206-082328.png

    04

    Scenario: Display Role Opportunities Section
    Given I am on the Company Preview page,
    When I scroll down,
    Then I should see a section titled "Berufschancen" (Career Opportunities) with descriptions of job roles and how candidates can join the company.

    image-20250206-082355.png

    05

    Scenario: Display Benefits Section
    Given I am on the Company Preview page,
    When I scroll further,
    Then I should see a section titled "Benefits" listing all the benefits the company offers (e.g., flexible working hours, health insurance, etc.).

    image-20250206-082406.png

    06

    Scenario: Display Enterprise Structure Section
    Given I am on the Company Preview page,
    When I scroll further,
    Then I should see a section titled "Enterprise structure" showing the organizational structure of the company and its key divisions.

    image-20250206-082419.png

    07

    Scenario: Display Other Open Vacancies Section
    Given I am on the Company Preview page,
    When I view the page,
    Then I should see a section titled "Weitere offene Stellen" (Other Open Vacancies) displaying a list of other available job positions at the company.

    image-20250206-082439.png

    08

    Scenario: Responsive Layout for Tablets
    Given I am viewing the Company Preview page on a tablet,
    When I view the content,
    Then the layout should adjust to the tablet’s screen size without breaking the design or content structure, ensuring that all sections are still visible and easy to navigate.

    09

    Scenario: Correct Font and Button Size on Tablets
    Given I am viewing the Company Preview page on a tablet,
    When I interact with the page,
    Then the font size, buttons, and other interactive elements should be appropriately sized for tablet use, ensuring ease of reading and clicking.

    10

    Scenario: Responsive Layout for Mobile devices
    Given I am viewing the Company Preview page on a mobile,
    When I view the content,
    Then the layout should adjust to the mobile’s screen size without breaking the design or content structure, ensuring that all sections are still visible and easy to navigate.

  • Release Notes – ROCKEN-TALENT – Release NA 04.02.2025 [1.1.15] – Feb 05 17:22

    How to use this page:

    Find your selected Jira issues in the table below. Select the expand to use them as your source of truth to write release notes.

    Release

    https://cheitgroup.atlassian.net/projects/RT/versions/10382

    Date

    Version

    Release NA 04.02.2025 [1.1.15]

    Description

    Contributors

    Yurii TymchukDasha RozhniatovskaAnton LiakhIhor BushtakovViktoriia Malysh

    Issues in this release

    Before you share the page, review the contents of each Jira issue and remove any sensitive data.

    Issue

    Summary

    Issue Type


    RT-6544

    [RT] 404 error during setup of the password if the profile was deleted from RT before

    Bug


    RT-6375

    [Applications] Display new applications of already existing profiles (displayed as Not Relevant)

    Story


    RT-6293

    [Support] [Processes] Add the prefilter for BM and HoD in Processes to see the processes of the users that are subordinated to them

    Story


    RT-6287

    [Profile] Develop deletion functionality

    Story


    RT-6224

    [Support] [CRM] [Applications] [Send Interview] The 400 error is shown while trying to send the Interview to the migrated application (reapplication type)

    Bug


    RT-5819

    (BE) users (roles) for Germany

    BE sub-task


    RT-5585

    [RT] [Interview] The “Save” button is always active on the Interview editing page, even if no changes were made

    Bug


    RT-4769

    [CRM] [Profile] The invitation to RT/Interview can be sent only once

    Bug


    RT-4751

    CRM users (roles) for Germany

    Story


    RT-4285

    [CRM] [RJ] [Publication] The “Sofort” start date of the Publication is not shown on the RJ

    Bug


    RT-3855

    [Profile] [Vacancy] Calculating the distance between Profiles and Vacancies

    Task

    New Features

    • Implemented Deletion functionality for Profiles in CRM.

    • Implemented market settings (Germany or/and Switzerland) for CRM users.

    • Distance between Profiles and Vacancies is calculating right now on vacancy and profile list. Use filters for location and radius https://prnt.sc/aS6_kCZoLFCi

    Improvements to existing features

    • [Applications] Display new applications of already existing profiles. Functionality:

      1. If the profile is in “new/unfinished” then it’s applications are displayed for answer according to the regular logic.

      2. If the profile is in “Rejection” status, then it’s new applications are shown with a display of the previous rejection reason and current status. The application offers approval (interview, process) and rejection answers. If the profile is rejected again, no change is done. If the profile is approved, the profile switches status to “in progress” and gets reassigned to the recruiter who approved the profile.

      3. If the profile is in “In progress”, “interview”, “active”, “offline” statuses then the application displays the current profile status and shows all the answer buttons as disabled. The user can change the status in the application so that it’s no longer displayed in the Applications list.

      4. Additionally: if a candidate in status unfinished uploads attachments once and the profile switches to New, no Unfinished reminders are sent anymore (cancelled for all other unfinished applications if there were any)

    • [Processes] Added the prefilter for BM and HoD in Processes to see the processes of the users that are subordinated to them. The prefilters are set in the processes by subordinated to their users for BM and HoD.

    Bug fixes

    • [RT] 404 error during setup of the password if the profile was deleted from RT before.

    • [CRM] [Applications] [Send Interview] The 400 error is shown while trying to send the Interview to the migrated application (reapplication type)

    • [RT] [Interview] The “Save” button is always active on the Interview editing page, even if no changes were made. Now the button activates when you change something.

    • [CRM] [Profile] The invitation to RT/Interview can be sent only once. The problem is fixed and invitation can be resend.

    • [CRM] [RJ] [Publication] The “Sofort” start date of the Publication is not shown on the RJ. Now it is shown.

  • Xing

    Their documentation

    Feed will be fetched four times a day. Currently there is no way of pushing feeds into the XING Jobs.

    Sandbox: https://space-rt-s.fra1.digitaloceanspaces.com/xing.xml

    Production: https://space-rt.fra1.digitaloceanspaces.com/xing.xml

    Our Fields

    Field

    Required

    Description

    Example value

    id

    •  

    Unique identifier for your job ads.
    Never use the same ID for two different ads.
    Length is limited to 100 characters.

    <![CDATA[54514]]>

    job_title

    •  

    The length needs to be between 3 and 255 characters.

    <![CDATA[Sachbearbeiter Export (m/w/d)]]>

    description

    •  

    Allowed tags: h1, h2, h3, h4, h5, h6, hr, a, br, li, ol, ul, p, em, i, b, strong

    Other tags and attributes including style tags and inline CSS will be removed. Length is limited to 10.000 characters.

    More information: Feed description

    company_name

    •  

    Constant value: ROCKEN

    <![CDATA[ROCKEN]]>

    job_location

    •  

    Requires to contains country and city:

    1. <city><![CDATA[Hamburg]]></city>

    2. <country><![CDATA[DE]]></country>

    <job_location>
        <address><![CDATA[Dammtorstraße 30]]></address>
        <city><![CDATA[Hamburg]]></city>
        <zip_code>08470</zip_code>
        <country><![CDATA[DE]]></country>
        <latitude>23.1112</latitude>
        <longitude>41.220</longitude>
    </job_location>
    
    <job_location>
        <city><![CDATA[Hamburg]]></city>
        <country><![CDATA[DE]]></country>
    </job_location>

    reply_setting

    •  

    Constant value: url

    <![CDATA[url]]>

    url

    •  

    Link to the application form

    <![CDATA[https://rocken.jobs/application/sachbearbeiter-export-mwd54514/?utm_source=xing&utm_medium=cpc&utm_campaign=sponsored]]>

    remote_options

    •  

    Mapped:

    {
      undefined: 'NON_REMOTE',
      home_office: 'FULLY_REMOTE',
      remote_work: 'FULLY_REMOTE',
      hybrid: 'PARTIALLY_REMOTE',
      on_site: 'NON_REMOTE'
    }

    Their choices:

    • FULLY_REMOTE

    • PARTIALLY_REMOTE

    • NON_REMOTE

    <remote_options>
        <remote_option><![CDATA[NON_REMOTE]]></remote_option>
        <remote_option><![CDATA[FULLY_REMOTE]]></remote_option>
    </remote_options>

    tags

    •  

    May contain several nodes holding a tag to help find your ad.
    The maximum length of all tags combined, separated by comma, is 500 characters.
    (not visible to users)

    skills

    •  

    May contain several nodes holding a skill to be used to match candidates.
    The maximum length of all skills combined, separated by comma, is 255 characters.

    (not visible to users)

    <skills><![CDATA[Java,Python]]></skills>

    salary

    •  

    Must contain a range_start and range_end which specify the lower and upper bound of the yearly salary range as integer. It may include an optional currency tag. The default value is ‘EUR’.

    <salary>
        <range_start>50000</range_start>
        <range_end>70000</range_end>
        <currency>EUR</currency>
    </salary>

    industry_id

    •  

    discipline_id

    •  

    job_type

    •  

    Should be only one value.

    Mapped:

    {
      permanent: 'FULL_TIME',
      part_time: 'PART_TIME',
      temporary: 'TEMPORARY',
      full_time: 'FULL_TIME'
    }

    Their choices:

    • FULL_TIME

    • PART_TIME

    • CONTRACTOR

    • INTERN

    • SEASONAL

    • TEMPORARY

    • VOLUNTARY

    Priority:

    FULL_TIME

    PART_TIME

    OTHER..

    <![CDATA[PART_TIME]]>

    career_level

    •  

    Mapped:

    {
      specialist: 'JOBLEVEL_3',
      leadership: 'JOBLEVEL_4',
      executive: 'JOBLEVEL_5'
    }

    Their choices:

    • JOBLEVEL_1 – Student/Intern

    • JOBLEVEL_2 – Entry Level

    • JOBLEVEL_3 – Professional/Experienced

    • JOBLEVEL_4 – Manager (Manager/Supervisor)

    • JOBLEVEL_5 – Executive (VP, SVP, etc.)

    • JOBLEVEL_6 – Senior Executive (CEO, CFO, President)

    <![CDATA[JOBLEVEL_3]]>

  • Story 1.5.5.10. CRM. Application. Tab notes

    Content

    General info

    The "Application" tab currently contains four sections: Primary, Client Brief, Personal, and Applications. An additional "Notes" tab should be added to allow users to add, edit, and delete notes related to the application. These notes should be retained when the application is transformed into a profile in the CRM. Furthermore, if the same user reapplies, their old notes should be displayed alongside the new application.

    User story

    As a CRM user,
    I want to have a "Notes" tab in the Application section,
    So that I can add, edit, and delete notes related to the application, and ensure the notes are transferred to the profile record in CRM when the application is processed. Additionally, the old notes should be visible if the user reapplies to the system.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=61149-37422&t=LlHxv1jCMxXICniQ-4

    Acceptance criteria

    01

    Scenario: Displaying Notes tab
    Given I am in the Application section,
    When I view the application,
    Then I should see the following tabs: Primary, Client Brief, Personal, Applications, and Notes.

    image-20250203-081606.png

    02

    Scenario: Adding a new note
    Given I am in the Notes tab,
    When I click "Add Note",
    Then I should be able to add a new note to the application.

    03

    Scenario: Editing an existing note
    Given I have added a note in the Notes tab,
    When I click "Edit" on an existing note,
    Then I should be able to modify the content of the note.

    04

    Scenario: Deleting a note
    Given I have added a note in the Notes tab,
    When I click "Delete" on an existing note,
    Then the note should be deleted from the application.

    05

    Scenario: Transferring notes to profile
    Given the application has been transformed into a profile in the CRM,
    When I view the profile,
    Then the notes from the application should be transferred and visible in the profile record.

    06

    Scenario: Displaying old notes for re-applied candidates
    Given a candidate has previously applied and is reapplying to the system,
    When I view the new application,
    Then I should see their old notes displayed alongside the new application.

  • Story 1.6.1.2. Match Vacancies and Candidates for Process Creation

    Content

    General info

    When creating a new process, the user should be able to select a vacancy and candidate from the same market, which is determined based on the company associated with the vacancy. This ensures that the process is created for a relevant market, keeping the candidate and vacancy aligned.

    User story

    As a CRM user,
    I want to select a vacancy and a candidate from the same market when creating a process,
    So that I can ensure that the selected candidate is relevant to the chosen vacancy based on the company’s market.


    RT-6535

    Получение подробных данных проблемы…
    СТАТУС

    Visual design

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=44550-100778&t=V4nNKW9wJlemJ1ll-4

    Acceptance criteria

    01

    Scenario: Selecting candidate and vacancy from the same market
    Given I am creating a new process,
    When I select a vacancy,
    Then I should only be able to select candidates from the market associated with that vacancy’s company.

    image-20240905-062719.png

    02

    Scenario: Restricting market selection
    Given I am creating a process,
    When I select a candidate,
    Then I should only be able to select vacancies that belong to the same market as the candidate’s market.

  • Release Notes – ROCKEN-TALENT – Release NA 30.01.2025 [1.1.14] – Jan 31 08:09

    How to use this page:

    Find your selected Jira issues in the table below. Select the expand to use them as your source of truth to write release notes.

    Release

    https://cheitgroup.atlassian.net/projects/RT/versions/10381

    Date

    Version

    Release NA 30.01.2025 [1.1.14]

    Description

    Contributors

    Ihor BushtakovAnton Liakh

    Issues in this release

    Before you share the page, review the contents of each Jira issue and remove any sensitive data.

    Issue

    Summary

    Issue Type


    RT-6542

    [Support][Profile preview] Temporarily remove the currency from salary

    Task


    RT-6540

    [Vacancy Preview] Connect accept/reject action directly on the "Interested"/"Not interested" buttons

    Bug


    RT-6531

    RT. Profile/Vacancy preview. Change font from Nohemi to Manrope

    Task


    RT-6493

    [Search] Bring out the keyword search to the main pages out of the filters

    Story


    RT-6481

    [Application] Do not send reminders if the candidate attached files at least to one application

    Task


    RT-6457

    [Process][Profile] Do not send reminders if the action they remind about is already done

    Bug


    RT-6443

    RT. Interview. Add spaces for validation errors

    Task

    Summary

    New Features

    • [Search] Bring out the keyword search to the main pages out of the filters

    • [Support][Profile preview] Temporarily remove the currency from salary

    • [Application] Do not send reminders if the candidate attached files at least to one application

    Improvements to existing features

    • RT. Interview. Add spaces for validation errors

    Bug fixes

    • [Vacancy Preview] Connect accept/reject action directly on the "Interested"/"Not interested" buttons

    • [Process][Profile] Do not send reminders if the action they remind about is already done

  • Story 1.5.5.9. CRM. Application list. Display New Applications for Existing Profiles

    Content

    General info

    The system should display all unanswered applications, including new and unfinished applications, for existing profiles in the CRM. It should show the status of the application, including the rejection reason if applicable, and allow changes in status for profiles that are not in "New," "Unfinished," or "Rejected" statuses. This functionality aims to ensure that all applications, regardless of the profile’s previous status, are visible for recruiters to review and respond.

    User story

    As an admin (any application), recruiting head (any application), recruiter (only application where they is a recruiter),
    I want to see all new and unfinished applications for existing profiles, including the rejection reason if the profile is rejected,
    So that I can review all applications, update statuses as needed, and ensure no application is missed due to previous processing.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=61057-83201&t=C4UtlUwwUUaufTow-4

    Acceptance criteria

    01

    Scenario: Displaying new and unfinished applications
    Given a profile has new or unfinished applications,
    When I view the Applications tab,
    Then only applications with the status "Unfinished" or "New" should be displayed, and all other statuses should be removed from the list.

    image-20250130-082939.png

    02

    Scenario: Creating a new application upon re-submission
    Given a profile has a status other than "Unfinished" or "New",
    When I re-submit the application,
    Then a new application with the status "Unfinished" or "New" should be created.

    03

    Scenario: Changing the application status to "Interview"
    Given there are multiple applications with statuses "Unfinished" or "New",
    When I click "Send interview",
    Then the application status should change to "Interview", and the other applications with statuses "Unfinished" or "New" should be marked as "Not Relevant" and removed from the list.

    04

    Scenario: Changing the application status to "Applied"
    Given there are multiple applications with statuses "Unfinished" or "New",
    When I click "Create process",
    Then the application status should change to "Applied", and the other applications of this candidate with statuses "Unfinished" or "New" should be marked as "Not Relevant" and removed from the list.

    05

    Scenario: Rejecting a single application
    Given there are multiple applications with statuses "Unfinished" or "New",
    When I click "Reject single",
    Then the application status should change to "Rejected", and the other applications of this candidate with statuses "Unfinished" or "New" should remain unchanged and stay in the list.

    06

    Scenario: Rejecting all applications
    Given there are multiple applications with statuses "Unfinished" or "New",
    When I click "Reject all",
    Then all applications of this candidate with the status "Unfinished" or "New" should change to "Rejected" and no longer be displayed in the list.

    07

    Scenario: Profile status in "In progress", "Interview", "Active", "Offline"
    Given a profile has the status "In progress", "Interview", "Active", or "Offline",
    When I view the application,
    Then the current profile status should be displayed, and all response buttons should be disabled.

    image-20250130-083448.pngimage-20250130-083418.pngimage-20250130-083429.png

    08

    Scenario: Status change button
    Given a profile has the status "In progress", "Interview", "Active", or "Offline",
    When I view the application,
    Then a button should be available to change the application status, but only in cases where the current status does not match the profile’s current status.

    09

    Scenario: Showing rejection reason for rejected profiles
    Given a profile is in the "Rejected" status,
    When I view the application,
    Then the rejection reason should be displayed alongside the application.

    image-20250130-083017.png

    10

    Scenario: Changing application status
    Given a profile is in "Rejected,"
    When the new application is approved,
    Then the profile should be switched to "In Progress" and reassigned to the recruiter who approved the profile.

    11

    Scenario: Display of profile status
    Given a profile has a defined status (e.g., "New," "Rejected"),
    When I view the profile’s applications,
    Then the current status of the profile should be displayed next to the application details, according to the design.

  • Release Notes – ROCKEN-TALENT – Release NA 24.01.2025 [1.1.12] – Jan 29 15:42

    How to use this page:

    Find your selected Jira issues in the table below. Select the expand to use them as your source of truth to write release notes.

    Release

    https://cheitgroup.atlassian.net/projects/RT/versions/10374

    Date

    Version

    Release NA 24.01.2025 [1.1.12]

    Description

    Contributors

    Ihor BushtakovDasha RozhniatovskaYurii TymchukViktoriia MalyshAnton Liakh

    Issues in this release

    Before you share the page, review the contents of each Jira issue and remove any sensitive data.

    Issue

    Summary

    Issue Type


    RT-6482

    [Interview] Candidate can’t pass the interview because of skills validation error

    Bug


    RT-6472

    [CRM] Change order of data display in ACTIVITY and NOTES

    Task


    RT-6464

    [Application] Open the application attachments in the next tab instead of downloading

    Task


    RT-6462

    [Search] Update new filters to narrow down the search

    Task


    RT-6456

    [Support] The name of the company staff is empty in the sharing profile email

    Bug


    RT-6447

    [Support] [Profile] 500 error is shown after trying to check the "Immediate Availability" checkbox and/or setting the "Search radius" distance

    Bug


    RT-6435

    [Support] [RT] [Vacancy Preview] [MacBook + Safari] Multiclicking on the "Apply" button triggers multiple process creation with the same vacancy

    Bug


    RT-6397

    [Interview] Update the logic of calculating completion progress

    Story


    RT-6352

    [Support] [Profiles] Some experience/education records are displayed in not chronological order

    Bug


    RT-6323

    [Roles] Allow HoR to reassign any entity in Recruiting

    Task


    RT-6306

    [Roles] Allow BMs to reassign responsible in any entity

    Task


    RT-6299

    Implement Cache-Control policy for frontend

    Task


    RT-5425

    Reduce amount of the google API calls

    Task

    Summary

    New Features

    Improvements to existing features

    Bug fixes