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-6372	[CRM] "Model not found" error is displayed while changing the status for the candidate	Bug
RT-6370	(CRM) Fix Applicant Rejections & activation of Talents "Model not found error"	Task
RT-6365	(RT) Fix button and change "Anwenden" to "Bewerben" for Jobrequest and vacancies in RT	Bug
RT-6358	[Support] Update email in Profile	Task
RT-6357	[RockenJobs] Missing last features after NA release	Bug
RT-6356	[CRM] Head of division not able to see "Vacancies" during creating a process	Bug
RT-6349	[Roles] Allow BMs, HoD, Sales and Consultants to view publications	Bug
RT-6347	[Profile] Fix the title of the question	Bug
RT-6342	[Publication][Vacancy] Change the naming and order of the Beschreibung fields in Vacancies/Publications	Bug
RT-6334	[Interview] Fix frontend issues	Bug
RT-6329	[Talent] Replace "Bewerben" with "Anwenden" text for drop-down confirmation	Bug
RT-6325	[RJ] Not all the jobs seem to be published in feeds	Bug
RT-6315	[Support] [Vacancy] [Publication] 500 error during creating the publication from vacancy	Bug
RT-6313	[Support] [Profiles] Attachments tab is not shown for the CRM users except admins and responsible	Bug
RT-6298	[RJ] Update the LinkedIn feed	Task
RT-6297	[Support] [Process] The 422 error is shown while switching the process status from "Company invitation" to "Interview 1"	Bug
RT-6277	[Support] [Processes] Identical processes can be created	Bug
RT-6207	[Support] [Talent] Add default sorting by date (DESC – from newest to old) for the vacancies on the Jobs page	Task
RT-6150	RJ. Title for additional links is not displayed	Bug
RT-6145	[Support] [Profiles] "Invalid Date" is displayed after selecting from the date picker during adding the experience	Bug
RT-6132	[RT] [Profile Preview] The currency is shown in the Profile Preview if the salary is not set	Bug
RT-6047	[CRM] [Stage] [Profile Preview] The hobbies icons are broken in the Profile Previews (on stage)	Bug
RT-5468	[RT] [Education/Experience] [Attachments] The number of max size of the attachment is not shown in the attachments uploading modal	Bug
RT-5377	[RT] [CRM] [Education/Experience] The lists are not shown in the education/experiences in the preview mode on the “Professional” page	Bug
RT-2548	[Talent] [Experiences] The Documents icons are cropped if the doc title is long on the Profile => Professional page	Bug
RT-2520	[Talent] [My Requirements] The date in "month.year" format is shown on the “My request for a job” page, but in the form, the date in "day.month.year" format is shown	Bug
RT-584	CRM/RT. Update Reisebereitschaft selectors	Task

Summary

New Features

Improvements to existing features

Bug fixes

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-6353	(CRM) Reassign the Processes	Task
RT-6346	Rename Fields "Wie definierst du deine Reisebereitschaft" → "Umzugsbereit"	Bug
RT-6337	Fix Error in Sentry	Task
RT-6275	[Support] [CRM] [Test user] The test user is assigned as a responsible consultant to the profiles	Bug

Summary

New Features

Improvements to existing features

Bug fixes

Overview

The process for deploying a new sandbox droplet is initiated by a request from the QA team to create a new droplet for a new engineer. The QA engineer must provide their SSH key for access.

Deployment Process

Step 1: Request and Preparation

1. Request from QA: The QA team submits a request to create a sandbox droplet for a new engineer.

2. SSH Key: The new QA engineer provides their public SSH key.

Step 2: Terraform Deployment

Terraform automates the creation of resources, including the droplet, DNS records, and assignment of a reserved IP. The reserved IP ensures the droplet remains accessible even if it is redeployed.

Steps:

Open projects/qa/terraform.tfvars file

1. Add the QA engineer’s name to the qa_team variable list.

2. Run Terraform to deploy the necessary resources:

   terraform plan
   terraform apply

Terraform outputs the droplet name, IP address and DNS records after the deployment is complete.

Step 3: Update Ansible Configuration

Using Ansible ensures the droplet is always in the desired state, and any changes or redeployments are consistent with the predefined configuration.

Steps:

1. Add the droplet name, IP and username to the ansible/hosts.ini file in the sandbox block.

   [sandbox]
   test-sandbox-qa ansible_host=111.22.33.44 user=test

2. Save the QA engineer’s public SSH key

   ansible/roles/system-user-mgmt/files/ssh/test.pub

Step 4: Run Ansible Playbook

Execute the sandbox-init.yml playbook with the specifying only a specific droplet

docker-compose run --rm ansible ansible-playbook sandbox-init.yml --limit test-sandbox-qa

This playbook performs the following:

1. Updates the system on the droplet.

2. Installs necessary tools and packages (e.g., docker, nginx).

3. Generates SSL certificates using Certbot.

4. Updates the NGINX configuration for each service (api, crm, talent, rockenjobs) with predefined conf files.

5. Prepares the environment for application deployment:

   • Creates necessary directories:

   • Attaches the DigitalOcean S3 space to the system for storing database dumps and other files.

