Причина проведення:

Дата проведення:

Учасники:

 Попередні обставини

Перелічіть у хронологічній послідовності події, які призвели до інциденту.

 Помилка

Опишіть, у чому проявляється некоректна робота внесених змін. Якщо можливо, доповніть візуальним представленням даних.

 Вплив

Опишіть, як інцидент вплинув на внутрішніх і зовнішніх користувачів. Вкажіть кількість звернень до служби підтримки.

 Виявлення

Зафіксуйте, коли і яким чином команда виявила інцидент. Опишіть, яким чином команда могла б виявити цей інцидент швидше.

 Реакція

Повідомте, хто відреагував на інцидент, які заходи було вжито і коли. Вкажіть, які були затримки або перешкоди для реагування на інцидент.

 Відновлення роботи

Зафіксуйте, що було зроблено з метою зниження негативних наслідків для користувачів і коли інцидент було усунуто. Опишіть, яким чином команда могла б усунути негативні наслідки швидше.

 Хронологія

Вкажіть терміни роботи над інцидентом. Додайте інформацію про попередні обставини, події після інциденту, а також про будь-які рішення та внесені зміни.

 Виявлення першопричини за методикою "П’ять "Чому""

Проведіть аналіз «Пять причин», щоб визначити справжні причини інциденту.

 Визначення першопричини без пошуку винних

Позначте кінцеву першопричину й опишіть, що потрібно змінити (при цьому не шукайте винних), щоб не допустити подібних інцидентів у майбутньому.

 Вивчення беклога

Подивіться, чи немає в беклозі розробки не внесеної до плану роботи, яка могла б запобігти інциденту або пом’якшити його наслідки.

 Пов’язані інциденти

Перевірте, чи не було в минулому інцидентів з такою самою першопричиною. Зазначте, яких заходів щодо зниження негативних наслідків було вжито для тих інцидентів, і з’ясуйте, чому подібний інцидент повторився.

 Уроки

Опишіть, що ви дізналися, що вийшло і що можна поліпшити.

 Подальші дії

Перелічіть завдання Jira, які були створені, щоб запобігти подібним інцидентам у майбутньому. Позначте, хто несе відповідальність, коли ця людина має виконувати свою роботу і де ця робота відстежується.

1. Estimated VS Spent time spent on the project (BE, FE, QA, PM, code review, total);

2. Time and number of bugs found by the client;

3. Additional client requests.

Project: OneLine: Migrol

Team: PM: Kate Hvozd ; FE: Andrij Rehush ; BE: val.b (Unlicensed) ; QA: Artem Makarov ; Team Leads: Artem Gnibeda , Honcharuk Oleh Pavlo Trukhin

Link to the Retrospective document – Retrospective

Conclusions

Description

Department

1. If there are a few emails in the row – each should be tested separately to make sure it was triggered by correct trigger (actition).

Win email sent before winning. Solution – Rewrite the logic.

(issue captured on the final tests, but developer said that it’s not easy to change the trigger, so we implemented some delay in email sending to cover this issue. However the client reported a bug anyway.)

DEVELOPEMENT PROCESSES

2. WP setup – Analyze the possible amount of fields and divide it accordinly to not exceed the limit or change the limit in advance.

some WP fields dissapered from theme settings because limits were reached.

Solution 1 – Changed the limits in WP. (The issue apeared after we’ve implemented a few new fields).

Solution 2 – New option pages for each option category !

Do not use repeater , divide to post types. (max input php)

DEVELOPEMENT PROCESSES

3. After each even small change the full functionality should be tested (even if it seems like the change is not connected to anything else. Including each email and their amount).

Links don’t work, the page reloads on click + triggers a duplicate email sending.

Solution – Links fixed, so they stopped trigerring the page reload and duplicate email sending.

DEVELOPEMENT PROCESSES

4. Set up correct receivers for emails that are triggered by crons. Be careful with transfers to prevent the code rewriting

Duplicated Reminder emails (and after fix appeared again)

Solution

• 1.06 (before launch) – changed the logic so users receive personalized emails and are o in the copy of each other

• 5.06 (after launch) – the fix made 1.06 was accidentally rewritten during some next transfer, so the fix was put back.

DEVELOPEMENT PROCESSES

5. Testing of the complicated functionality should include checkup of all the positive scenarios step by step. (To make sure that data saves correctely – accordingly to user actions)

Prize limits were reaching too fast as “-1” was on applied to more prizes then needed.

Solution: “-1” was applied to correct prize (not all the prizes form interests that were chosen)

Solution 2: Logging of each complicated step in the script’s operation!

