Content

General info

To enhance job visibility, the system needs to export job listings to the de.indeed.com platform via an XML feed. This feed should include publications from de.rocken.jobs and be formatted according to Indeed’s XML feed specifications. The job listings should be successfully transmitted to de.indeed.com, ensuring all necessary job information is included and formatted correctly.

User story

As a recruiter or system administrator,
I want to export job listings from de.rocken.jobs to the de.indeed.com platform via an XML feed,
so that the job listings can be published on de.indeed.com and be visible to potential candidates.

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

Content

General info

To expand the reach of job listings, the system should support the export of jobs to the Monster.de platform via an XML feed for de.rocken.jobs. This feed will include all necessary details from de.rocken.jobs, ensuring it is formatted correctly to meet Monster’s API requirements and can be successfully uploaded to their platform.

User story

As a recruiter or system administrator,
I want to export jobs from de.rocken.jobs to the Monster.de platform via an XML feed,
so that the job listings are published on Monster.de and can be accessed by potential candidates.

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

Content

General info

Tech docs – Jobs.ch

User story

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

Content

General info

https://api.staging.rockengroup.com/api-documentation-2000#/Publication%20-%20Feed after generation could be checked in DO https://space-rt-s.fra1.digitaloceanspaces.com/indeed.xml as was for jobsch (was refactor and added BEWERBEN_URL field) https://space-rt-s.fra1.digitaloceanspaces.com/jobs-ch.xml

User story

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

 

Content

General info

https://api.staging.rockengroup.com/api-documentation-2000#/Publication%20-%20Feed after generation could be checked in DO https://space-rt-s.fra1.digitaloceanspaces.com/linkedin.xml Added exception when try to generate file without publication (400 http error and FeedGenerationException in sentry) Rename description fields for publications: NA Beschreibung / Description -> Rolle / Role NA Einführung / Introduction -> Verantwortung / Responsibility NA Verantwortlichkeiten / Responsibilities -> Qualifikationen / Qualifications

Tech docs – LinkedIn

User story

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

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

 General info

 What needs to be improved in processes (1)?

• Add additional meetings in small groups before refinement
• Involve additional stakeholders to our team meetings
• Add more context and problematic info to the tasks for designers
• Build a processes on how to use glossary of terms

 What needs to be improved in documentation (2)?

• Write DevOps documentation
• Add onboarding and offboarding descriptions
• Use Definition of ready when preparing descriptions and tickets
• Keep up-to-date the descriptions and design before, during and after implementing features
• Involve more team members to update descriptions

 What needs to be improved in team collaboration (3)?

• Unclear topics should be covered better so that no reopens, follow-up bugs and tickets appear
• Introducing the stakeholders into the dev presentations can improve the collaboration
• Everyone should be involved on retrospectives for improvements

 What needs to be improved in management and planning (4)?

• implement process of change management
• switch to story points
• Planning based on understanding why we do things and how it will help users.
• bugs should not accumulate in the backlog in large numbers
• prepare more detail roadmap
• clean up the backlog

 What needs to be improved in visual design (5)?

• Sync storybook and design (list of variables)
• prepare a plan for RT new design implementation

 What needs to be improved in development (6)?

• Introduce team meetings before implementing a big feature like markets/role system before implementing so everyone is up to date
• Move to Vue3

 What needs to be improved in testing and quality (7)?

• Need to make new frontend with tests
• Need to add test coverage and metrics
• Add Test case like TestRail
• Involve QA at the stage of creating a description of tickets, and acceptance criteria (to describe more scenarios)

 What needs to be improved in release and support phase (8)?

• –

 What needs to be improved from our lessons (9)?

• –

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-6665	[CRM] Server Error When Opening Vacancy	Bug
RT-6619	[Profiles] Market is empty in profile collapse	Bug
RT-6598	[Users] Market checkbox is not saved after creating a new user	Bug
RT-6561	[Support] [Profile listing] Change the placeholder in the "Search keywords" search	Bug
RT-6530	[Support] Company description is not shown on the vacancy preview in the "Company Profile" tab	Bug
RT-6476	[RJ] Update the Indeed XML	Task
RT-6455	[Support] Update the JobsCH field	Task
RT-6431	[Support] [RT] [Recommended Jobs] Not filtered jobs are shown in the "Recommended Jobs" block	Bug
RT-5831	(BE) Talent profiles for Germany	BE sub-task
RT-2547	[Talent] [Experiences and other] [iOS Mobile – iPhone 14 Pro, iPhone 13] The error pages are not adapted to Mobile	Bug

Summary

This release includes various bug fixes, updates to job listing fields, and improvements to talent profile features. The main focus has been on resolving server errors, refining profile market displays, updating XML job feed integrations, and improving mobile adaptation.

New Features

• RT-6476: Update the Indeed XML integration.

• RT-6455: Update the JobsCH field for improved job listings.

Improvements to existing features

• RT-5831: Enhancements to Talent profiles for Germany, ensuring better accuracy in profile information according to the market.

Bug fixes

• RT-6665: Fixed a server error when opening a vacancy in CRM.

