This commit was merged in pull request #657.
This commit is contained in:
@@ -2,6 +2,7 @@
|
||||
|
||||
## Unreleased
|
||||
|
||||
- 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.
|
||||
- The stability reviewer checks each parser that splits text on a separator or strips a suffix against a value that holds the separator, and reports a row the parse misplaces or drops.
|
||||
|
||||
|
||||
@@ -12,10 +12,9 @@
|
||||
|
||||
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|
||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||
| 449 | 0.15.0 | | | **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.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 |
|
||||
| 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 | 449, 453, 454 | question | **Cut 0.15.0 as soon as items 449, 450, 453 and 454 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 | 453, 454 | question | **Cut 0.15.0 as soon as items 449, 450, 453 and 454 have merged, before its release review, and run that review in 0.15.1.** | 1 | 1 | 1 | 1 | 1 | | 0.0 |
|
||||
| 468 | 0.15.0 | | | **Tell a do-epic worker the team's own label for each repo when it files a finding or a release-review issue, so those issues carry the label the team's board uses.** | 2 | 2 | 2 | 4 | 2 | 1.6 by 4 | 1.4 |
|
||||
| 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 |
|
||||
@@ -76,24 +75,6 @@
|
||||
|
||||
## Details
|
||||
|
||||
### 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.
|
||||
|
||||
Reference in New Issue
Block a user