DEVELOPEMENT PROCESSES CheITGroup

6. After form testing – always make sure that all the fields data appeared in WP and emails.

Sometimes some fields do not appear in the WP table (but saved in DB)

Solution:

• the frst time it was reported there were a few such cases. We haven’t found the reason why it happened and were monitoring it.

• then we assumed that the code should be rewritten but it will be too dangerous, so we’ve just moved the data from DB to the table and DB.

DEVELOPEMENT PROCESSES

7. Data protection when submitting a form

• Sanitizing form fields

• Check email validity! For example thomas.peter.rickli.@gmail.com

• Using wp_nonce

• Sending the form only through $_POST

• try cache

DEVELOPEMENT PROCESSES

8. Recapcha – deside on the confirmed development and QA flow.

Recapcha – was not working properly.

*There was no functionality at all!

QA

9. During the development of the forms the code should be anlyzed for the potential basic bot prevention

Basic bot prevention

DEVELOPEMENT PROCESSES

10. Double check the functionality after deployment on a live site

• checking changes in the code

• checking the functionality of the site/page

• the one who developed it is the one who transfers it

DEVELOPEMENT PROCESSES

QA

OneLine: Migrol

Incident #1 [Win email sent before winning]

30.05.2024 9:26 AM

(on live before launch)

“fyi: I don’t know if I should already start doing bugherd tasks, since you are also still testing, but I got the instant win email before I spun the wheel. The e-mail should be sent when I am on the instant prize page.”

Kate Hvozd val.b (Unlicensed)

Artem Makarov

Pavlo Trukhin

@Amire Berisha 

Rewrite the logic.

(PM captured this issue on the final tests, but developer said that it’s not easy to change the trigger, so we implemented some delay in email sending to cover this issue. However the client reported a bug anyway.)

If there are a few emails in the row – each should be tested separately to make sure it was trigerred by correct trigger (actition).

OneLine: Migrol

Incident #2 [some WP fields dissapered from theme settings because limits were reached]

31.05.2024 8:44AM

(on live before launch)

Kate Hvozd val.b (Unlicensed)

Artem Makarov

Pavlo Trukhin

@Amire Berisha 

Changed the limits in WP. (The issue apeared after we’ve implemented a few new fields).

Analyze the possible amount of fields and divide it accordinly to not exceed the limit or change the limit in advance.

OneLine: Migrol

Incident #3 [Links don’t work, the page reload on click – trigges a duplicate email sending]

3.06.2024 10:02 AM

(on live before launch)

•  IMPORTANT: ALL Links of the Prices don’t work. This Link here doesn’t work: https://prnt.sc/sU8p3Z5jI5JE It gets me over here

• Client called, they said they received 2 confirmation E-Mails when they won 5Rp, Mobility. Could you maybe check, I will as well

Kate Hvozd val.b (Unlicensed)

Artem Makarov

Pavlo Trukhin

@Amire Berisha 

Links fixed, so they stopped trigerring the page reload and duplicate email sending.

After each even small change the full functionality should be tested (even if it seems like the change is not connected to anything else. Including each email and their amaunt).

OneLine: Migrol

Incident #4 duplicated Reminder emails (and after fix appeared again)]

1.06 and 5.06

(on live before and after launch)

• 1.06 (before launch) – one more question: I did get the reminder Mail as well: https://prnt.sc/JJLDQGF5nhpcBut I did get like 3 of them, yours, mine and one with the name of the client. Do you know why?

• 5.06 (after launch) – Urgent Task again with the Reminder E-Mail. @Oliver Gehrig got like 12 Reminders: https://media.one-line.ch/QLqTXwA4

Kate Hvozd val.b (Unlicensed)

Artem Makarov

Pavlo Trukhin

@Amire Berisha 

• 1.06 (before launch) – changed the logic so users receive personilized emails and are o in the copy of each other

• 5.06 (after launch) – the fix made 1.06 was accidentally rewritten during some next transfer, so the fix was put back.

• Set up correct receivers for emails that are triggered by crons.

• Be careful with transfers to prevent the code rewriting

OneLine: Migrol

Incident #5 [Prize limits were reaching too fast as “-1” was on applied to more prizes then needed]

4.06.2024 4:37PM

(on live after launch)

 Car Wash for exmaple was won like more that 500 times today. In the backend I see this: https://prnt.sc/N5xSGxyHIAl_ and thats all of them.

Kate Hvozd val.b (Unlicensed)

Artem Makarov

Pavlo Trukhin

@Amire Berisha 

“-1” was applied to correct prize (not all the prizes form interests that were chosen)

