File items 448 to 455 into 0.13.0, so do-epic fits a team's Jira labels, workflow, issue types and merge rule
CI / tests (pull_request) Successful in 3m36s
CI / tests (pull_request) Successful in 3m36s
This commit was merged in pull request #636.
This commit is contained in:
@@ -6,12 +6,20 @@
|
||||
|
||||
`Bar = 0.1`
|
||||
|
||||
`Next ID = 448`
|
||||
`Next ID = 456`
|
||||
|
||||
## Items
|
||||
|
||||
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|
||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||
| 448 | 0.13.0 | | | **Read a team's own repo labels as do-epic's picks, through a label table in its config, and treat an item that has sub-tasks as split, so planning never files sub-tasks beside the team's own.** | 3 | 2 | 2 | 5 | 4 | 1.6 by 8 | 2.2 |
|
||||
| 452 | 0.13.0 | | | **Make do-epic's view of the Jira workflow settings: the statuses at which an issue unblocks the issues it blocks, and the moves the team's own automation makes, so do-epic makes none of those.** | 3 | 2 | 2 | 5 | 5 | 1.6 by 7, 1.5 by 3 | 2.1 |
|
||||
| 449 | 0.13.0 | 448 | | **Record do-epic's repo picks and sub-task summaries in the team's own spelling, such as `core-4` and `core-4: Bygg …`, as its config sets them.** | 2 | 2 | 2 | 4 | 3 | 1.6 by 6 | 2.0 |
|
||||
| 453 | 0.13.0 | | | **Make the issue types that do-epic and `todo-item add` file in Jira settings, since a Jira project such as TW has no Task type.** | 2 | 2 | 1 | 3 | 2 | 1.6 by 5 | 1.8 |
|
||||
| 450 | 0.13.0 | | | **Add `do-epic <EPIC-KEY> --dry-run`, which prints every Jira write planning would make and each chunk that would start, and makes none of them.** | 2 | 2 | 2 | 4 | 3 | 1.6 by 5 | 1.6 |
|
||||
| 455 | 0.13.0 | | | **Let a chunk file a follow-up issue that its own issue blocks, with `do-epic --file --blocked-by` and `--parent`, so a change a repo ships as two pull requests gets an issue for each.** | 2 | 2 | 1 | 3 | 2 | 1.6 by 4 | 1.4 |
|
||||
| 451 | 0.13.0 | | | **Add a project setting `merge = "human"`, under which a chunk leaves its pull request ready for a person to merge, and a do-epic chunk parks until the pull request is merged.** | 3 | 2 | 3 | 6 | 5 | 1.6 by 7 | 1.4 |
|
||||
| 454 | 0.13.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 |
|
||||
| 446 | 0.14.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 |
|
||||
| 77 | 0.14.0 | | | **Teach `bin/metric-bench` Go and TypeScript, rerun it once two projects' comprehension histories name places, and bring into review only a metric that tracks the panel.** | 4 | 2 | 1 | 5 | 6 | 1.1 by 7, 1.4 by 7 | 2.1 |
|
||||
| 196 | 0.14.0 | | decision | **Replay the architecture, principles, overrides and product-owner passes with `review-replay` on Opus 5.5 projects, record each run in the review-replay routing decision, and, where a run qualifies a rung, add back the code that lowers a pass to it.** | 2 | 2 | 3 | 5 | 2 | 1.4 by 3 | 1.2 |
|
||||
@@ -69,6 +77,167 @@
|
||||
|
||||
## Details
|
||||
|
||||
### 448. Read a team's own repo labels as do-epic's picks, through a label table in its config, and treat an item that has sub-tasks as split, so planning never files sub-tasks beside the team's own.
|
||||
|
||||
do-epic reads an item's repo only from a `repo:<name>` label. A team that labels each issue with its repo's name, or with a short name such as `twu-4` for `tenant-web-ui-4`, gets no issue counted as placed. Planning then predicts every open item's repos again and can file sub-tasks beside the ones the team filed, and the team's own sub-tasks never run. On TW-13503, nine items with 40 sub-tasks between them would have been split again, two of them under issues with open pull requests. docs/decisions.md → `do-epic: drives one Jira epic …` already says that on the first machine, an item's label that equals a repo's name names that repo.
|
||||
|
||||
- A table in do-epic's config.toml maps a team's label to a repo's name, such as `[repo-labels]` with `twu-4 = "tenant-web-ui-4"`. A label the table maps records a pick, as `repo:<name>` does, wherever a pick is read: planning, the scheduler, human tasks, findings, finishing and the chunk's own run.
|
||||
- An open item that has any sub-task counts as split. Planning never predicts its repos or files a sub-task under it, and the scheduler works it through its sub-tasks, as it does an item labelled `split-by-repo`.
|
||||
- Test it on the in-memory backend with an epic shaped as TW-13503: parents whose sub-tasks carry the team's labels, and an item labelled with a short name.
|
||||
- `scheduler.chunks` sits next to `start_chunks`, a place the comprehension seats found hard to follow; leave `chunks` easier to read than it was.
|
||||
|
||||
Touches:
|
||||
|
||||
- `bin/do_epic/repo_pick.py`: `recorded`, `of_label`
|
||||
- `bin/do_epic/split.py`: `split`, `finished`
|
||||
- `bin/do_epic/planning.py`: `planned`, `placed`, `answered`, `ranked_keys`
|
||||
- `bin/do_epic/scheduler.py`: `chunks`, `held_up`
|
||||
- `bin/do_epic/human_tasks.py`: `notifier_checkout` (small)
|
||||
- `bin/do_epic/finish.py`: `repo_of` (small)
|
||||
- `bin/do_epic/findings.py`: `written` (small)
|
||||
- `bin/do_epic/main.py`: `chunk_run` (small), `chunk_root` (small), `split_items_closed` (small)
|
||||
- `bin/do_epic/config.py`: `DoEpicConfig`, `load`
|
||||
- `bin/do_epic/test_repo_pick.py`
|
||||
- `bin/do_epic/test_split.py`
|
||||
- `bin/do_epic/test_planning.py`
|
||||
- `bin/do_epic/test_scheduler.py`
|
||||
- `README.md`: `### Set up a project` (small)
|
||||
|
||||
### 452. Make do-epic's view of the Jira workflow settings: the statuses at which an issue unblocks the issues it blocks, and the moves the team's own automation makes, so do-epic makes none of those.
|
||||
|
||||
do-epic counts an issue as done only where Jira's status category is done, and moves a finished chunk's issue to done itself, by `jira-finish-transition`. On a team whose CI moves issues through the workflow, both are wrong. On TW, CI moves an issue to Code Review when its pull request opens, to Release Ready when it merges, and to Done when it is deployed. So do-epic would move an issue to Done before it is deployed, and would hold every blocked issue until the blocker is deployed, though the team wants blocked work to start once the blocker's pull request merges.
|
||||
|
||||
- Settings in do-epic's config.toml name the statuses at which an issue unblocks the issues it blocks, such as `jira-unblock-statuses = ["Release Ready", "Done"]`; without them, Jira's done category counts, as today.
|
||||
- A setting says which moves the team's workflow makes on its own, so do-epic makes none of them. With the setting, a finished chunk moves no status and stops with no reason; `jira-finish-transition` then only closes the epic.
|
||||
- The epic's finishing waits until every issue is in Jira's done category, so release reviews follow the deploy.
|
||||
- `--status` names the status an issue waits to reach.
|
||||
|
||||
Touches:
|
||||
|
||||
- `bin/do_epic/config.py`: `DoEpicConfig`, `load`
|
||||
- `bin/do_epic/backend/protocol.py`: `EpicIssue` (small)
|
||||
- `bin/do_epic/backend/jira.py`: `found_of` (small), `finish_issue`
|
||||
- `bin/do_epic/scheduler.py`: `open_blockers`
|
||||
- `bin/do_epic/main.py`: `handed_on`, `split_items_closed`
|
||||
- `bin/do_epic/finish.py`: `due` (small), `still_open` (small)
|
||||
- `bin/do_epic/status.py`: `lines` (small)
|
||||
- `bin/do_epic/test_scheduler.py`
|
||||
- `bin/do_epic/test_main.py`
|
||||
- `bin/do_epic/backend/test_jira.py`
|
||||
- `README.md`: `### Set up a project` (small)
|
||||
|
||||
### 449. Record do-epic's repo picks and sub-task summaries in the team's own spelling, such as `core-4` and `core-4: Bygg …`, as its config sets them.
|
||||
|
||||
do-epic writes its own spelling into a team's Jira: a pick as `repo:core-4` and a sub-task's summary as `[core-4] <the item's summary>`. A team with its own convention, such as TW's label `core-4` and summary `core-4: Bygg …` with a capital after the colon, then finds two labels on each issue and summaries in a shape its board doesn't use. Goal 1.6 asks the loop to fit the tracker's conventions, not change them.
|
||||
|
||||
- do-epic records a repo pick as the team's label for that repo, from the label table item 448 adds, and as `repo:<name>` only for a repo the table doesn't name.
|
||||
- A summary template in do-epic's config.toml shapes each sub-task's summary, such as `sub-task-summary = "{label}: {Summary}"`, where `{Summary}` is the item's summary with a capital first letter. Without the setting, the summary stays `[<repo>] <summary>`.
|
||||
- `do-epic-claude` and `do-epic-human` stay as they are: no team label means either.
|
||||
|
||||
Touches:
|
||||
|
||||
- `bin/do_epic/repo_pick.py`: `label_of`, `record`
|
||||
- `bin/do_epic/split.py`: `task_summary`, `split` (small)
|
||||
- `bin/do_epic/planning.py`: `placed` (small), `answered` (small)
|
||||
- `bin/do_epic/config.py`: `DoEpicConfig`, `load` (small)
|
||||
- `bin/do_epic/test_repo_pick.py`
|
||||
- `bin/do_epic/test_split.py`
|
||||
- `README.md`: `### Set up a project` (small)
|
||||
|
||||
### 453. Make the issue types that do-epic and `todo-item add` file in Jira settings, since a Jira project such as TW has no Task type.
|
||||
|
||||
do-epic and `todo-item add` file every new issue as a Task, the name `plan_store/jira_epic.py` sets as `ISSUE_TYPE`. A Jira project without a Task type, such as TW, whose types are Feature, Bug, Chore and Investigation, refuses each one. So `do-epic --file` fails there, and so does the epic's finishing, which files a release review for each repo.
|
||||
|
||||
- A setting in do-epic's config.toml names the type a finding is filed as, and another the type of a release review, such as `jira-finding-type = "Feature"` and `jira-review-type = "Chore"`; Task stays the default.
|
||||
- A project config whose plan is a Jira epic takes the same `jira-finding-type` for `todo-item add`.
|
||||
- A type the project doesn't have fails before anything is filed, naming the types the project has.
|
||||
|
||||
Touches:
|
||||
|
||||
- `bin/plan_store/jira_epic.py`: `ISSUE_TYPE`
|
||||
- `bin/do_epic/backend/jira.py`: `JiraEpic.file`
|
||||
- `bin/do_epic/config.py`: `DoEpicConfig`, `load` (small)
|
||||
- `bin/do_epic/findings.py`: `written` (small)
|
||||
- `bin/project_config/settings.py`: `SCALARS` (small)
|
||||
- `bin/do_epic/backend/test_jira.py`
|
||||
- `README.md`: `### Set up a project` (small)
|
||||
|
||||
### 450. Add `do-epic <EPIC-KEY> --dry-run`, which prints every Jira write planning would make and each chunk that would start, and makes none of them.
|
||||
|
||||
`do-epic <EPIC-KEY>` writes to Jira before it starts any chunk: labels, sub-tasks, comments on a team's issues and a new backlog order. A person has no way to see those writes before they happen, so the first run on a team's epic is a gamble, and the writes can't be taken back in one step. On TW-13503 the first run would have filed duplicate sub-tasks and posted comments to the team.
|
||||
|
||||
- `do-epic <EPIC-KEY> --dry-run` runs planning and the scheduler against the epic as Jira holds it, through a store that records each write in place of making it. It prints each label, sub-task with its summary and labels, comment and rank move it would write, then each chunk that would start and why each other open issue waits, as `--status` words it.
|
||||
- It writes nothing to Jira, starts no window and asks no question; where planning would ask, it prints the question.
|
||||
- `do-epic --help` and README → Tools describe the flag.
|
||||
|
||||
Touches:
|
||||
|
||||
- `bin/do_epic/main.py`: `run`, `windows_opened`
|
||||
- `bin/do_epic/planning.py`: `planned` (small), `answered` (small)
|
||||
- `bin/do_epic/backend/fake.py`
|
||||
- `bin/do_epic/backend/protocol.py`: `EpicStore` (small)
|
||||
- `bin/do_epic/test_main.py`
|
||||
- `bin/do_epic/test_planning.py`
|
||||
- `README.md`: `## Tools` (small)
|
||||
|
||||
### 455. Let a chunk file a follow-up issue that its own issue blocks, with `do-epic --file --blocked-by` and `--parent`, so a change a repo ships as two pull requests gets an issue for each.
|
||||
|
||||
One epic issue is one chunk and one pull request. Some repos ship a change as two pull requests in two releases, as Timewave's legacy repos do: first a pull request that pins and isolates today's behaviour, then the one that changes it, each with its own ticket and the first blocking the second. A chunk in such a repo can't file the second issue so that it waits for the first, so the human must split those issues by hand before the run.
|
||||
|
||||
- `do-epic <EPIC-KEY> --file` takes `--blocked-by <KEY>`, which links the new issue as blocked by that issue of the epic, so a chunk files its second step and finishes its own.
|
||||
- `--file` also files a sub-task, with `--parent <KEY>`, where the chunk's issue is a sub-task of a split item, so the second step stays under the same item.
|
||||
- The chunk's instructions say when to use it: where the repo's rules ask for a change to ship as more than one pull request.
|
||||
|
||||
Touches:
|
||||
|
||||
- `bin/do_epic/findings.py`: `parsed`, `written`, `instructions`, `USAGE`, `HELP`
|
||||
- `bin/do_epic/backend/protocol.py`: `EpicStore` (small)
|
||||
- `bin/do_epic/backend/jira.py`: `JiraEpic.file`
|
||||
- `bin/do_epic/backend/fake.py`: `MemoryEpic.file` (small)
|
||||
- `bin/do_epic/test_findings.py`
|
||||
- `README.md`: `## Tools` (small)
|
||||
|
||||
### 451. Add a project setting `merge = "human"`, under which a chunk leaves its pull request ready for a person to merge, and a do-epic chunk parks until the pull request is merged.
|
||||
|
||||
Every chunk merges its own pull request with `chunk-pr merge`. Some teams forbid that: Timewave's conventions say never to merge a pull request without the human's explicit go-ahead for that pull request. The loop can't run in such a team's repos without breaking the rule, and `wait-for-approval` doesn't cover it, since a reviewer's approval is not the go-ahead to merge.
|
||||
|
||||
- A project setting `merge` takes `chunk`, the default and today's behaviour, or `human`.
|
||||
- Under `human`, `chunk-pr merge` levels the branch and marks the pull request ready, then leaves the merge to a person and exits saying the pull request awaits a person's merge.
|
||||
- A do-epic chunk then parks on a new gate, `your merge`, shown in its window's name and in `--status` like any gate. It takes no slot, finishes once the forge reports the pull request merged, and still resumes when a reviewer comments.
|
||||
- A loop-claude chunk ends with the pull request ready. The chunk settles how the item's `--finish` runs after a person merges it.
|
||||
- `parked_through` in `bin/do_epic/main.py` is the place the comprehension seats found hardest to follow; leave it easier to read than it was.
|
||||
|
||||
Touches:
|
||||
|
||||
- `bin/project_config/settings.py`: `SCALARS` (small)
|
||||
- `bin/chunk_pr/main.py`: `merged`, `merge_turn`
|
||||
- `bin/chunk_pr/approval.py`: `awaited` (small)
|
||||
- `bin/do_epic/gates.py`: `gate`, `Gate`
|
||||
- `bin/do_epic/main.py`: `parked_through`
|
||||
- `bin/do_epic/chunk_prompt.py`: `shipping`
|
||||
- `bin/do_epic/test_gates.py`
|
||||
- `bin/do_epic/test_main.py`
|
||||
- `README.md`: `### Set up a project` (small), `## Tools` (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.
|
||||
|
||||
- Settings in do-epic's config.toml name a transition to make when a chunk starts, such as `jira-start-transition = "In Progress"`, and a board whose active sprint the issue joins, such as `jira-board = 6`. Without them, nothing moves, as today.
|
||||
- A starting chunk assigns its issue to the account whose credentials do-epic uses, unless someone else holds it, which it leaves alone and says so. A sub-task's parent joins the sprint in its place, since Jira keeps a sub-task in its parent's sprint.
|
||||
- An issue already past the start transition, such as one in Code Review, keeps its status.
|
||||
|
||||
Touches:
|
||||
|
||||
- `bin/do_epic/config.py`: `DoEpicConfig`, `load` (small)
|
||||
- `bin/do_epic/backend/protocol.py`: `EpicStore`
|
||||
- `bin/do_epic/backend/jira.py`: `JiraEpic`
|
||||
- `bin/do_epic/backend/fake.py`
|
||||
- `bin/do_epic/backend/contract.py`: `EpicStoreContract`
|
||||
- `bin/do_epic/main.py`: `chunk_run`
|
||||
- `bin/do_epic/backend/test_jira.py`
|
||||
- `README.md`: `### Set up a project` (small)
|
||||
|
||||
### 446. 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.
|
||||
|
||||
Item 422 judges a worker that stalls before its result, but only reports: each verdict goes to the terminal and to `stuck-workers.md` in the project's transcript archive. Question for the human: after a few days of verdicts there, do they match what you would have done? Once you say yes, kill only the process a `stuck` verdict names, and only where the pid is below the worker's claude, never the worker or the loop, and record the call in a decision.
|
||||
|
||||
Reference in New Issue
Block a user