Theme

Category: ROCKEN Documentation

  • Story 3.2.2. RJ. Hero

    Content

    General info

    The Hero is a prominent section on the Rocken Jobs (RJ) main page, featuring a search field where users can enter the vacancy name or position, choose a city, and initiate a search to view relevant vacancies on the publication list page. This functionality is crucial for helping users quickly find suitable job openings.

    Additionally, the header section includes various animated elements such as a sphere, along with texts and logos to highlight the value propositions and trusted partner companies. The texts should be dynamic and engaging, emphasizing key benefits like a wide range of job opportunities, personalized recommendations, and dedicated consultant support.

    User story

    As a job seeker,
    I want to use the search field in the header to find vacancies by position and location,
    So that I can quickly view relevant job listings that match my search criteria on the publication list page.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=54391-28805&t=NTm4mK2SkjyVDMLS-4

     

    #

    Acceptance Criteria

     

    01

    Scenario: Search field visibility
    Given: the RJ main page is loaded
    When: the user views the header section
    Then: the search field should be visible, allowing users to input the vacancy name or position and select a city.

     

    image-20240928-191653.png

     

    02

    Scenario: Performing a search
    Given: the user has entered a vacancy name or position in the search field and selected a city
    When: the user clicks the "Search" button
    Then: the user should be redirected to the publication list page with the results filtered based on the entered criteria.

     

     

    03

    Scenario: Animated elements display
    Given: the RJ main page is loaded
    When: the user scrolls through the header section
    Then: an animated sphere should appear

     

    image-20240928-191627.png

     

    04

    Scenario: Partner logos display
    Given: the user is viewing the header section
    When: the page loads
    Then: the following partner logos should be visible: "amag" "IP”, “47", "MTF", etc.

     

    image-20240928-191801.png

    05

    Scenario: Display of key value proposition texts
    Given: the user scrolls down the header section
    When: the user views the bottom of the header
    Then: the following texts should be visible:

    • "Wide range of job opportunities"

    • "Personalized recommendations"

    • "Experienced consultant support from apply to offer."

     

    image-20240928-191830.png

  • Story 3.2.1. RJ. Main page. Header

    Content

    General info

    The Menu is a critical navigation element that appears at the top of the main page. It includes items such as "Products," "Salaries," "About Us," and "For Employers." This story focuses on making the menu easily editable through the WordPress CMS, enabling admins to update menu items and modify links as needed without code changes.

    User story

    As a website administrator,
    I want to be able to change the main page menu and update its links through WordPress,
    So that I can quickly manage and update the navigation structure without needing a developer.

    Visual design:

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=54391-27355&t=NTm4mK2SkjyVDMLS-4

     

    #

    Acceptance Criteria

     

    01

    Scenario: Menu visibility and default items
    Given: the main page is loaded
    When: the user views the header
    Then: the logo and menu should display with the following items:

    • "Products"

    • "Salaries"

    • "About Us"

    • "For Employers."

     

    image-20240928-190644.png

     

    02

    Scenario: Navigating through menu items
    Given: the menu is visible
    When: the user clicks on a menu item ("Products," "Salaries," "About Us," or "For Employers")
    Then: the page should redirect to the corresponding section or URL specified in WordPress.

     

     

    03

    Scenario: Editing menu items in WordPress
    Given: the administrator is logged into the WordPress CMS
    When: they access the menu editor
    Then: they should have the ability to edit, delete, or add new menu items and specify links for each.

     

     

    04

    Scenario: Saving changes to the menu
    Given: the administrator has edited the menu in WordPress
    When: they click the "Save Menu" button
    Then: the changes should be reflected on the RJ main page

     

    05

    Scenario: Search transformation on scroll
    Given: the user scrolls down on the main page
    When: the user scrolls past the Hero block
    Then: the search should appear in header instead menu

     

    image-20241001-133742.png

     

  • Epic 3.2. RJ. Main page

    Content

    General info

    This epic focuses on the Main Page of the Rocken Jobs (RJ) website. The main page serves as the central hub for navigation, showcasing key sections and menu items to guide users through the various parts of the site, such as product offerings, salary information, company details, and employer-specific content. The epic includes multiple stories addressing elements like the menu structure, content sections, and navigation logic, ensuring that users can intuitively explore and access the information they need.

    The stories also ensure that the menu and content management can be configured through the WordPress CMS, allowing administrators to easily modify menu items and links without requiring additional development efforts.

     

    Epic ticket:


    RT-4929

    User stories

    Visual design

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=54391-28773&t=1TTklKs8AAsmr4KG-4

     https://www.figma.com/design/zxM4jCEDpfZee9yw27l08k/Rocken-Components?node-id=1410-10101&t=LkrwzwOD1irytTnC-4

  • Story 3.1.1. RJ. XML feeds

    Content

    [ Content ] [ General info ] [ User story ] [ Acceptance Criteria ]

    General info

    Implement the functionality for generating XML feeds on the Rocken Jobs platform. The XML feeds will contain structured data about job vacancies, making it easy to share and distribute job information with external platforms and partners. The generated XML files should include all relevant fields, such as job title, location, company details, job descriptions, and application links, formatted according to specified XML schema standards.

    The purpose of this feature is to ensure that Rocken can maintain a standardized format for sharing job vacancy data across various external job platforms, improving visibility and reach for posted positions. This will facilitate data transfer and integration with external systems that consume XML-based job feeds.

    Technical documentation Feed XML

    User story

    As a Rocken CRM user responsible for vacancy data distribution,
    I want to generate XML feeds for job vacancies automatically,
    So that I can share the information with external platforms in a standardized format.

     

    #

    Acceptance Criteria

     

    01

    Scenario: Generating XML feed for vacancies
    Given: vacancies in the system
    Then: the system should generate an XML feed containing all vacancies with the correct fields according to the specified schema.

     

     

    02

    Scenario: XML schema validation
    Given: the XML feed is generated
    When: the feed is reviewed for schema compliance
    Then: the XML structure should match the defined schema format and include mandatory fields such as Job Title, Location, Company, Job Description, and Application Link Feed XML

     

     

    03

    OOS Scenario: Link to download XML feed
    Given: the XML feed is successfully generated
    When: the feed is ready for download
    Then: the user should see a download link for the generated XML file, allowing them to save it locally.

     

     

    04

    Scenario: Error handling for incomplete data
    Given: one or more vacancies are missing mandatory fields
    When: the user attempts to generate the XML feed
    Then: the system should display an error message indicating which vacancies are missing required fields and prevent XML generation until the issues are resolved.

     

    05

    Scenario: Updating XML feed
    Given: new job vacancies are added or existing vacancies are updated
    Then: the updated XML file should reflect all the latest changes, ensuring the feed is always up-to-date.

     

  • Epic 3.1. RJ. General functionality

    Content

    General info

     In this epic will be described general functionality for the website, for example XMLs

     

    Epic ticket:


    RT-4924

    User stories

    Visual design

     –

     

  • Release Notes – ROCKEN-TALENT – Release NA 23.09.2024 – Sep 25 12:22

    How to use this page

    The release notes on this page have been generated using the Jira issues macro. Each column of the table represents one of the issue fields you selected to include when you created these release notes in Jira.

    To edit any of these fields:

    1. Select Edit or type e to edit this Confluence page.

    2. Select the Jira issues macro table and then select the edit icon.

    3. Select Display options to adjust the columns and number of issues that will appear in your table of issues.

    4. Select Insert to save your changes.

    Learn more about the Jira issues macro

    Ключ Краткое описание Тип запроса
    RT-4761
    [CRM] [Migrations] Rework table has_company_staffs
         		Задача


    1 проблема

  • Release Notes – ROCKEN-TALENT – Release NA 19.09.2024 – Sep 25 12:22

    How to use this page

    The release notes on this page have been generated using the Jira issues macro. Each column of the table represents one of the issue fields you selected to include when you created these release notes in Jira.

    To edit any of these fields:

    1. Select Edit or type e to edit this Confluence page.

    2. Select the Jira issues macro table and then select the edit icon.

    3. Select Display options to adjust the columns and number of issues that will appear in your table of issues.

    4. Select Insert to save your changes.

    Learn more about the Jira issues macro



    Проблем: 5

  • Release Notes – ROCKEN-TALENT – Release NA 17.09.2024 – Sep 25 12:21

    How to use this page

    The release notes on this page have been generated using the Jira issues macro. Each column of the table represents one of the issue fields you selected to include when you created these release notes in Jira.

    To edit any of these fields:

    1. Select Edit or type e to edit this Confluence page.

    2. Select the Jira issues macro table and then select the edit icon.

    3. Select Display options to adjust the columns and number of issues that will appear in your table of issues.

    4. Select Insert to save your changes.

    Learn more about the Jira issues macro

    Ключ Краткое описание Тип запроса
    RT-4732
    Close links from public access
         		Задача


    1 проблема

  • Release Notes – ROCKEN-TALENT – Release NA 12.09.2024 – Sep 25 12:21

    How to use this page

    The release notes on this page have been generated using the Jira issues macro. Each column of the table represents one of the issue fields you selected to include when you created these release notes in Jira.

    To edit any of these fields:

    1. Select Edit or type e to edit this Confluence page.

    2. Select the Jira issues macro table and then select the edit icon.

    3. Select Display options to adjust the columns and number of issues that will appear in your table of issues.

    4. Select Insert to save your changes.

    Learn more about the Jira issues macro



    Проблем: 4

  • Retro Sprint 78

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

    Initiated by

    Andrii Kupriianov (PM)

    Reason

    Finished sprint

    Date

    24.09.2024

    Members

    Andrii Kupriianov Ivan Hodoniuk Dasha Rozhniatovska Anton Poliakov Olexandr Tikan Yurii Tymchuk Viktoriia Malysh Roman Kliuiko Anton Liakh

    Link to the board

    Retro Sprint 78 – https://ideaboardz.com/for/Rocken%20Sprint%2078/5387809

    Liked

    Lacked

    Learned

    Longed for

    • closed more important tasks in the sprint, good progress

    • feeling that we’are moving forward with a release.

    • it seems the most important part for migrations are done

    • Design are working too much forward from development. So it can be a problem in a future.

    • Lack of planning for the design tasks. To see a bigger picture.

    • Design periodical tasks organization.

    • Technical problem of communication inside the team.

    • relations for process migrations was not identified at the beginning

    • Fullstack tasks

    • optimization sql, slow requests on a new production

    • creates separated board for design tasks

    • Elastic Search

    • not standard certificate generation process

    • some new types of DNS records

    • start work with risks during estimations of the user story

    • Setup percentage of code covering tests

    • Work on design task estimation and overall preparation.

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

    • We need a plan for the implementation redesign of Rocken Talent (maybe on some separate meeting with the whole team) – post-release activity
    • For better estimation of big tasks use investigation tickets.
    • Arrange regular meeting for design tasks. Review ticket structure for design tasks (e.g. sections problem, goal, use cases, etc) – not relevant so far
    • Create and plan tasks for optimization of production
    • Create tasks for design documentation
    • Communication in the team in one environment (see the calendars each other, how to arrange a meetings, etc) – will be later in the Microsoft teams
    • Pay attention to the code quality, percentage of covering the code by tests. Optimization of test for memory – create a task for percentage of covering the code