Category: ROCKEN Documentation

  • Story 2.2.6.1. RT. Profile preview. Restrictions to apply the vacancy

    Content

    General info

    As far as the profile will be in status “In Progress”, “Interview” – the candidates must be UNABLE to apply to any of the Jobs in RockenTalent. Make the application buttons grey and unclickable. If the user tries to click on them, the tooltip must appear / or an error saying “You need to have a complete profile first” / “Du musst zuerst ein vollständiges Profil haben”

    They must be able to fill out the Interview as the first priority, but for now we’ll only block the Jobs application functionality:

    image-20240725-092518.pngimage-20240725-093113.png

    User story

    As a candidate

    I can’t apply to the vacancy in interview and in progress statuses

    So that helps complete profile on RT first

    Visual design:

     

    Acceptance criteria

     

    01

    Given: profile in CRM in statuses: in progress or interview
    AND vacancy preview page

    Then: don’t see apply button
    AND have ability to complete the profile info by clicking on “complete profile“

    info: “You need to have a complete profile first” / “Du musst zuerst ein vollständiges Profil haben”

    image-20240725-092518.png

    https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=52126-84330&t=xpv90lo5T7ZUVD5M-4

    image-20240807-104823.png

    02

    Given: finished interview with suggestions
    AND profile status Interview

    Then: don’t have any opportunity to apply

    03

    Given: finished interview
    AND profile status Active

    When: click Apply to the vacancy

    Then: successful application

  • Story 2.2.1.2. RT. Profile account. Invite profile to RT via interview

    Content

    General info

    Application page offers approval of the applicant via sending an interview:

    image-20240725-093527.png

    Email:

    image-20240725-093615.png

    Currently the button from the email leads to the separate interview page on RT, e.g. https://talent.rocken-talent.cheitgroup.com/candidate/interview/lkljexk

    User story

    As a consultant

    I want to invite candidates/profiles/talent to Rocken talent via interview

    So that helps invite some new candidates to RT from interview

     

    Visual design:

     

     

    Acceptance criteria

     

    01

    Given: Email to candidate about interview

    When: open email

    Then: see in the email 2 buttons: Go to interview, go to profile

    Locale::de => 'd-48f5a597d125422d8a677b517f141147',

    Locale::en => 'd-f48571778d7d4646b791f515d3346eb3',

    image-20240802-113328.png

    02

    Given: interview flow last page

    When: click “Login to rocken“

    Then: redirect to set password page

    image-20240806-073759.pngimage-20240725-101358.png

    03

    Given: profile in interview / In progres status
    AND any Rocken talent page

    When: click on the logo

    Then: redirect to set password page

  • Story 2.2.1.1. RT. Profile account. Invite profile to RT via process

    Content

    General info

    Application page offers approval of the applicant via sending a process:

    image-20240725-085951.pngimage-20240725-085912.png

    Currently the button from the email leads to the vacancy page with the answer buttons

    image-20240725-090245.png

    User story

    As a consultant

    I want to invite candidates/profiles/talent to Rocken talent via creating process

    So that helps invite some new candidates to RT from process

     

    Visual design:

     

     

    Acceptance criteria

     

    01

    Given: Process started by consultant request

    When: email is sent

    Then: see in the email 2 buttons: open page vacancy preview and create a profile in RT

    Single Vacancy sharing:

    • Locale::de => 'd-d8d3e94cc1d44a2a9bf2c194894c757a',

    • Locale::en => 'd-fb93f132b59544878fb09c05e327605d',

    image-20240802-120602.png

    Multiple Vacancy sharing:

    • DE: d-085a3cdc0d114c8eb1e878664fc5a8ec

    • EN: d-c8e6b48444ef485cbc0949b6456ab97b

    image-20240802-120821.png

    02

    Given: email with started process (request)
    AND candidate isn’t logged in to the RT

    When: click on the button “Open in my profile“

    Then: redirect to the password setting page

    03

    Given: email with started process (request)
    AND candidate is logged in to the RT

    When: click on the button “Open in my profile“

    Then: redirect to the homepage

    04

    Given: vacancy preview page

    When: click on the buttons “Interested“ / “Not interested“
    AND finish an interaction with the modal windows Story 2.3.1.3. Vacancy preview modals

    Then: redirect to the page with set password

    image-20240725-094939.png
  • Release Notes – ROCKEN-TALENT – Release NA 01.08.24 – Aug 01 18:42

    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


  • Release Notes – ROCKEN-TALENT – Release NA 29.07.2024 – Jul 30 11:12

    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


  • Retro Sprint 74

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

    Initiated by

    Andrii Kupriianov (PM)

    Reason

    Finished sprint

    Date

    30.07.2024

    Members

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

    Link to the board

    Retro Sprint 74 – https://ideaboardz.com/for/Rocken%20Sprint%2074/5343173

    Liked

    Lacked

    Learned

    Longed for

    • Releases

    • Demo

    • More stable system

    • Presentation the project from QA

    • Definition of ready, definition of Done

    • Slow DevOps processes

    • Not enough time for planning

    • Implementation of design

    • Some kind of notification for the designers (where to find a links) when we can test the new features implementations.

    • speed of transferring tickets to QA, because of new release flow

    • Where to put feedback for the small design improvements

    • Requirements for German market

    • Amount of tasks for finishing sprint

    • Issues with deployment + git flow

    • Leave ticket in to do column by the end of the sprint

    • Update and manage the work/tickets, not team members

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

    • Implement Definitions into project processes
    • Better styling the design, close to pixel-perfect (Dev)
    • Add a design review process – we can use time on retro to provide feedback
    • Agreed on design decisions with the design team
    • Start a deeper review of the CRM
    • Prepare for the German market – created description, need design
    • Actions for GIT to optimize deployment – post-release feature
    • Leave tickets in to do column by the end of the sprint
    • Releases on the staging on Tuesdays and Thursdays
  • Retro Sprint 73

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

    Initiated by

    Andrii Kupriianov (PM)

    Reason

    Finished sprint

    Date

    16.07.2024

    Members

    Andrii Kupriianov Ivan Hodoniuk Dasha Rozhniatovska Anton Liakh Anton Poliakov Olexandr Tikan Valya Stelmashenko (Unlicensed) Julia Yurii Tymchuk

    Link to the board

    Retro Sprint 73 – https://ideaboardz.com/for/Rocken%20Sprint%2073/5332401

    Liked

    Lacked

    Learned

    Longed for

    • Ticket estimation for sprint seems to be accurate

    • I liked the demo, but it needs to be a little faster (too much design, perhaps, but the task is big, so there were probably a lot of questions)

    • good progress with tasks

    • Planning of the workload for the next sprints, estimations of the tasks

    • Bug-hunter selection pre-sprint.

    • close/finish all tickets in sprint

    • Lacked Vika

    • review Rico’s task

    • A common understanding of what doesn’t work

    • Bugs prevent you from making/testing features

    • Ask more questions about tasks before doing them. Especially if something is not clear.

    • Learned about separate envs for QA, new flow for testing

    • Release based deployment.

    • I’m a little worried about adding or changing the functionality of something that’s already been done, which can delay the release.

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

    • Implement spillover planning
    • Time limits for Demo planning
    • Change the flow for support tasks, contact PM first
    • Describe and estimate tasks globally, not related to one page
    • Release based deployment
    • Setup new QA process – preparing QA env on stage

  • Epic 1.0.3. Email

    General info

    On staging (local, sandbox)

    On production

    • All mails should go from responsible person, if not assigned then wir@rocken.jobs is taken.

    • If mail goes to candidate it is sent from @rocken.jobs email. Otherwise is taken ordinary user(responsible) email as sender. 

    Epic ticket:

    User stories

     

    Visual design

     

     

  • PostgreSQL: Snapshooter restore DB

    If we need to restore a database for a period longer than 7 days, we can use a dump created with the external service http://SnapShooter.com .

    To do this, you need to go to the page and log in to the service. https://app.snapshooter.com/login

    Screenshot from 2024-07-31 10-48-23.png

    After entering your login and password, you will be taken to the service dashboard page.

    Screenshot from 2024-07-31 10-51-24.png

    After logging into the SnapShooter service control panel, you should navigate to the section with backups that were made according to the schedule. To do this, you need to click on ‘Backup Jobs’ (1), then select the desired backup job, in the screenshot, it’s ‘crm-prod-db-ON-prod-postgresql-db,’ and click on ‘View’ (2).

    Selection_012.png

    On the opened page, at the bottom, we will see a list of backups that we can use for restoring.

    Identify the backup you need and click the Manage button (1). In the screenshot, this is the backup from 2024-07-30 09:00:14.

    Selection_010.png

    After that, a page with the dump for the selected period will open. Here, we can download it (1), view instructions (2), or restore it to the current database (3).

    Selection_013.png

    In case we want to restore an existing backup to a database with the same name as the one from which the backup was made, we can use the ‘Restore’ button (3).

    After that, we need to select the name of the database we want to restore.

    Screenshot from 2024-08-26 20-13-07.png

    "And press the ‘Start Restore’ button, which will initiate the restoration process to restore the database with the same name."

    Preferably – Restoring from dump in new database

    If we want to restore the dump to a database with a new name, for example, crm-prod-db_v2, we can do this by downloading the backup. To do so, click the ‘Download’ button (1) shown in the screenshot above. This will start the process of downloading the database archive to your local computer.

    Screenshot from 2024-08-26 20-49-01.png

    Don’t pay attention to the database size, this is a test database.

    After the database archive is downloaded, we need to extract it. This can be done using the command gunzip crm-prod-db.sql.gz.

    Screenshot from 2024-08-26 20-59-46.png

    After that, we need to log in to our DigitalOcean account and create a new database where we want to restore the dump.

    In the dump file, we need to change SELECT pg_catalog.set_config('search_path', '', false); to SELECT pg_catalog.set_config('search_path', 'public', false);.

    Selection_014.png

    Then, go to the ‘Users and Databases’ section (1). At the bottom of the list of databases, there is a field for adding a new database (2), "Enter the name of the new database and click ‘Save’. (For example crm-prod-db-v2)

    Selection_015.png

    After that, using the psql command-line utility, we enter the following command. And

    psql -U crm-prod-user -d crm-prod-db-v2 -p 25060 -h prod-postgresql-db-do-user-8527978-0.j.db.ondigitalocean.com < crm-prod-db.sql

    where -U is the username, -p is the port, -d is the name of the database (in our case, this is the new database we created in the previous step), -h is the database server address, and crm-prod-db.sql is the name of the dump file.

    and press ENTER.

    After that, enter the database password, which is stored in 1Password (Postgresql PROD login), press Enter again, and wait for the data transfer process from the dump to complete.

    Enjoy.

  • PostgreSQL: Digital Ocean restore DB

    To restore a PostgreSQL database on DigitalOcean, there is a tool that can recover data for a period of 7 days. In order to restore the data, we need to:

    • Select the project in which we need to restore the database (in the image, it is snapshooter_test)

    Screenshot from 2024-07-26 13-27-26.png

    • After that, click on the desired cluster, which will take you to the management section of that cluster. (On the screenshot, it is: test-snapshooter-postgresql-14)

    Screenshot from 2024-07-26 15-21-07.png

    • Then, we need to click the blue "Actions"(1) button located in the upper right corner, and in the menu, select "Restore from backup" (2).

    Selection_003.png

    • After that, we can choose to create a new cluster from the most recent backup or from a specific period. If we want to restore from a specific period, we select the desired date and time and click "Restore to New Cluster." In the "Enter database name" field, we can either change it or leave it as default, based on your preference.

    Choose a good database name

    The new database name will be part of the host name for the cluster. Choose a good name, as this might be the new main database server for the forseeable future.

    Selection_005.png

    • After that, the process of creating the new cluster for the selected period will start. The status of this process is indicated by a blue progress bar located below the name of the new cluster.

    Selection_006.png

    • Once the process is complete, the new cluster will be created and ready for use.

    Selection_007.png

    • It will also be displayed in the list of databases for the selected project. It is worth noting that if a read-only node was connected to the server from which the backup was created, it will not be restored in the new cluster.

    Selection_008.png

    Enjoy (улыбка)

    Reconfigure Database settings in apps

    The restore creates a new cluster and you must configure the new host in all the apps that access it to work properly.

    Additional information: If you are sure that the old cluster is no longer needed, it can be deleted to save costs on infrastructure maintenance. However, you should only delete it if you are 100% certain that it is no longer needed—this is crucial because the backups created in the previous period will also be deleted along with the cluster.

    For the new cluster, if it will be used as the primary, a read-only node should be created.

    Additionally, if you decide to use the new cluster as the primary, the password and username will remain the same as when connecting to the old one; only the hostname will change. In our example, the old host was test-snapshooter-postgresql-14-do-user-8527978-0.j.db.ondigitalocean.com, and it became test-snapshooter-postgresql-14-jul-26-backup-do-user-8527978-0.h.db.ondigitalocean.com or if you using internal connection hostname (private VPC network ) private-test-snapshooter-postgressql-14-do-user-8527978-0.j.db.ondigitalocean.com was changed on private-test-snapshooter-postgressql-14-jul-26-backup-do-user-8.h.db.ondigitalocean.com .

    If we need to restore data from a period older than 7 days, we can use the Snapshooter service. Instruction how to restore database using the Snapshooter service