This commit is contained in:
@@ -2,6 +2,7 @@
|
||||
|
||||
## Unreleased
|
||||
|
||||
- `do-epic` starts an epic's runnable issues in order of score alone, not in Jira's backlog order. It scores each open issue that holds no scores, the ones people filed included, and comments on the issue why.
|
||||
- do-epic and `todo-item add` file issues as the Jira issue types the settings `jira-finding-type` and `jira-review-type` name, Task by default, and refuse before filing where the Jira project lacks the type, naming the types it has.
|
||||
- do-epic names the team's own label for each repo, from the `[label-repos]` table, when it tells a chunk's worker how to file a finding or a release review, and keeps `repo:<name>` for a repo the table doesn't name.
|
||||
- do-epic records a repo pick, and the summary of each sub-task it files, in the team's own spelling: a label from the `[label-repos]` table of its config, and a `sub-task-summary` template with `{label}` and `{Summary}`.
|
||||
|
||||
@@ -12,10 +12,9 @@
|
||||
|
||||
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|
||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||
| 470 | 0.15.0 | | | **Start an epic's runnable issues in order of score alone, scoring each open issue that holds no scores, the ones people filed included, so Jira's backlog order no longer decides what starts.** | 3 | 2 | 2 | 5 | 5 | 1.2 by 4, 1.6 by 3 | 1.5 |
|
||||
| 454 | 0.15.0 | | | **Start a do-epic chunk's issue as the team's board expects, by settings: assigned to the account do-epic works as, moved by a start transition and added to a board's active sprint.** | 3 | 2 | 2 | 5 | 4 | 1.6 by 4 | 1.1 |
|
||||
| 472 | 0.15.0 | 454 | owner | **Let a project's config name a working branch per epic, such as `TW-12345`, that chunks branch off, merge into and keep level with `main`, so a person merges the finished epic into `main` in one pull request.** | 4 | 2 | 3 | 7 | 7 | 1.5 by 6, 1.6 by 7 | 1.1 |
|
||||
| 467 | 0.15.0 | 454, 470, 472 | question | **Cut 0.15.0 as soon as items 449, 450, 453, 454, 468, 470 and 472 have merged, before its release review, and run that review in 0.15.1.** | 1 | 1 | 1 | 1 | 1 | | 0.0 |
|
||||
| 467 | 0.15.0 | 454, 472 | question | **Cut 0.15.0 as soon as items 449, 450, 453, 454, 468, 470 and 472 have merged, before its release review, and run that review in 0.15.1.** | 1 | 1 | 1 | 1 | 1 | | 0.0 |
|
||||
| 473 | 0.15.0 | | security | **Load no MCP server in a headless claude call that is denied tools, so text an outsider wrote cannot reach one.** | 2 | 2 | 2 | 4 | 3 | 4 by 4 | 5.0 |
|
||||
| 469 | 0.15.1 | | | **Move a do-epic parent issue whose sub-tasks a person filed to Release Ready once every sub-task has landed, and to Done once every sub-task is done, by transitions its config names.** | 3 | 2 | 2 | 5 | 4 | 1.2 by 4, 1.5 by 4, 1.6 by 3 | 3.1 |
|
||||
| 446 | 0.16.0 | | question | **Kill the process a stuck check names where its verdict is `stuck`, once the human says the recorded verdicts match what they would have done.** | 2 | 2 | 3 | 5 | 3 | 1.5 by 3 | 1.0 |
|
||||
@@ -79,32 +78,6 @@
|
||||
|
||||
## Details
|
||||
|
||||
### 470. Start an epic's runnable issues in order of score alone, scoring each open issue that holds no scores, the ones people filed included, so Jira's backlog order no longer decides what starts.
|
||||
|
||||
do-epic starts the issues it may run in Jira's backlog order (`scheduler.chunks`). It scores and ranks only the issues it filed itself (`planning.ranked_keys`); a person's issue holds no scores and keeps the rank the team gave it. The human asked, on 2026-11-20, that only the score decide priority on an epic such as TW-13503, where people filed every issue.
|
||||
|
||||
- As it plans, do-epic scores each open issue that may become a chunk and holds no scores: L, E, I, S and Moves against the chain of goals `ranking.py` uses (the epic's, then code health, then the repo's). It writes the scores to the issue's `plan-item` property, as `todo-item edit` does on a person's issue, with a comment, in the epic's language, telling the team the issue is scored and why.
|
||||
- Scores a person wrote, or that an earlier run wrote, stay as they are.
|
||||
- `scheduler.chunks` orders the runnable issues by score, highest first, with each blocker lifted above what it blocks, as `rank_todo.py` does. An issue that couldn't be scored comes last, in backlog order, and `--status` says why.
|
||||
- A sub-task is scored on its own, against its own repo's goals.
|
||||
- The board's rank of a person's issue stays as the team set it. Choice, made 2026-11-20: start order is do-epic's decision, the board order is the team's (goal 1.6). do-epic still re-ranks the issues it filed.
|
||||
- `--dry-run` prints the scores it would write and the order it would start in.
|
||||
|
||||
Touches:
|
||||
|
||||
- `bin/do_epic/planning.py`: `planned`, `ranked_keys`, `item_of`
|
||||
- `bin/do_epic/ranking.py`: `ranked` (small)
|
||||
- `bin/do_epic/scheduler.py`: `chunks`, `start_chunks`
|
||||
- `bin/do_epic/main.py`: `planned_and_started` (small), `status_printed` (small)
|
||||
- `bin/do_epic/backend/protocol.py`: `EpicStore`
|
||||
- `bin/do_epic/backend/jira.py`: `JiraEpic`
|
||||
- `bin/do_epic/backend/fake.py`: `MemoryEpic`
|
||||
- `bin/do_epic/backend/contract.py`
|
||||
- `bin/do_epic/dry_run.py`
|
||||
- `bin/do_epic/test_planning.py`
|
||||
- `bin/do_epic/test_do_epic.py`
|
||||
- `README.md`: `### Set up a project` (small)
|
||||
|
||||
### 454. Start a do-epic chunk's issue as the team's board expects, by settings: assigned to the account do-epic works as, moved by a start transition and added to a board's active sprint.
|
||||
|
||||
When a do-epic chunk starts, its issue stays as Jira holds it: unassigned, in New and outside the sprint. A team whose board shows who works on what, such as TW, where an issue being worked is assigned to the person, In Progress and in the active sprint, then sees nothing of the loop's work. Today each worker would have to do this by hand, from rules only some machines hold.
|
||||
|
||||
Reference in New Issue
Block a user