• RT-6619: Resolved an issue where the market field appeared empty in profile collapses.

• RT-6598: Fixed an issue where the market checkbox was not saved when creating a new user.

• RT-6561: Updated the placeholder in the “Search keywords” field in profile listings.

• RT-6530: Fixed an issue where the company description was not displayed in the vacancy preview under the “Company Profile” tab.

• RT-6431: Resolved an issue where unfiltered jobs were appearing in the “Recommended Jobs” block.

• RT-2547: Fixed errors on iOS mobile (iPhone 14 Pro, iPhone 13) where error pages were not adapted properly.

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-6661	[Vacancy Preview] The "Nohemi" font is used for texts	Bug
RT-6610	RT. Vacancy Preview. Adjust mobile version	Task
RT-6605	[CRM] [Publications] [Small screens] The size of the market icon is not fixed on the listings (e.g. Publication/Application)	Bug
RT-6585	RT. Vacancy Preview. Adjust tablet version	Task
RT-6511	[Support] [Profile] [Filters] The e-mails are cropped in the Profiles filters	Bug
RT-6499	[Publication] Add ID as the unique identifier	Task
RT-6451	[Support] [Processes] [Chat] The user still sees the processes in the chat that were reassigned from him to another user	Bug
RT-6418	[Support] [Processes] Add the "Created" status to the statuses filter	Bug
RT-6351	[Support] Some data is displayed with incorrect text wrapping	Bug
RT-6330	[Support] Blocked users continue to be available for assigning to different entities	Bug
RT-6300	[Support] Found results are still shown after filtering by responsible if the profiles were reassigned to another consultant	Bug
RT-6254	[Roles] Allow BMs, HoDs, Consultancy and Sales to reassign their Vacancies	Task
RT-6218	[Support] [Profiles] The numbers are shown with locations on the profile preview	Bug
RT-5631	[RJ] [New stage] Information about another company is shown after clicking the company in the “Beliebte Partnerfirmen” on the Home page	Bug
RT-5593	[RT] [Profile preview] The time fields are not styled on the “Interested” modal in the shared profile	Bug
RT-3711	[CRM] [Applications listing] [Rejection popup] The space is shown under the “Send email to candidate“ if the checkbox is unchecked	Bug

Summary

This release introduces improvements to various areas, such as the vacancy preview, CRM publications, support processes, and role permissions. Several bugs were fixed, including issues with UI elements like font usage and layout on mobile devices. Additionally, new features and adjustments have been implemented to enhance the user experience and streamline various functionalities in both the CRM and RT.

New Features

• Vacancy Preview: Updates made to adjust mobile and tablet versions of the vacancy preview.

• Publications: New ID added as a unique identifier for publications.

• Role Management: Allows Business Managers (BMs), Heads of Departments (HoDs), Consultancy, and Sales teams to reassign vacancies.

Improvements to existing features

• Mobile Version Adjustments: Mobile and tablet versions of the vacancy preview have been optimized.

• UI Adjustments: Fixed market icon size on small screens for CRM publications and applications.

• Profile Previews: Adjusted how time fields are displayed in profile previews.

Bug fixes

• Font Issue: Resolved a bug where the "Nohemi" font was improperly used for text in the Vacancy Preview.

• Email Display Issue: Fixed an issue where email addresses were being cropped in the profile filters.

• Filter Issue: Corrected the issue where blocked users were still available for assignment to entities.

• Reassignment Display Issue: Fixed the bug where the user could still see reassigned processes in the chat.

• Text Wrapping Issue: Corrected text wrapping issues when displaying data.

• Popup Display: Fixed a bug where additional space was shown under the “Send email to candidate” checkbox in the rejection popup.

• Company Info Issue: Resolved an issue where incorrect company information was displayed after clicking on a company in the “Beliebte Partnerfirmen” section on the Home page.

Content

General info

Implement middleware that checks if the user’s role matches the content of the page they are attempting to access. If the user’s role does not correspond to the content, the system should force a logout and redirect the user to the login page. Specifically, when a CRM admin accesses Rocken Talent, the user should be logged out and redirected to the login page instead of seeing the empty content on home page:

Additionally, a toast message should be displayed informing the user of the forced logout.

User story

As a CRM admin user,
I want to be logged out and redirected to the login page if I try to access Rocken Talent with an invalid role,
so that I can log in with the correct role to access the appropriate content.

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

Visual design:

https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=63232-114896&t=UlVST2DDCCwVAxi1-4

#	Acceptance Criteria
01	Scenario: Detect Invalid Role Access Given I am a CRM admin logged into the system, When I try to access a Rocken Talent page that requires a different role, Then I should be logged out of the system and redirected to the login page.
02	Scenario: Display Toast Message on Forced Logout Given I am logged in with a CRM admin role but try to access Rocken Talent, When the system logs me out and redirects me to the login page, Then I should see a toast message indicating that I need to log out and log in again to access the correct content.
03	Scenario: Role-Based Redirect to Login Page Given I am a CRM admin and try to access Rocken Talent, When the system identifies a role mismatch, Then I should be redirected to the login page to re-authenticate with the correct role.