Story 1.4.3.1. CRM. Profile Edit Mode – Professional Information

Content

[ Content ] [ General info ] [ User story ] [ Visual design: ] [ Acceptance criteria ]

General info

This user story covers the ability for users to edit professional experience, education, and skills in the CRM profile. It ensures that the candidate’s professional background and skill set are accurately recorded in the system. Users can interact with modal windows for adding both professional experience and educational qualifications, including detailed fields such as job title, company, degree, start and finish dates, tasks, and additional documentation.

User story

As a CRM user,
I want to edit professional experience, education, and skills in the CRM profile,
So that the candidate’s career history, academic background, and competencies are accurately reflected.

Visual design:

https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=62473-546196&t=4u4fWPJlX8GNC8UX-4

	Acceptance criteria
01	Scenario: The user can edit an existing professional experience entry. Given the user is editing a professional experience entry, When the user modifies the job title, company, or dates and clicks ‘Save’, Then the updated experience details should be saved in the profile. Modal window “Edit position“: Story 1.4.6.3. CRM. Profile Edit Mode – Add job position modal
02	Scenario: The user can remove a professional experience entry. Given the user is editing the professional experience section, When the user clicks ‘Delete’ next to an experience entry, Then the job entry should be removed from the profile.
03	Scenario: The user can edit an existing education entry. Given the user is editing an education entry, When the user modifies the school name, degree, or dates and clicks ‘Save’, Then the updated education information should be saved. Modal window "Edit Education": Story 1.4.6.4. CRM. Profile Edit Mode – Add education modal
04	Scenario: The user can remove an education entry. Given the user is editing the education section, When the user clicks ‘Delete’ next to an education entry, Then the entry should be removed from the profile.
05	Scenario: The user can edit existing skills. Given the user is in profile creation mode, When the user modifies the level of skills and clicks ‘Save’, Then the skill should be updated in the profile.
06	Scenario: The user can delete a skill. Given the user is editing the skills section, When the user clicks ‘Delete’ next to a skill, Then the skill should be removed from the profile.

March 10, 2025

Story 1.4.6.2. CRM. Profile Creation Mode – Professional Information

Content

[ Content ] [ General info ] [ User story ] [ Visual design: ] [ Acceptance criteria ]

General info

This user story covers the ability for users to add and manage professional experience, education, and skills in the CRM profile during the profile creation process. It ensures that the candidate’s professional background and skill set are accurately recorded in the system. Users can interact with modal windows for adding both professional experience and educational qualifications, including detailed fields such as job title, company, degree, start and finish dates, tasks, and additional documentation.

User story

As a CRM user,
I want to enter and manage professional experience, education, and skills in the CRM profile,
So that the candidate’s career history, academic background, and competencies are accurately reflected.

Visual design:

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

	Acceptance criteria
01	Scenario: The user can add a professional experience entry (position). Given the user is in profile creation mode, When the user clicks ‘Add Experience’ AND enters details such as job title, company, dates, etc in modal window Then the new job experience should appear in the professional experience section. Modal window “Add position“: Story 1.4.3.2. CRM. Profile Edit Mode – Add job position modal
02	Scenario: The user can add an education Given the user is in profile creation mode, When the user clicks ‘Add Education’ or ‘Add additional education’ AND enters the school name, degree, and dates in modal window Then the education information should be saved in the profile. Modal window "Add Education": Story 1.4.3.3. CRM. Profile Edit Mode – Add education modal
03	Scenario: The user can add skills. Given the user is in profile creation mode, When the user enters a skill name in the search bar and clicks ‘Save’, Then the skill should be saved in the profile. Interaction: The user can start typing in the skills section to see suggestions and select a relevant skill.

Acceptance criteria

01

Scenario: The user can add a professional experience entry (position).
Given the user is in profile creation mode,
When the user clicks ‘Add Experience’
AND enters details such as job title, company, dates, etc in modal window
Then the new job experience should appear in the professional experience section.

Modal window “Add position“: Story 1.4.3.2. CRM. Profile Edit Mode – Add job position modal

02

Scenario: The user can add an education
Given the user is in profile creation mode,
When the user clicks ‘Add Education’ or ‘Add additional education’
AND enters the school name, degree, and dates in modal window
Then the education information should be saved in the profile.

