This commit was merged in pull request #660.
This commit is contained in:
@@ -2,6 +2,7 @@
|
||||
|
||||
## Unreleased
|
||||
|
||||
- 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}`.
|
||||
- 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.
|
||||
|
||||
@@ -13,10 +13,9 @@
|
||||
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|
||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||
| 469 | 0.15.0 | | | **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 |
|
||||
| 453 | 0.15.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 |
|
||||
| 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 |
|
||||
| 467 | 0.15.0 | 453, 454, 469, 470 | question | **Cut 0.15.0 as soon as items 449, 450, 453, 454, 468, 469 and 470 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, 469, 470 | question | **Cut 0.15.0 as soon as items 449, 450, 453, 454, 468, 469 and 470 have merged, before its release review, and run that review in 0.15.1.** | 1 | 1 | 1 | 1 | 1 | | 0.0 |
|
||||
| 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 |
|
||||
| 462 | 0.16.0 | | | **Run under `mutate-changes` the tests that today fail in mutmut's copy of the tree, so a mutant of a line only they cover is killed.** | 2 | 1 | 2 | 3 | 3 | code health by 3 | 4.7 |
|
||||
| 77 | 0.16.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 |
|
||||
@@ -106,24 +105,6 @@ Touches:
|
||||
- `bin/do_epic/backend/test_jira.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)
|
||||
|
||||
### 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.
|
||||
|
||||
Reference in New Issue
Block a user