Testing of the complicated functionality should include checkup of all the positive scenarios step by step. (To make sure that data saves correctely – accordinly to user actions)

OneLine: Migrol

Incident #6 [Sometimes some fields do not appear in the WP table (but saved in DB)

3.06 , 10.06.2024

(on live before and after launch)

3.06 – Question, all of the fields in the form are mandatory. But why was this data transferred from him to the backend? https://prnt.sc/ujBXgA1EzgVg 

10.06 –  I pulled out the lead list and in which ones the first or last name is missing.These are mandatory fields for us. Do you know why they are empty? https://prnt.sc/7haPj4nuYF7j

Kate Hvozd val.b (Unlicensed)

Artem Makarov

Pavlo Trukhin

@Amire Berisha 

• the fisrt time it was reportet there were a few such cases. We haven’t found the reason why it happended and were monitoring it.

• then we assumed that the code should be rewritten but it will be to dangerous, so we’ve just moved the data from DB to the table and DB.

After form testing – always make sure that all the fields data appeared in WP and emails.

OneLine: Migrol

Incident #7 Recapture

One-Line: Migrol/ One-Line

IN PROGRESS

Only for internal use

WP

000

22.04.24

03.06.24

Time Doctor

Internal cheitgroup.slack.com (Channels: “”)

external cheitgroup.slack.com (Channel = )

Invoice and Timedoctor report

Kate Hvozd

Rosarot

val.b (Unlicensed) (Artur Bulan )

Artem Makarov

Amire, (Egzon Cekaj – for important matters).

24.04 – 05.05

Разом з Arthur Bulan, Andrij Rehush, Valeriy Boyko, Kate Hvozd розробляли концепцію і функціональність майбутнього колеса фортуни:

• узгодили git flow і вбудовування в поточний проєкт win4win (де так само триває робота)

• спланували як буде побудована робота:

плагін ACF, бібліотелки для "розкрутки" колеса фортуни, WP плагін колеса фортуни, у якого позичили функціонал розрахунку ймовірності

• опрацьовували кожен крок роботи, концепцію, архітекруту

• reestimate

Уже було проведено перший Code Review + періодичні зідзвони з приводу того чи іншого функціоналу

06.05 – 10.05

The functionality was taken from the WordPress Lucky Wheel plugin:

• calculation of sampling probabilities of a particular sector

• connection to sendgrid API (this plugin class is used)

Synchronization of languages between migrol site and win4win will be implemented through options of ACF PRO plugin

13.05 – 17.05

Preparing a template for testing

• Optimization translations and settings on ACF options pages

• setting up hosting for cron job + use of Advanced Cron Manager plugin

20.05 – 26.05

• implementation and testing of iframe insertion functionality

• finalization of translations based on ACF options

• checking and customizing cron jobs on ISP panel of live site hosting

27.05 – 02.06:

• bug fixing and research the problems

• CRON configuration (with the WP Control plugin)

• SendGrid API configuration

• The LiteSpeed Cache plugin configuration

• all preparatory work for the project launch

03.06 – 09.06:

• bug fixing and research the problems!

• SendGrid API check configuration

10.06 – 23.06:

• bug fixing and research the problems!

• SendGrid API check configuration

• Adding Google Recaptcha V2

• Add global logging for all cron events

• Working with site security and repelling attacks

24.06 – 07.07:

• Modify and add global logging for all cron events

• Sending 20,000 letters

• Advertising campaign stop

08.07 – 14.07

No updates this week

Desktop ?

Mobile ?

Block structure ?

To leave a comment use account

developers@one-line.ch

GrBXUff7R6jgyH8W

• to open inbox: https://outlook.live.com/owa/

Nus49413

RIV&Po|d5831

Kate’s number +380931688286

migrol.stage.one-line.ch

https://gitlab.cheitgroup.com/cheitgroup/developing/one-line-projects/LINE

https://migrol.stage.one-line.ch/wp-admin/

admin

Fumc8Yka6

server: migrol.stage.one-line.ch

user: line

password: jwRzxDKn

port: 22

https://migrol.stage.one-line.ch/phpmyadmin

DB_NAME: line_wp_7081

DB_USER: line_wp_7081

DB_PASSWORD: gcPnGu213ln4eWrF

USE VPN to login to gmail

access to vpn:

https://protonvpn.com/

login: oneline2022
password: @@5jUt5AU2_@X@W

Choose SWIZERLAND

access to gmail:

kronoswissws@gmail.com
Tuesday_20%_SKCH

2fa is on 078 934 72 23 = Severin Bucher (OneLine)

Sendgrid Account:
Win4Win
C2sy3Nr#cD&SwGK