Modal window "Add Education": Story 1.4.3.3. CRM. Profile Edit Mode – Add education modal

03

Scenario: The user can add skills.
Given the user is in profile creation mode,
When the user enters a skill name in the search bar and clicks ‘Save’,
Then the skill should be saved in the profile.

Interaction: The user can start typing in the skills section to see suggestions and select a relevant skill.

March 7, 2025

Story 1.4.1.8. CRM. Profile Creation modal window on listing page

Content

[ Content ] [ General info ] [ User story ] [ Visual design: ] [ Acceptance criteria ]

General info

The "Create Talent Profile" form allows users to add new talent profiles by providing necessary details such as first name, second name, email, and market preference. The form includes validation to ensure all required fields are filled and correct options are selected.

User story

As a CRM user,
I want to create a new talent profile by filling in the required fields
So that I can add a new talent to the system from CRM directly.

Visual design:

https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=61265-61584&t=so8svCNBmzJWCajC-4

	Acceptance criteria
01	Scenario: Clicking on "Create Profile" from the listing page. Given I am on the Talent Profiles listing page, When I click on the "Create Profile" button, Then the modal window with the profile creation form should appear.
02	Scenario: Submit the form with all required fields filled. Given I am on the "Create Talent Profile" page, When I fill in all required fields (first name, second name, email, and market), Then the "Save" button should be enabled, and I should be able to submit the form.
03	Scenario: Validation when required fields are empty. Given I have not filled in a required field, When I try to submit the form, Then a validation message should appear for the empty field(s). EN: Please fill in this field. DE: Bitte füllen Sie dieses Feld aus.
04	Scenario: Validation when market option is not selected. Given I have filled in the first name, second name, and email correctly, When I do not select a market option, Then the form should show a message indicating that a market must be selected. EN: Please select one of the options. DE: Bitte wählen Sie eine der Optionen aus.
05	Scenario: Successfully submitting with a market selection. Given I select a market option (Switzerland, Germany, or Both markets), When I submit the form, Then the profile should be created with the chosen market option saved. AND see the toas green message “Talent profile created successfully“ / “Talentprofil erfolgreich erstellt“ AND shown on the listing page at the top without reload the page

March 7, 2025

Epic 1.4.6. CRM. Talent Profile creation mode

Content

[ Content ] [ General info ] [ User stories ] [ Visual design ]

General info

Epic ticket:

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

User stories

Visual design

https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=24649-150341&t=Hj6EIWi3xA7e3iA3-4

March 7, 2025

NA Release notes 03.2025

March 7, 2025

Release Notes 06.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/10485
Date	6 мар. 2025 г.
Version	Release NA 06.03.2025 [1.1.24]
Description
Contributors	Dasha Rozhniatovska Anton Liakh Ihor Bushtakov

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-6904	[Support] Error message is shown for Leadership questions in the interview	Bug
RT-6885	[CRM] [Company] [Editing] The "The industries field is required." message is shown after trying to save canges on company editing tabs	Bug
RT-6855	[Support] [Vacancy Preview] The address of the vacancy is not fully shown on the Vacancy Preview	Bug
RT-6836	[Publication] Fix rejection email templates	Bug
RT-6807	[Process] Verify/fix deactivation and emails process	Investigation
RT-6802	[Process] Change status to Shared in "by download" after downloading Zip	Task
RT-6750	[CRM] [Company] [Market] The prefilter by market is not set on the Company listing page	Bug
RT-6739	[Applications] [Filters] The prefilter by "New" status is missing. Also the “Market” prefilters are not shown	Bug
RT-6714	[CRM] [Company] [Market] The prefilter by the market is not set when the Company page is opened	Bug

Summary

The Rocken-Talent Release NA 06.03.2025 introduces important bug fixes and improvements. The release primarily addresses issues related to CRM, application filtering, and process handling. Key updates focus on resolving bugs in the company and market-related filters, and fixing various issues with vacancy previews and leadership questions in interviews.

New Features

Process Updates: Added functionality to automatically change status to "Shared" after downloading the Zip file.
Email Template Fixes: Resolved issues with rejection email templates for publications.

