Finish item 351: a plan read from a Jira Cloud epic
CI / tests (pull_request) Successful in 2m2s

This commit was merged in pull request #537.
This commit is contained in:
2026-11-14 19:59:23 +01:00
parent 3931eef451
commit c51c246c36
2 changed files with 5 additions and 11 deletions
+1
View File
@@ -2,6 +2,7 @@
## Unreleased
- A project config may name its plan as `jira:https://<site>/browse/<KEY>`: the plan is then read from the open child issues of that Jira Cloud epic, in backlog order, with the credentials in the config's `env-file`. Such a plan is only read so far: file, edit and finish its issues in Jira.
- A new `adf_codec` package converts markdown to ADF, the rich text of Jira Cloud and Confluence, and back with `@larvit/adf-codec` 0.3.1. It runs in a pinned Node container with a memory limit and no network, and returns adf-codec's error codes as a `Failure`. No tool calls it yet.
- The new `todo-item list [--release <version>]` prints the plan's items in the plan's order, `todo-item edit <ID>` sets an item's cells or detail, and `todo-item move <ID> --release <version>` moves it to another release; each change ranks the plan. Agents now read and change the plan's items only with `todo-item`, and the tools read the plan as it stands through one store, `bin/plan_store`, so a later backend can keep a plan outside `todo.md`. `todo-item list --release` with a bad version exits 2, and `finish <ID> --no-changelog` also drops an item no chunk built.
- A project's config may name the language its prose is written in (`language`) and templates for its commit titles, pull request titles and branch names (`commit-title`, `pull-request-title`, `branch`), in which `{id}` stands for the plan item's ID and `{summary}` for the one-line summary. The tools and the prose reviewer follow them. On a branch that fits the `branch` template, rule-hook's new `commit-title` rule refuses a commit title that doesn't fit, and `chunk-pr` such a pull request title. While a project's config holds a fault, rule-hook refuses every commit there.
+4 -11
View File
@@ -12,16 +12,15 @@
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 351 | 0.11.0 | | | **Read a project's plan from the child issues of a Jira Cloud epic its config names, ranked in Jira's backlog order.** | 4 | 2 | 3 | 7 | 5 | 1.6 by 6 | 1.2 |
| 379 | 0.11.0 | 351 | | **Convert every description of a plan read in one adf-codec container run, and take a heavy slot around the build of the codec's image.** | 3 | 2 | 3 | 6 | 4 | code health by 2, 1.5 by 2 | 3.2 |
| 378 | 0.11.0 | 351 | | **Name the branches, worktrees and commit and PR titles of a Jira plan's chunks by the issue key, as in `ABC-123` and `ABC-123 - ...`.** | 2 | 2 | 3 | 5 | 2 | 1.6 by 4 | 1.4 |
| 353 | 0.11.0 | 351 | | **Let a project's config take its goals and audience from a Jira epic's description, under the same two headings.** | 2 | 2 | 3 | 5 | 3 | 1.6 by 4 | 1.3 |
| 379 | 0.11.0 | | | **Convert every description of a plan read in one adf-codec container run, and take a heavy slot around the build of the codec's image.** | 3 | 2 | 3 | 6 | 4 | code health by 2, 1.5 by 2 | 3.2 |
| 378 | 0.11.0 | | | **Name the branches, worktrees and commit and PR titles of a Jira plan's chunks by the issue key, as in `ABC-123` and `ABC-123 - ...`.** | 2 | 2 | 3 | 5 | 2 | 1.6 by 4 | 1.4 |
| 353 | 0.11.0 | | | **Let a project's config take its goals and audience from a Jira epic's description, under the same two headings.** | 2 | 2 | 3 | 5 | 3 | 1.6 by 4 | 1.3 |
| 358 | 0.11.0 | | | **Let a project's config allow its runtime and tests on the host, and set the comprehension score under which code health is very important.** | 2 | 2 | 3 | 5 | 3 | 1.6 by 4 | 1.3 |
| 362 | 0.11.0 | | | **Send loop-claude's notices through the notifier a project's config names, with Mattermost as the first backend.** | 2 | 1 | 2 | 3 | 3 | 1.6 by 3 | 1.0 |
| 363 | 0.11.0 | 362 | | **Add a Slack backend to the notifier, sending each notice as a DM from a bot.** | 2 | 1 | 2 | 3 | 3 | 1.6 by 4 | 1.3 |
| 377 | 0.11.0 | | | **Hand a reviewer without a shell the plan as a listing `larv-review` writes into the review folder, whatever store holds the plan.** | 2 | 2 | 3 | 5 | 3 | 1.6 by 4 | 1.3 |
| 373 | 0.11.0 | | | **Pick the next release's chunks that may run at once by the files and the parts of files each is predicted to touch, and record the prediction beside what each merged chunk touched.** | 3 | 2 | 2 | 5 | 5 | 1.5 by 4, 1.4 by 2 | 1.3 |
| 352 | 0.11.0 | 351, 379 | | **Write a project's plan to its Jira epic: file items as child issues, edit those the loop filed, score unscored issues with a comment, and move a finished item to the status its config names.** | 3 | 2 | 3 | 6 | 5 | 1.6 by 6 | 1.2 |
| 352 | 0.11.0 | 379 | | **Write a project's plan to its Jira epic: file items as child issues, edit those the loop filed, score unscored issues with a comment, and move a finished item to the status its config names.** | 3 | 2 | 3 | 6 | 5 | 1.6 by 6 | 1.2 |
| 355 | 0.11.0 | | | **Store a record on the Confluence Cloud page its config names, as markdown converted through the adf-codec shim, and interrupt the human when a teammate saved the page since the loop read it.** | 3 | 2 | 3 | 6 | 5 | 1.6 by 6 | 1.2 |
| 356 | 0.11.0 | | | **Hand reviewers the review standards from the folder a project's config names, in place of `~/.claude/skills/larv-review/standards/`.** | 2 | 2 | 3 | 5 | 2 | 1.6 by 3 | 1.1 |
| 372 | 0.11.0 | | | **Key loop-claude's session, archive, routing state and config-folder commits per chunk, so two chunks of one project run side by side without touching each other's state.** | 3 | 2 | 3 | 6 | 6 | 1.5 by 3 | 0.4 |
@@ -86,12 +85,6 @@
## Details
### 351. Read a project's plan from the child issues of a Jira Cloud epic its config names, ranked in Jira's backlog order.
lilleman's calls, 2026-11-12. One epic is one project's plan. An item is a child issue: its key is the item's ID, so branches, worktrees and commit and PR titles follow `CLAUDE.md`'s ticket rules (`ABC-123`, `ABC-123 - ...`). Summary is the tagline, description the detail (ADF, read through the adf-codec shim). Release is the Fix Version, or what item 359 configures. Blocked by is the "is blocked by" link. L, E, I, S, Moves and Exempt are issue entity properties, so no Jira admin is needed; the computed score also shows as a label such as `score-2.4`. Jira's backlog rank decides the order, since the team sets it; the loop's score doesn't break ties, and the loop doesn't reorder anything others filed. Auth: email plus API token from the project's env file.
Item IDs stay `int`: the store holds the Jira project key from the config, and an issue's number is the item's ID, so the 30 or so modules that read an ID as an int stay as they are. The store refuses a child issue from another Jira project. This item only reads: `add`, `edit` and `finish` fail, saying item 352 builds them. lilleman's call, 2026-11-14: item 377 hands the plan to a reviewer without a shell, and item 378 names branches and titles by the issue key. Re-scored 2026-11-14 at L 4: a new pattern, HTTP to Jira Cloud with entity properties, rank and ADF, across plan_store and project_config.
### 379. Convert every description of a plan read in one adf-codec container run, and take a heavy slot around the build of the codec's image.
Two changes in `bin/adf_codec/`, in one item since both change the codec and its tests. Item 352 waits for this one. It waits for item 351, which adds `bin/plan_store/jira_epic.py`.