Repository navigation
Agile-проекты: истории, спринты, релизы и MCP-планирование - #39
Merged
Merged
Conversation
added 30 commits
August 19, 2026 10:47
Three independent causes, all predating this branch (verified by running the suite at a93d0e5, where all 3 suites / 32 tests failed): - EmailService reads SMTP_HOST/SMTP_USER/SMTP_PASS via getOrThrow in its constructor, so the missing keys killed the Nest app at boot. - web-goal-reports-routing builds its own TestingModule and never provided TaskGoalQueryPort, which GoalController started requiring. - test-app.ts hand-maintains an entity list that had drifted from app.module.ts, missing AuthMethod, PushSubscription, ApiToken and Link. The entity-list drift is the same failure mode that BoardGroup hit in the previous commit. Worth replacing the hand-maintained list with a shared ALL_ENTITIES export, but that touches app.module.ts and is left out here.
CHECK constraints on BoardGroup can express self-references and the epic/story-vs-parentId shape, but not rules that need to look at other rows: a story's parent must itself be an epic (depth stays exactly 2), a group with children can't be reparented, and a task's groupId must belong to a group in the same project. BoardGroupConstraintsMigrationService creates the five SQLite triggers for these idempotently on every onApplicationBootstrap, since synchronize's rename/create/copy/drop dance silently drops triggers whenever board_groups' schema changes.
- Project.viewMode gains 'agile'; create/update DTOs validate it. - ProjectService seeds К выполнению/В работе/Готово columns on agile project creation, and on switching an existing project to agile if it has no columns yet. - MoveTaskDto accepts groupId; ProjectTaskService validates it exists in the target project before passing it to TaskRepositoryPort.updatePosition. - TaskService.update nulls groupId when projectId changes, so the trg_task_group_same_project trigger doesn't reject the PATCH.
use-board-dnd sends move without groupId, so treating an absent field as "clear it" meant one drag in board mode silently pulled a task out of its epic — an irreversible domain change driven by a display setting, which the design explicitly forbids. Absent groupId now means "leave unchanged", explicit null means "ungroup". The exception is a move to a different project: the group belongs to the old project, so carrying it over would trip trg_task_group_same_project.
Creating any epic or story returned 500: board_groups.userId is NOT NULL and the service never populated it. The whole feature was non-functional through the real API. 449 unit tests missed it because board-group.service.spec.ts mocks the repository, so schema constraints are never exercised there. Coverage for that gap now lives in test/board-groups.e2e-spec.ts, which drives the real HTTP API against a real SQLite schema — reverting this one line turns that suite red.
Review finding: the plan promised a test that deleting an epic cascades to its stories while its tasks survive with groupId nulled, but nothing exercised it — the unit test only asserted the repository mock was called and attributed the cascade to the FK without ever proving it. Deleting an epic is destructive, so "the FK probably handles it" is not good enough: a foreign_keys pragma being off, or a wrong onDelete, would take the user's tasks with it.
The sortable list inside a cell sized itself to its content, so an empty cell in a row 88px tall accepted drops only in a 20px strip at the top — 68px of dead zone. Aiming at the visibly empty cell of another column dropped the card outside any list and it snapped back, which reads as "tasks don't move between columns". Measured before: cellH 88 / dropH 20. After: cellH 88 / dropH 76 (the remaining 12px is the cell's own padding).
TaskCard runs its own PointerEvents drag engine. Past a 5px threshold it calls setPointerCapture, so every later pointer event goes to the card and Sortable never sees the drag — the card returns to where it started, which reads as "tasks don't move between columns". The user's console proved it: the only two messages were Telegram's "Changing swipes behavior" warnings, and disableVerticalSwipes is called from exactly one place — use-task-dnd, the custom engine. TaskCard now takes dndSource; AgileCell passes false so the card is a plain Sortable item. With the engine off the card also loses its onTap, so opening a task moves to a real click handler. Adds a guard test: removing the prop turns it red. Also keeps temporary [agile-dnd] logging in dev until the fix is confirmed on a real mouse. BoardColumn has the same conflict and is left untouched — see the task file's Known risks.
… panel The leading "Без колонки" lane ate horizontal space and pushed real columns off-screen on mobile. Board lanes are now exactly the project's columns; tasks with columnId === null surface in a new AgileBacklogPanel (Jira-style sidebar) instead. Dropping a task into the panel sends only columnId: null and omits groupId entirely so the task's epic/story assignment survives the move.
Drag between columns and to/from the backlog is confirmed working on a real mouse, so the [agile-dnd] trace has served its purpose.
Nesting read flat because it was expressed only by top borders and a header tint — horizontal bands, nothing enclosing. Epic now carries an accent rail and a hairline frame, story sits on a lighter surface with a thinner rail and an indented label. Frames are drawn with inset box-shadow rather than border or padding: a shadow takes no space, so the subgrid columns stay on the same verticals as the board headers. A literal inset rectangle is not available here — any margin or padding on a subgrid item shifts its tracks and breaks the alignment the whole layout exists for. Tasks attached straight to an epic now get their own 'Задачи эпика' band. Without it they rendered flush under the last story's tasks and read as belonging to that story — the UI was lying about where a task lives. Also: focus-visible rings and a press scale on the epic buttons, and a larger hit area on the collapse chevron.
On a board the card title is the densest, most repeated element, yet it was set at 14px — the same size as the column header and the epic title, so it competed with the labels that give the board its structure. 13px restores the ladder: story 12 → task 13 → epic and column 14. Only the compact variant changes; list views keep 14px, where the title is the primary element rather than one of forty.
…erging The card had no background at rest — only on hover — so on the board it was text sitting on the story band, not an object. Combined with the epic and story tints it produced one flat dark field: background 0.145, epic band 0.153, story band 0.160. Fifteen thousandths of lightness apart, which the eye reads as a single colour. The theme already ships the step: --card is 0.205 in dark, a designed elevation above --background. Compact cards now use it, with a border and a small shadow, and the two bands were pushed apart to 0.164 and 0.182 so the ladder is board < epic < story < card. Borders alone could not carry this: --border is white/10 in dark, which the UI/UX checklist calls out as effectively invisible. Card title also drops to 12px, and the story label goes muted so the two separate by brightness now that they share a size.
Everything was tinted at once — labels and the card area sat on nearly the same tone, so nothing marked where an epic ended or a story began. Roles are now split. The epic is a panel: its own surface, rounded corners, accent rail, and a real gap of board background above it, so each epic reads as a separate object. Labels are chrome painted on that panel — epic header lightest, story header a step below. The cell area stays canvas, which is what lets a card show up at all. Stories are divided by a hairline instead of a second fill, so a story reads as one unit with its cards rather than as another stripe. Dark-theme ladder: board 0.145, epic panel 0.170, story label 0.188, card 0.205, epic header 0.219.
…toggle
- Project.type ('simple' | 'agile') is now the single source of truth for
"is this project agile" — ViewMode drops back to 'list' | 'board' and no
longer drives any domain rule.
- ProjectCreateDialog gets a Обычный/Agile segmented control (default
simple, resets on reopen); ProjectEditDialog stays untouched (type is
immutable after creation).
- ViewModeToggle reverts to two buttons; ProjectView hides it and renders
the agile board whenever project.type === 'agile', regardless of the
project's (possibly legacy) viewMode value.
- TaskDetailDialog's goals-block visibility now reads project.type instead
of viewMode.
added 29 commits
September 29, 2026 17:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Что изменилось
Добавлена поддержка Agile-проектов: эпики и истории, backlog, спринты, релизы, ключи задач и планирование на доске.
История переносится в спринт вместе со своими задачами через меню или drag-and-drop. Задачи из закрытых спринтов сохраняют историю; новые задачи наследуют спринт истории. Завершение и удаление спринтов согласованы с группами и задачами.
MCP поддерживает создание, изменение, запуск, завершение и удаление спринтов, получение групп проекта и перенос истории вместе с задачами. Добавлена авторизация API-токенами на соответствующих API.
Проверка