Improvements to existing features

CRM Company Editing: Improved functionality when saving company editing changes, particularly related to the industry field.
Vacancy Preview: Improved the display of addresses in vacancy previews.
Market Filters: Fixed issues with the prefilter by market on company listing and applications filtering pages.

Bug fixes

Leadership Questions: Resolved error messages showing for leadership questions in the interview process.
Company Listings: Fixed the market prefilter issue when opening the company listing page.
Process Handling: Addressed bugs with deactivation processes and email triggers related to status changes.

March 7, 2025

Sprint 90 review

1. General info

Sprint Number	90
Sprint Duration	26.02.2025 – 11.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 11 · 2:00 – 3:00pm (Europe/Kiev) Video call link: https://meet.google.com/kaq-saxx-ire

2. Sprint goal

Planned Sprint Goals	German market Go live Order roles adjustments CRM Profile view mode PDF optimization
Goal Achievement	German market Go live Order roles adjustments

3. Completed work on production (Demo Items)

№	User story / Task	Presenter
1.	German market
	RT-6756	Viktoriia
	RT-4752	Viktoriia
	RT-4756	Viktoriia
	RT-4754	Viktoriia
	RT-4758	Viktoriia
	RT-6393	Viktoriia
	RT-6761	Viktoriia
	RT-6839	Viktoriia
	RT-6823	Viktoriia
	RT-6759	Viktoriia
2.	CRM Orders
	RT-6684	Viktoriia
	RT-6685	Viktoriia
	RT-6717	Viktoriia
	RT-6820	Viktoriia
3.	Talent Profile view mode in CRM
	RT-6617	Viktoriia
	RT-5368	Viktoriia
4.	Other tasks
	RT-5216	Viktoriia
	RT-6324	–
	RT-6802	–
	RT-6836	–
	RT-6807	–
	RT-6904	–
	Automation tests, bugfix, BI board page, changes in Jobch category tags, etc	–

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

№	User story / Task	Presenter	Demo notes
	PDF optimizarion
	RT-6799	Yurii
	Talent Profile view page in CRM
	RT-6616	Ihor
	RT-6618	Ihor
	RT-6637	Ihor
	RT-6641	Ihor
	RT-6646	Ihor
	RT-6650	Ihor
	RT-6667	Ihor

5. Work NOT completed

User story / Task	Next steps
RT-2451	test current fixes create 5 additional tasks
RT-6321	Finish this task next sprint
RT-5754	Finish this task next sprint
RT-6320	Finish this task next sprint
RT-6405	Sentry will be checked next sprint
RT-6428	depends on current optimization results
RT-6427	depends on current optimization results

6. Metrics & Sprint Performance

Metric	Value	Comments
Planned hours	319h
Remaining hours	214h	Most of the remaining tasks are ready on stage
Sprint Velocity	105h	Completely finished tasks in the sprint by Definition of done
Bugs Reported [Critical/High/Medium/Minor]	82 5/41/36/0
Bugs Fixed	63

March 6, 2025

Sprint reviews

March 6, 2025

