Category: ROCKEN Documentation

  • Release Notes 13.03.2025

    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/10583

    Date

    Version

    Release 13.03.2025

    Description

    Contributors

    Dima Savchenko (WP)Ihor BushtakovIvan Hodoniuk

    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-7002

    [Support] [RJ] The company page is opened after clicking the pagination on the blog

    Bug


    RT-6925

    [Support] The previously entered vacancy/profile is still selected if the "Create process" popup is closed and opened again

    Bug


    RT-6921

    [Profiles] Remove any automatical profile reassignment

    Bug


    RT-6799

    PDF optimization for Profile PDF. Combine rendering in one request

    Story

    Summary

    The release includes improvements to existing features and bug fixes. Key updates in this release include PDF optimization for profile PDFs, which now render more efficiently in a single request. Several bug fixes were also made: the issue where the company page opened after clicking pagination on the blog was resolved, the problem where previously entered vacancies/profiles remained selected after reopening the "Create process" popup was fixed, and automatic profile reassignment was removed. No new features were introduced in this release.

    New Features

    No new features listed in this release.

    Improvements to existing features

    PDF optimization for Profile PDF. The rendering of the profile PDF is now combined in one request and work faster

    Bug fixes

    • RT-7002: Fixed a bug where the company page would open after clicking the pagination on the blog.

    • RT-6925: Resolved an issue where the previously entered vacancy/profile remained selected if the "Create process" popup was closed and reopened.

    • RT-6921: Removed automatic profile reassignment.

  • Story 1.0.16.1. Attachments. Safe access for user file

    Content

    General info

    As part of enhancing data security, the system must ensure that attachments shared through URLs with companies or users are accessible only for a limited time. This feature addresses the security concern where links to user files have been accessible without time limitations.

    User story

    As a user,
    I want the attachment links to expire after 3 hours,
    so that sensitive data on S3 is protected and cannot be accessed beyond the designated time window.

    Visual design:

     

     

    Acceptance criteria

     

    01

    Scenario: Attachment link expiration after 3 hours
    Given a user is given a URL to an attachment,
    When the URL is accessed,
    Then the link should expire after 3 hours.

    during the investigation the links to attachments in the shared profiles without time limitations were found. Here is an example:

    02

    Scenario: Shared profile URL with time-limited access
    Given a shared profile URL with an attachment,
    When the link is accessed,
    Then the attachment should not be available after 3 hours.

    03

    Scenario: Expired link access attempt
    Given a URL to an attachment,
    When the user tries to access it after 3 hours,
    Then the system should display an error or invalid link message.

    04

    Scenario: Restricted access to valid link within 3 hours
    Given the system has time-limited access to attachment links,
    When a user shares the link,
    Then only the user with the valid link within the 3-hour period should be able to access it.

  • Epic 1.0.16. Security

    Content

    General info

    This Epic is focused on ensuring secure access to user files and implementing time-limited access to attachments to prevent unauthorized or prolonged access and other security tasks.

    Epic ticket:


    RT-7048

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

    User stories

    Visual design

  • Release Notes 11.03.2025

    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/10486

    Date

    Version

    Release NA 11.03.2025 [1.1.25]

    Description

    Contributors

    Ihor BushtakovDasha RozhniatovskaYurii Tymchuk

    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-7021

    Fix perfomance problems with Production regarding processes

    Bug


    RT-7005

    [Support] [Talent] Some regions/locations are not found on the "Jobs" tab

    Bug


    RT-7004

    [Talent] Profile language is reset to DE after reapplying on RJ

    Bug


    RT-6926

    [Support] Applied keywords are removed after adding filters

    Bug


    RT-6911

    Fix errors from log rocken_slack_bot

    Task


    RT-6908

    [Talent] Leadership questions are not updated

    Bug


    RT-6886

    [CRM] [Order] [Vacancy] [Head of Division] 403 error is shown for HoD while creating the vacancy with order

    Bug


    RT-6859

    [Support] [Vacancies] [Profiles] Location is not found using the address in the filters

    Bug


    RT-6833

    [Support] [Vacancy/Publication] The 500 error is shown when opening the Vacancy with no responsible

    Bug


    RT-6786

    [CRM] [Order] The admin role can not be selected in the "Sales/Account manager" field

    Bug

    Summary

    The ROCKEN-TALENT Release NA 11.03.2025 [1.1.25] includes several important bug fixes aimed at improving the functionality and stability of the platform. Performance issues related to processes in production have been addressed, and several bugs related to profile language, job tab locations, keyword filters, leadership questions, and vacancy creation have been resolved. These fixes are expected to enhance user experience, especially in terms of smoother operation and more accurate data handling across the system.

    New Features

    No new features

    Improvements to existing features

    Performance: Resolved performance issues regarding processes in production (RT-7021).

    Bug fixes

    • Jobs Tab: Fixed issues with missing regions/locations on the "Jobs" tab (RT-7005).

    • Profile Language: The profile language reset to German (DE) after reapplying on RJ is now fixed (RT-7004).

    • Keywords: Fixed the removal of applied keywords when filters are added (RT-6926).

    • Leadership Questions: Fixed issues with outdated leadership questions (RT-6908).

    • Vacancy Creation Error: Fixed a 403 error occurring when creating a vacancy with orders by the Head of Division (RT-6886).

    • Location Filters: Fixed issues with location not being found using the address in filters (RT-6859).

    • 500 Error for Vacancies: Fixed the 500 error when opening a vacancy with no responsible assigned (RT-6833).

    • Admin Role Selection: Fixed issue preventing the admin role from being selected in the "Sales/Account Manager" field (RT-6786).

  • Sprint 91 review

    (синяя звезда) 1. General info

    Sprint Number

    91

    Sprint Duration

    12.03.2025 – 25.03.2025

    Facilitator

    Andrii Kupriianov

    Attendees

    Andrii Kupriianov Viktoriia Malysh Dasha Rozhniatovska Anton Liakh Anton Poliakov Olexandr Tikan Yurii Tymchuk Ihor Bushtakov Ivan Hodoniuk Julia Martin Stoev Oleksii Fedorchuk Roman Kliuiko Serhii Karashkevych Chris Kai Kindermann

    Link to the meeting

    Tuesday, March 25 · 2:00 – 3:00pm (Europe/Kiev)
    Video call link: https://meet.google.com/kaq-saxx-ire

    (синяя звезда)  2. Sprint goal

    Planned Sprint Goals

    Goal Achievement

    (синяя звезда)  3. Completed work on production (Demo Items)

    User story / Task

    Presenter

    Demo notes

    Viktoriia

    Viktoriia

    Viktoriia

    Viktoriia

    Viktoriia

    Viktoriia

    Viktoriia

    Viktoriia

    Viktoriia

    Viktoriia

    Viktoriia

    Viktoriia

    Viktoriia

    Viktoriia

    Viktoriia

    Viktoriia

    Viktoriia

    :Verified: 4. Working on stage (Demo Items)

    User story / Task

    Presenter

    Demo notes

    Yurii

    Ihor

    Ihor

    Ihor

    Ihor

    Ihor

    Ihor

    Ihor

    (синяя звезда)  5. Work NOT completed

    User story / Task

    Next steps

    (синяя звезда)  6. Metrics & Sprint Performance

    Metric

    Value

    Comments

    Planned hours

    319h

    Remaining hours

    214h

    Sprint Velocity

    105h

    Bugs Reported
    [Critical/High/Medium/Minor]

    82
    5/41/36/0

    Bugs Fixed

    63

  • Retro Sprint 91

    (синяя звезда) General info

    Liked

    Lacked

    Learned

    Longed for

    (синяя звезда) What needs to be improved?

    •  

  • Story 1.4.3.7. CRM. Profile Edit Mode – Personal: Personal section

    Content

    General info

    The Personal section of the Profile Edit Mode allows users to input personal information such as gender, birthday, nationality, residence permit, marital status, children, car ownership, commute preferences, and languages spoken. This section helps gather essential personal details to complete the user’s profile and tailor the CRM system’s features to the user’s preferences.

    User story

    As a CRM user,
    I want to specify personal details, including gender, birthday, marital status, car ownership, and language skills,
    So that personal information can be captured and used for better matching to potential opportunities.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=62378-58547&t=uY2xP4dMRl179HBq-4

    Acceptance Criteria:

    #

    Acceptance Criteria

    01

    Scenario: User selects first/last name and gender.
    Given I am on the personal details page,
    When I enter name and select gender from the dropdown,
    Then candidates name and gender should be displayed correctly.

    image-20250310-083852.png

    02

    Scenario: User inputs birthday.
    Given I am on the personal details page,
    When I enter my birthdate,
    Then my birthdate should be displayed correctly.

    03

    Scenario: User inputs nationality.
    Given I am on the personal details page,
    When I select my nationality from the dropdown,
    Then my nationality should be displayed correctly.

    04

    Scenario: User inputs residence permit.
    Given I am on the personal details page,
    When I select my residence permit status from the dropdown,
    Then the selection should be displayed correctly.

    05

    Scenario: User selects marital status.
    Given I am on the personal details page,
    When I select my marital status (e.g., Married, Separated, etc.),
    Then my marital status should be displayed correctly.

    06

    Scenario: User selects number of children.
    Given I am on the personal details page,
    When I select the number of children (e.g., No children, 1, 2, etc.),
    Then the selected number of children should be displayed correctly.

    07

    Scenario: User selects car ownership.
    Given I am on the personal details page,
    When I select whether I own a car (Yes, No),
    Then the selection should be displayed correctly.

    08

    Scenario: User inputs driver’s license status.
    Given I am on the personal details page,
    When I select whether I have a driver’s license,
    Then the selection should be displayed correctly.

    09

    Scenario: User selects preferred commute option.
    Given I am on the personal details page,
    When I select my preferred commute to work (Car, Public transport),
    Then my commute preference should be displayed correctly.

    10

    Scenario: User inputs distance to work and address.
    Given I am on the personal details page,
    When I enter the distance (in km) and address,
    Then the values should be displayed correctly.

    11

    Scenario: User adds languages.
    Given I am on the personal details page,
    When I add a language and specify the level,
    Then the language and level should be displayed correctly.

    12

    Scenario: The user can save new info in the "Personal" section.
    Given the user has entered all necessary information in the "Personal" section,
    When the user clicks the ‘Save’ button (that is sticky to the bottom),
    Then the entered details in the "Personal" section should update and be reflected on the page.

    13

    Scenario: The user can cancel without saving changes.
    Given the user is in the "Personal" section,
    When the user clicks the ‘Cancel’ button (that is sticky to the bottom),
    Then the page should close without saving any changes and revert to the previous state.

  • Story 1.4.3.8. CRM. Profile Edit Mode – Personal: About and hobbies

    Content

    General info

    The About and Hobbies section in the Profile Edit Mode allows users to enter additional personal details, including a description about themselves and their hobbies. The "About" field lets users provide a short description, while the "Hobbies" field allows users to search and select relevant hobbies from a predefined list. This section helps capture more personalized information about the user.

    User story

    As a CRM user,
    I want to specify a brief description of the candidate and select hobbies,
    So that my profile can be more personalized with additional details that may help in matching me to suitable opportunities.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=62378-58547&t=uY2xP4dMRl179HBq-4

    Acceptance Criteria:

    #

    Acceptance Criteria

    01

    Scenario: User inputs information in the "About" section.
    Given I am on the personal details page,
    When I enter a description in the "About" field,
    Then the entered information should be displayed correctly.

    image-20250310-081748.png

    02

    Scenario: User selects hobbies.
    Given I am on the personal details page,
    When I search and select hobbies from the provided list,
    Then the selected hobbies should be displayed correctly.

    03

    Scenario: User can search hobbies.
    Given I am on the personal details page,
    When I use the search field to search for hobbies,
    Then the search results should show relevant hobbies for selection.

    04

    Scenario: No hobbies are selected by default.
    Given I am on the personal details page,
    When I view the "Hobbies" section,
    Then it should show "No hobbies selected" if no hobbies have been selected.

    05

    Scenario: User can remove selected hobbies.
    Given I have selected hobbies in the "Hobbies" section,
    When I remove a hobby,
    Then the removed hobby should no longer appear in the list of selected hobbies.

    06

    Scenario: The user can save new info in the "About and Hobbies" section.
    Given the user has entered all necessary information in the "About and Hobbies" section,
    When the user clicks the ‘Save’ button (that is sticky to the bottom),
    Then the entered details in the "About and Hobbies" section should update and be reflected on the page.

    07

    Scenario: The user can cancel without saving changes.
    Given the user is in the "About and Hobbies" section,
    When the user clicks the ‘Cancel’ button (that is sticky to the bottom),
    Then the page should close without saving any changes and revert to the previous state.

  • Story 1.4.3.6. CRM. Profile Edit Mode – Personal: Job requirements

    Content

    General info

    The Job Requirements section allows users to input their current position, salary expectations, and employment preferences in the Profile Edit Mode. This section includes fields such as current salary, desired salary range, employment type, current employment status, availability, willingness to travel, preferred work locations, and industries. The section helps in gathering the user’s job preferences to tailor future opportunities and recommendations.

    User story

    As a CRM user,
    I want to specify job requirements, including current salary, desired salary range, employment type, availability, and willingness to travel,
    So that my job preferences can be captured and used for better matching to potential opportunities.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=62378-58547&t=uY2xP4dMRl179HBq-4

    Acceptance Criteria:

    #

    Acceptance Criteria

    01

    Scenario: User edit position.
    Given I am on the job requirements page,
    When I select current job position
    Then the value should be selected and displayed correctly.

    image-20250310-083106.png

    02

    Scenario: User inputs current salary in the "Current salary" field.
    Given I am on the job requirements page,
    When I enter a salary in the "Current salary" field (not mandatory),
    Then the value should be saved and displayed correctly.

    03

    Scenario: User inputs desired salary range values.
    Given I am on the job requirements page,
    When I enter values for "Desired Salary from" and "Desired Salary till" (mandatory)
    Then both values should be displayed correctly, with a validation message if the range is invalid.

    04

    Scenario: User selects an employment type.
    Given I am on the job requirements page,
    When I select any employment type from the options (Permanent employment, Temporary, Part time),
    Then the selected employment type should be displayed.

    05

    Scenario: User selects their current employment status.
    Given I am on the job requirements page,
    When I select a status for "Current employment" (Not selected, Quit, Not under notice),
    Then the selected status should be displayed.

    06

    Scenario: User selects a notice period.
    Given I am on the job requirements page,
    When I select a value for "Notice period,"
    Then the value should be displayed correctly.

    07

    Scenario: User selects workload.
    Given I am on the job requirements page,
    When I set "Workload,"
    Then the value should be displayed correctly.

    08

    Scenario: User sets travel willingness and percentage.
    Given I am on the job requirements page,
    When I select a travel willingness option (e.g., Europe-wide, Worldwide),
    Then I should also be able to set the "Travel percentage" and both should be displayed correctly.

    09

    Scenario: User selects willingness to relocate option.
    Given I am on the job requirements page,
    When I select a willingness to relocate option (Yes, No),
    Then the option should be displayed correctly.

    10

    Scenario: User adds preferred work locations.
    Given I am on the job requirements page,
    When I add preferred work locations,
    Then these locations should be displayed correctly.

    11

    Scenario: User selects industries.
    Given I am on the job requirements page,
    When I search and select industries,
    Then the selected industries should be displayed correctly.

    12

    Scenario: The user can save new info on "Job requirements" section
    Given the user has entered all necessary information in the "Job requirements" section,
    When the user clicks the ‘Save’ button (that sticky to the bottom),
    Then the details entered in the "Job requirements" section should be saved in the profile.

     

    13

    Scenario: The user can cancel without saving changes.
    Given the user is in the "Job requirements" section,
    When the user clicks the ‘Cancel’ button (that sticky to the bottom),
    Then the page should close without saving any changes.