6. Deploys the latest version of the deployment script (rocken_deploy).

Step 5: Finalization

8. Add the new droplet IP address to the VPN configuration and restart it.

9. Add the new droplet IP address (not Reserved IP) to the SendGrid Whitelist (Settings/IP Access Management)

10. Provide the connection details (droplet IP, DNS records) to the QA team.

11. The QA engineer connects to the droplet via SSH (VPN required) and runs the deployment script to build and deploy applications from the GitLab repository.

Security

• VPN Access: Access to sandbox droplets and their DNS is restricted to connections through the corporate VPN, ensuring secure communication.

• Reserved IP: Each droplet has a reserved IP for consistent access.

Summary

The process ensures:

• Secure and consistent deployment using Terraform and Ansible.

• Sandbox droplets are always in the required state for QA activities.

• Simplified redeployment and configuration updates.

This workflow guarantees a reliable environment for QA engineers to perform their tasks efficiently and securely.

Questions:

• How many and which roles do we need?

• How often will their permissions change?

• For the roles, is flexibility or responsibility / accountablility more important for the new role system?

• Can new offices request new roles (e.g. Munich everybody can do everything)?

• How do we deal with people moving from recruiter to consultant?

  • What happens to their previous processes?

• How many roles can a person have?

• How do we deal with organizational changes in the system (like in March)?

  • How important is it to test changes upfront versus the effort to build such a system?

• How does the replacement logic work?

• How does the line of command work (team manager can see and edit their teams processes)?

  • When do processes get escalated?

  • Is this different for different levels?

  • How many levels are there?

• How does replacement work for team leads / BMs?

• Is it important to limit the access for certain roles?

  • For example: Everybody can see everything and roles are used to streamline processes.

 General info

 What needs to be improved?

• review service for translations (e.g. OneSky)
• Update documentation for the roles
• work with sentry
• add tasks for logs
• start RJ container
• plan time for small groups before refinement
• work with confluence and update all requirements only here
• Bug Hunter for support tasks, sentry, and release deployment

Content

General info

This story focuses on enabling recruiters to edit candidate profiles after the profiles are activated with the status “Active”. Additionally, a dedicated field to display the responsible recruiter should be added to the Profile Info section. This will improve profile management and ensure that the responsible recruiter information is clearly recorded and editable by authorized users.

User story

As a recruiter,
I want to edit candidate profiles after they become active and have the responsible recruiter stored in the profile information,
So that I can manage and update profiles efficiently while ensuring accountability.

Visual design:

https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=56738-428971&t=gCvYXC1iXBdanNDN-4

Content

General info

This story focuses on adding functionality to allow users to customize the fields displayed in the Profile Preview page. A 3-dot menu will be added in the top-right corner of the profile view, providing a View Settings option. This option will open a window where users can select or deselect fields to show or hide in the profile preview.

User story

As a CRM user,
I want the ability to customize the fields displayed in the Profile Preview through a View Settings menu,
So that I can tailor the profile information shown to my specific needs.

Visual design:

https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=52324-78221&t=gCvYXC1iXBdanNDN-4

Content

General info

This feature allows recruiters to schedule a publication for a future date. A new "Publication Date" field will be added, enabling recruiters to select a date in the calendar. Publications will remain in the "Draft" status until the scheduled date, at which point they will automatically switch to "Published" status. The lifetime of the publication will start from the selected date, ensuring accurate tracking.

User story

As a recruiter,
I want to schedule a publication date in the future,
So that I can plan and automate the publishing of job postings efficiently.

Visual design:

https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=19381-96471&t=e9W2mOrdWuITo2q8-4

Content

General info

User story

As a …

I want …

So that …

Visual design:

Content

Main folders

• General Info: Contains primary information about the documentation process and other activities on the project.

• Templates: Includes templates for Epics and User Stories.

• CRM: Houses Epics and User Stories related to the CRM system.

• TALENT: Contains Epics and User Stories specific to Rocken Talent.

• Rocken Jobs: Focuses on Epics and User Stories for Rocken Jobs.

• Corporate Website: Covers Epics and User Stories for the Corporate Website.

Guidelines

1) Each User Story must include:

• A general description

• The User Story itself

• Acceptance criteria written in Gherkin format (Given, When, Then).

2) Multiple User Stories addressing a specific functionality should be grouped into an Epic.

An Epic includes:

• A general description

• Links to related Jira tickets

• Associated design documents.

3) All Epics and User Stories must be linked to a Jira ticket in the “Add Description” sprint.

4) Upon completing the description, tickets should be moved to the “Product Owner Review” sprint for review.

5) Once approved, the ticket progresses to the “Ready to Estimate” sprint, where the team discusses it during the Refinement meeting.

6) After estimation, the ticket moves to the “Ready for Sprint” sprint.

• The Scrum Master and Product Owner prepare tickets for upcoming sprints.

• Final sprint commitments are made by the team during the Sprint Planning meeting.

7) Minor changes can be updated within the existing User Stories.

8) Major changes require creating new Epics or User Stories with links to the relevant existing items.