Release Notes 05.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/10421
Date	4 мар. 2025 г.
Version	Release NA 05.03.2025 [1.1.21]
Description
Contributors	Yurii Tymchuk Dasha Rozhniatovska Anton Liakh Ihor Bushtakov

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-6858	[CRM] [Vacancy] The “management consultant” user is automatically assigned to the “consultant” field while creation of the vacancy with order	Bug
RT-6857	[CRM] [Vacancy/Publication] The "Consultant"/"Recruiter" field can not be edited in the Vacancy/Publication with the Order	Bug
RT-6856	[CRM] [Order] [Vacancy] 422 error is shown while trying to edit the order in a vacancy (vacancy with order)	Bug
RT-6854	[Support] [Profile Preview/PDF] The candidate’s full address is not shown in Profile Preview/PDF	Bug
RT-6850	[CRM] [Order] [Vacancy] 500 error is shown after trying to add the order to the vacancy (if it’s publications do not have the added order, or if it has the publications, one or a couple of them have the order)	Bug
RT-6849	[CRM] [Order] [Vacancy] Add the proper EN/DE texts on the "Add order" popup	Bug
RT-6844	[Support][CRM] [Company staff] [E-mails] Some emails are not sent to the company staff (sharing) because a lot of company staff do not have a gender	Bug
RT-6839	Adapt "Erläuterung.pdf" for German market	Task
RT-6835	[CRM] [Process] [Sharing] The email is not sent to the company staff if the attachments were added while changing the Process status	Bug
RT-6834	[CRM] [Process] [German AGB] The DE Cover Letter consists of 5 pages but it is written that the file has 6 pages	Bug
RT-6832	[CRM] [Profile] [Market] The Market is not shown in the Profile after sending the Interview to the applicant	Bug
RT-6823	CRM/RT/Interview. Currency in the system based on market	Task
RT-6820	[Vacancy] Order is automatically assigned to all associated publications of the vacancy	CR
RT-6800	[Support] [Company] [Staff] HoD and Sales Manager can not add the staff to the Company	Bug
RT-6797	[RJ] [Home page] The banner is missing in the Hero section on the Home page	Bug
RT-6796	[CRM] [Orders] Remove the restriction to add the vacancy/publication only to the "Active" order	Bug
RT-6793	[CRM] [Profile] There is no placeholder avatar if the Applicant applied to the DE Publication	Bug
RT-6792	[CRM] [Order] Only the first step of the order can be filled if the Order is created directly from the Vacancy creation form	Bug
RT-6791	[CRM] [Profile] [Categories] Fix the view of the Categories in CRM (e.g. Profile listing page)	Bug
RT-6790	[CRM] [Order] [Create Vacancy] The “Company”, “Order”, and “Management Consultant“ fields are not inherited from the Order while creating the Vacancy from the Order page	Bug
RT-6789	[CRM] [Order] The 404 error is shown after trying to create the Publication from the order if there are no vacancies assigned to the Order	Bug
RT-6786	[CRM] [Order] The admin role can not be selected in the "Sales/Account manager" field	Bug
RT-6780	[CRM] [Vacancy] The order can not be added to the existing vacancy	Bug
RT-6779	[CRM] [Vacancy] The “Management Consultant” field does not need to be shown in the Vacancies with no order	Bug
RT-6778	[CRM] [Vacancy with order] 500 error is shown when opening the Vacancy that has the order	Bug
RT-6776	[CRM] [Profile] [Header] The “edit” icon is missing near the “RT” label on the Profiles listing page	Bug
RT-6775	[CRM] [Profiel] [Header] Add the icons in the Header according to the design	Bug
RT-6774	[CRM] [Profile] [Header] The whole area of the “change status” button has the “hand” cursor but not the whole area is clickable	Bug
RT-6772	[CRM] [Profile] [Header] The “change avatar” button is not centered. The color of the button’s background is not set	Bug
RT-6771	[CRM] [Profile] [Header] There is no comma between the first and last name in Header	Bug
RT-6761	[Process] Attach dedicated PDF for Germany	Task
RT-6759	[Company][User] Allow to assign German users as contacts in companies	Story
RT-6758	[Support] [Process] 500 error is shown while trying to set the process status to "Interview 2"	Bug
RT-6757	[Support] [RJ] The timeout error is shown while posting some publications on RJ	Bug
RT-6756	RJ old. Profil erstellen for different markets	Story
RT-6752	[Support] [Interview] Some hard skills can not be chosen in the Interview	Bug
RT-6750	[CRM] [Company] [Market] The prefilter by market is not set on the Company listing page	Bug
RT-6742	[CRM] [Profiles] [Application tab] Remove extra columns ("Applicant", and "Current Position" columns)	Bug
RT-6741	[RJ] [DE] The "Top-Kategorien", "Beliebte Standorte" are missing in Header and the "Offene Stellen" block is missing on the Home page	Bug
RT-6739	[Applications] [Filters] The prefilter by "New" status is missing. Also the “Market” prefilters are not shown	Bug
RT-6738	[RJ] [DE] The application can not be finished because of the mobile number error	Bug
RT-6737	[CRM] [Processes] [Market] The market is not shown under the Candidate’s name	Bug
RT-6735	[CRM] [All listing pages] [Market] The market is not shown under the User’s name	Bug
RT-6734	[CRM] [Publication] [Market] Remove the market icon near the publication name on the Publications listing page	Bug
RT-6733	[CRM] [Publication] [Market] Remove the "Market" field from the Publication page and add the market icon near the Company name	Bug
RT-6725	[RJ] [CRM] [Company/Publication] The id of the Company/Publication is not changed after changing the market of the Company.	Bug
RT-6723	[RJ] [Company/Publication] [Market] The wrong link is opened on RJ if the market of the Company was changed	Bug
RT-6721	[CRM] [Company] The "CHF" currency is shown in German Company in salary range	Bug
RT-6719	[CRM] [Company/Order/Vacancy/Publication/Processes] The market icons near the company name are not size-fixed on the Company/Order/Vacancy/Publication/Processes listing pages	Bug
RT-6717	[Filters] Update according to the new Order requirements	CR
RT-6715	[CRM] [Company] [Market] [Creation] The market is not prefiltered on the Company creation page	Bug
RT-6714	[CRM] [Company] [Market] The prefilter by the market is not set when the Company page is opened	Bug
RT-6713	[CRM] [Company] [Market] [Edit mode] The "Market" field is shown for all roles	Bug
RT-6712	[CRM] [Company] [Market] The icon with the market is not shown near the name on the Company listing page	Bug
RT-6711	[Support] [Publications] [Production] The titles of the blocks in RJ are different from the CRM. The information in the blocks is mixed up	Bug
RT-6710	[Company] [Market] The market is written in lowercase in the Company Header	Bug
RT-6709	[Company] [Market] The market is not shown in the Company and can not be changed	Bug
RT-6708	[Support] JobsCH. Cut the length of tags	Task
RT-6695	[Support] Open the BI board link for access, do not add to CRM menu	CR
RT-6685	[Support] Update the Vacancies	CR
RT-6684	[Support] Update the Orders	CR
RT-6655	[Support] [Application/Profiles] The Profile is reassigned sometimes to other users after sending the Interview	Bug
RT-6621	(BE) CRM. Talent Profile view mode. Main Header	BE sub-task
RT-6620	(FE) CRM. Talent Profile view mode. Main Header	FE sub-task
RT-6617	CRM. Talent Profile view mode. Main Header	Story
RT-6591	[Support] [Process] Internal CRM page is opened after scanning the QR code on the shared profile PDF	Bug
RT-6549	[Support] Company with the exact name is not shown in the dropdown during vacancy creation	Bug
RT-6539	[CRM] [RJ] [Publication] The 400 error is shown after opening the Publication in RJ from the CRM	Bug
RT-6501	[Emails] Consultant’s phone number is not shown in the emails	Bug
RT-6393	RJ. Publications for Germany	Task
RT-6324	[Profile] Do not display address in shared profile before Company Accepted status	Story
RT-5823	(BE) companies for Germany	BE sub-task
RT-5822	(FE) companies for Germany	FE sub-task
RT-5815	(BE) vacancies for Germany	BE sub-task
RT-5814	(FE) vacancies for Germany	FE sub-task
RT-5811	(BE) processes for Germany	BE sub-task
RT-5810	(FE) processes for Germany	FE sub-task
RT-5807	(BE) applications for Germany	BE sub-task
RT-5806	(FE) applications for Germany	FE sub-task
RT-5368	CRM. Talent Profile view mode. Tab applications	Story
RT-5216	CRM. Company. Industries must be mandatory during creation and editing	Task
RT-4758	CRM processes for Germany	Story
RT-4756	CRM applications for Germany	Story
RT-4754	CRM vacancies for Germany	Story
RT-4752	CRM companies for Germany	Story

