| Month | Worked | Days worked | Tasks done | Planned | Spent on tasks |
|---|---|---|---|---|---|
| November 2026 | 31h 02m | 5 | 19 of 28 | 30h 00m | 26h 30m |
| October 2026 | - | - | - | - | - |
| September 2026 | - | - | - | - | - |
| August 2026 | - | - | - | - | - |
| July 2026 | - | - | - | - | - |
| June 2026 | - | - | - | - | - |
← 2026-11-15 2026-11-16 2026-11-17 →
8 of 8 tasks done · planned 8h 00m · spent on tasks 8h 00m
| Priority | Task | Estimate | Spent | Status | Result and updates |
|---|---|---|---|---|---|
| 1 | T-0066 Ask to close the previous task When someone reports on a new task while an earlier one has reports but isn’t finished, the bot asks in their channel whether it is finished, with Yes and Not yet buttons Deliverable: Unfinished tasks get closed and the boss no longer sees old tasks stuck “in progress” |
1h 30m | 1h 45m | Done Over estimate |
Result: now when moving on to another task it asks you have you finished task u worked on before
09:32 · started local server made plan and now boss can see plan when a employee made it (0h 30m) 10:03 · making so the app asks u to close task before moving to next (0h 30m) 10:34 · made so it asks to close task before moving on (0h 30m) 11:03 · tested now ask feature (0h 15m) |
| 2 | T-0067 Test the new features in real Slack Check channel posts, prompts in the channel, the /report redirect, the boss’s add, reorder and delete messages, and the close-previous-task question Deliverable: Everything works with real people, and any bugs are written down |
1h 30m | 1h 15m | Done | Result: Everything works, no bugs found.
10:35 · testing the new asking feature (0h 15m) 11:34 · testing features (0h 30m) 12:05 · ested channels, prompts, the close question and the boss controls in real Slack. (0h 30m) |
| 3 | T-0068 Task numbers in Slack task lists Show the task number (T-0042) in the plan confirmation, the clock-in and clock-out lists and the report form dropdown Deliverable: Every task shown in Slack has its number |
0h 30m | 0h 30m | Done | Result: Every task shown in Slack has its number
13:36 · Task numbers are done (0h 30m) |
| 4 | T-0069 Block unregistered people and send a welcome message Unknown Slack users cannot use the bot, and registered employees get a welcome message Deliverable: An unregistered user is refused and a new employee receives the welcome message |
1h 30m | 1h 30m | Done | Result: unregistered users cant use bot and new users get welcome message with comands and quick tutorial how to use them
14:07 · working on a unregistered users getting block if try too use the bot (0h 30m) 14:38 · made so unregistered users are blocked to use bot (0h 30m) 15:10 · made also welcome messages to new users (0h 30m) |
| 5 | T-0070 Fix user guide wording Reread docs/user-guide.md after the channel changes and fix unclear text Deliverable: The guide matches how the bot works now |
0h 30m | 0h 30m | Done | Result: reread docs/user-guide.md and updated it to match how the bot works now
15:37 · fixed user guide (0h 30m) |
| 6 | T-0071 Upgrade the dashboard UI Make the weekly view work on a phone and show a small tasks-done-of-planned bar under each name Deliverable: The boss can read the weekly view on his phone and see task progress per person |
1h 00m | 1h 00m | Done | Result: Dashboard now works on phones: fixed name column, progress bar per person, scrollable menu, bigger tap targets. Checked at phone size, all tests pass.
16:02 · working on a phone view of a dashboard (0h 30m) 16:33 · finshed uphrading UI (0h 30m) |
| 7 | T-0072 prepare app to launch it on a real server Check what is needed before launching on a real server. Write the server setup steps and a plan for moving the current data. Also test the app in production mode locally and add a health page that shows whether the scheduler is running. Deliverable: A deploy guide (docs/deploy.md), a clean run in production mode, and a /health page |
1h 00m | 1h 00m | Done | Result: A deploy guide (docs/deploy.md) with the server steps and how to move the data, a clean production-mode run, and a /health page.
17:16 · made a .md file for launch (0h 45m) 17:32 · Checked what is needed to launch on a real server and wrote the deploy guide (docs/deploy.md): install, settings, Nginx and HTTPS, scheduler, Slack URLs, moving the data, backups. Tested the app locally in production mode: all pages work and errors show no details. Added a /health page that shows whether the database and the scheduler are working. Tests added, all pass. (0h 15m) |
| 8 | T-0073 Buffer for fixes Time for bugs found while testing and anything that overruns Deliverable: Found problems are fixed |
0h 30m | 0h 30m | Done | Result: Code checked and the escaping bug fixed. Boss-change and “Saved” messages now appear in the report channel.
18:00 · Checked the code for outdated text and bugs. Fixed a bug where a task title with Slack markup (like @channel) could ping everyone; typed text is now escaped everywhere. Moved the boss’s “added / changed / removed a task” messages and the “Saved” confirmations into the person’s report channel, with a private-chat fallback. Tests added, all 350 pass. (0h 30m) |
Tasks you added. Dāvis Galla does not see them until they are put into the plan.
| Asked | Answered | Report | |
|---|---|---|---|
| 09:31 | 09:32 | started local server made plan and now boss can see plan when a employee made it | |
| 10:03 | 10:03 | making so the app asks u to close task before moving to next | |
| 10:34 | 10:34 | made so it asks to close task before moving on | |
| 10:35 | 10:35 | testing the new asking feature | |
| 11:03 | 11:03 | tested now ask feature | |
| 11:34 | 11:34 | testing features | |
| 12:05 | 12:05 | ested channels, prompts, the close question and the boss controls in real Slack. | |
| 13:35 | 13:36 | Task numbers are done | |
| 14:07 | 14:07 | working on a unregistered users getting block if try too use the bot | |
| 14:38 | 14:38 | made so unregistered users are blocked to use bot | |
| 15:09 | 15:10 | made also welcome messages to new users | |
| 15:37 | 15:37 | fixed user guide | |
| 16:02 | 16:02 | working on a phone view of a dashboard | |
| 16:33 | 16:33 | finshed uphrading UI | |
| 17:04 | 17:16 | made a .md file for launch | |
| 17:32 | 17:32 | Checked what is needed to launch on a real server and wrote the deploy guide (docs/deploy.md): install, settings, Nginx and HTTPS, scheduler, Slack URLs, moving the data, backups. Tested the app locally in production mode: all pages work and errors show no details. Added a /health page that shows whether the database and the scheduler are working. Tests added, all pass. | |
| 18:00 | 18:00 | Checked the code for outdated text and bugs. Fixed a bug where a task title with Slack markup (like @channel) could ping everyone; typed text is now escaped everywhere. Moved the boss’s “added / changed / removed a task” messages and the “Saved” confirmations into the person’s report channel, with a private-chat fallback. Tests added, all 350 pass. |