Summary

The Rocken-Talent Release NA 05.03.2025 [1.1.21] focuses on significant updates related to the German market implementation, with comprehensive adjustments to orders and roles within the CRM system. These improvements ensure better handling of market-specific data, as well as smoother processes for vacancy and publication management. Key enhancements include mandatory industry fields during company creation, better synchronization between vacancies and orders.

New Features

German Market Implementation: Added support for publications specific to the German market. Significant updates to processes, vacancies, and applications tailored for the German market and launched German Rocken Jobs.

Improvements to existing features

Mandatory Industry Field: Industry is now a required field during company creation and editing.
Orders and Roles Adjustments: Enhanced handling of orders in relation to vacancies, publications, and roles like consultants and recruiters.

Bug fixes

Fixed issues related to missing fields, errors during order handling, and CRM interface elements like avatars and category views.

March 6, 2025

Sandbox: Synchronization Script

Overview

This script is designed to synchronize project files from a local directory to a remote server using rsync. Also, it executes a remote script after syncing. It can be useful for developers to quickly transfer data from their own computer to the sandbox to test changes.
The script can be downloaded from the GitLab repo.

Requirements

Python 3.x
SSH access to the remote server
rsync installed on both local and remote machines

Configuration

The script relies on a configuration file (config.json) to specify project details. Below is an example of the configuration structure:

{
    "config": {
        "sandbox_host": "test.sandbox.rockengroup.com",
        "user": "rockenadmin",
        "ssh_port": 22,
        "remote_script": "rocken_deploy"
    },
    "projects": {
        "api": {
            "repo_url": "https://api.test.sandbox.rockengroup.com",
            "local_dir": "path_to_api_source",
            "remote_dir": "/home/rockenadmin/rocken/api",
            "excludes": [""]
        }
    }
}

The config section contains global settings for synchronization. The projects section defines individual projects that can be synchronized. Each project has its own configuration.

Configuration Fields:

Some variables that require review:

sandbox_host: Remote sandbox DNS address. Typically, the hostname follows the pattern of including the username along with sandbox.rockengroup.com, such as ivan.sandbox.rockengroup.com or viktoriia.sandbox.rockengroup.com.
projects: Section of projects with their sync settings.
local_dir: Path to the local directory.
excludes: List of files or directories to exclude from syncing. Empty by default.

Some defaults (probably does not require intervention):

user: Username for SSH authentication. Default: root. Do not change it.
ssh_port: SSH port number. Default: 22. Do not change it.
remote_script: Remote script to run remotely after syncing. Default: rocken_deploy. Do not change it.
remote_dir: Destination directory on the remote server. Do not change it.
repo_url: Url of the project in the sandbox. Not used

Installation

Copy the example configuration file before installation:
```
cp config.json.example config.json
```
Set the correct local directory path for necessary projects in the config.json file.
Define the DNS address of the sandbox in the config.json file.
Install the script as a system command:
- First, ensure the script is executable:
```
chmod +x rocken_sync.py
```
- Then, run the script with the install argument:
```
sudo python3 rocken_sync.py install
```
This will set the full path to the config.json file in the CONFIG_PATH variable in the script itself, and display an appropriate message about that.

Important: After the install step, please do not change the location of the config.json file, otherwise, it will cause an error when running the script.

Important: After the install step, please do not change the location of the config.json file, otherwise, it will cause an error when running the script.

After the installation, you can call the script directly from the terminal as rocken_sync.

Usage

To run the script with a project name, use the following command:

rocken_sync <project_name>

For example, to sync the api project:

rocken_sync api

Optional argument:

--config <path_to_config>

Allows specifying a custom configuration file.

Script Logic

Load Configuration: Reads config.json to retrieve project details.
Validate Input: Ensures the specified project exists and that required fields are set.
Check Local Directory: Verifies that the local directory exists before proceeding.
Sync Files via Rsync: Transfers files using rsync with --delete to remove outdated files.
Execute Remote Script: Runs the deployment script via SSH to rebuild project.
Handle Errors: Catches and displays errors if any commands fail.

March 5, 2025

Category: ROCKEN Documentation

Content

General info

User story

Visual design:

Acceptance criteria

Content

General info

User story

Visual design:

Acceptance criteria

Content

General info

User story

Visual design:

Acceptance criteria

Content

General info

User stories

Visual design

Summary

New Features

Improvements to existing features

Bug fixes

2. Sprint goal

3. Completed work on production (Demo Items)

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

5. Work NOT completed

6. Metrics & Sprint Performance

Summary

New Features

Improvements to existing features

Bug fixes

Overview

Requirements

Configuration

Configuration Fields:

Installation

Usage

Script Logic