Answer product-owner round 1: 0 🔴, 1 🟡 (0 misread); say in the help and the dry run that a starting chunk starts its issue in Jira
This commit is contained in:
+7
-7
@@ -53,7 +53,7 @@ An issue under which a person filed a sub-task is not planned: its sub-tasks run
|
||||
Where the rule leaves the label unclear, it asks you on the terminal. Answer with the label, or with Enter alone to leave the issue waiting.
|
||||
Where two or more issues may start, it then scores each of them that holds no scores, and tells the issue's team the scores in a comment on the issue. It scores by the `Score = ...` line under the epic's ## Scoring, and moves the issues do-epic itself filed into that order on the board.
|
||||
An open issue labelled `repo:<name>` or `do-epic-claude` runs as a chunk once no issue blocks it.
|
||||
The issues start in order of score, highest first, whatever their order on the board. An issue it could not score starts after the others.
|
||||
The issues start in order of score, highest first, whatever their order on the board. An issue it could not score starts after the others. As its chunk starts, an issue is assigned in Jira to the account do-epic works as, unless someone else holds it. Where config.toml names a start transition or a sprint board, the issue is also moved by that transition and joins that board's active sprint.
|
||||
A `do-epic-human` issue that blocks another gets a window too. The window DMs you once, then waits without taking a place until you close the issue in Jira.
|
||||
As many run at once as the epic's description allows with a line such as `**Max parallel chunks:** 2`, one where it has none.
|
||||
A repo takes as many chunks as its `parallel-chunks`, and none while loop-claude runs chunks in it.
|
||||
@@ -63,7 +63,7 @@ on once the checks pass, the approval comes or a reviewer comments, and a place
|
||||
name says `awaits a slot`. In a repo whose config sets `merge = "human"`, a chunk never merges: once its pull
|
||||
request is ready, with nothing else to wait on, the window's name says `awaits your merge`, and its worker goes on once you merged it. A parked chunk survives a reboot: run do-epic <EPIC-KEY> again to go on polling.
|
||||
--status doesn't start any chunk. It prints a line per open issue: that its chunk runs or asks you a question, or why it waits, such as the gate a parked chunk awaits and since when.
|
||||
--dry-run runs the planning and the scheduling against the epic as Jira holds it. It doesn't write anything to Jira, start a window or ask a question. It prints each label, sub-task, comment, score and rank move that planning would write, the order the issues would start in, each chunk that would start and why each other issue waits. A sub-task not yet filed shows a key such as ABC-new1. A question planning would ask is printed instead of asked. Planning's claude calls still run.
|
||||
--dry-run runs the planning and the scheduling against the epic as Jira holds it. It doesn't write anything to Jira, start a window or ask a question, and it doesn't start any issue in Jira as a real run's chunk does. It prints each label, sub-task, comment, score and rank move that planning would write, the order the issues would start in, each chunk that would start and why each other issue waits. A sub-task not yet filed shows a key such as ABC-new1. A question planning would ask is printed instead of asked. Planning's claude calls still run.
|
||||
A repo that is missing isn't cloned. Planning then stops there, so its writes are only those made before it, and the issues of that repo wait, and a chunk of another repo may start in the place a real run gives them; a real run would clone it and go on.
|
||||
{findings.HELP}
|
||||
{finish.HELP}
|
||||
@@ -215,7 +215,7 @@ def dry_run_printed(epic: EpicRun) -> Stop:
|
||||
return Stop(1, dry.reason)
|
||||
effects = dataclasses.replace(epic.effects, tmux=dry_run.recording(epic.effects.tmux), git=dry_run.without_clones(epic.effects.git), on_terminal=lambda: False)
|
||||
rehearsal = dataclasses.replace(epic, store=dry, effects=effects)
|
||||
say("dry run: nothing is written to Jira and no window starts, so a line below that says an issue is labelled, split or scored shows what a real run would do", effects, stdout=True)
|
||||
say("dry run: nothing is written to Jira and no window starts, so a line below that says an issue is labelled, split or scored shows what a real run would do. A real run would also start in Jira the issue of each chunk it starts: assign it and, where config.toml says so, move it and add it to a sprint", effects, stdout=True)
|
||||
started = planned_and_started(rehearsal, dry=True)
|
||||
writes = "".join("\n- " + write.replace("\n", "\n ") for write in dry.writes)
|
||||
say(f"planning would write to Jira:{writes}" if dry.writes else "planning wouldn't write anything to Jira", effects, stdout=True)
|
||||
@@ -305,10 +305,10 @@ def chunk_run(key: str, epic: EpicRun) -> Stop:
|
||||
if isinstance(place, Stop):
|
||||
return place
|
||||
root, repo = place
|
||||
if issue:
|
||||
issue_started(key, epic)
|
||||
if unmade := folder_made(root):
|
||||
return Stop(1, unmade.reason)
|
||||
if issue:
|
||||
issue_started(key, epic)
|
||||
session = session_named(f"A {epic.key} do-epic {key}", epic.paths.claude_code_transcripts)
|
||||
loop = Loop(root=root, session=session, window=tmux.Window(epic.session, key, pane), paths=epic.paths, env=epic.env, launcher=epic.launcher, effects=epic.effects)
|
||||
run = ChunkRun()
|
||||
@@ -341,9 +341,9 @@ def issue_started(key: str, epic: EpicRun) -> None:
|
||||
"""Starts the issue called key in the tracker, and says who else holds it, or why it didn't start. The chunk runs either way: the tracker shows the team the work, and the work doesn't read it."""
|
||||
other = epic.store.start_issue(key)
|
||||
if isinstance(other, Failure):
|
||||
say(f"{key} doesn't show in the tracker as started, and its chunk runs all the same: {other.reason}", epic.effects, stdout=True)
|
||||
say(f"not every step that starts {key} in the tracker was made, and its chunk runs all the same: {other.reason}", epic.effects, stdout=True)
|
||||
elif other:
|
||||
say(f"{key} stays assigned to {other}, who holds it", epic.effects, stdout=True)
|
||||
say(f"{key} stays assigned to {other}", epic.effects, stdout=True)
|
||||
|
||||
|
||||
def parked_through(repo: str, loop: Loop, epic: EpicRun, told: str | None, finished: bool) -> str | Stop:
|
||||
|
||||
@@ -389,7 +389,7 @@ class AChunksRun(DoEpicTest):
|
||||
|
||||
def test_a_starting_chunk_says_who_else_holds_its_issue_and_leaves_it_theirs(self) -> None:
|
||||
store = MemoryEpic("ABC-12", [self.issues[0], dataclasses.replace(self.issues[1], assignee="Ada Berg")])
|
||||
self.assertIn("ABC-21 stays assigned to Ada Berg, who holds it\n", self.started(store).partition("=== cycle 1")[0])
|
||||
self.assertIn("ABC-21 stays assigned to Ada Berg\n", self.started(store).partition("=== cycle 1")[0])
|
||||
self.assertEqual(store.issues[1].assignee, "Ada Berg")
|
||||
|
||||
def test_a_chunk_runs_though_its_issue_could_not_start_in_the_tracker_and_says_why(self) -> None:
|
||||
@@ -397,7 +397,7 @@ class AChunksRun(DoEpicTest):
|
||||
def start_issue(self, key: str) -> str | None | Failure:
|
||||
return Failure(f"cannot assign {key}: Jira answered 403")
|
||||
out = self.started(Unstartable("ABC-12", list(self.issues)))
|
||||
self.assertIn("ABC-21 doesn't show in the tracker as started, and its chunk runs all the same: cannot assign ABC-21: Jira answered 403\n", out.partition("=== cycle 1")[0])
|
||||
self.assertIn("not every step that starts ABC-21 in the tracker was made, and its chunk runs all the same: cannot assign ABC-21: Jira answered 403\n", out.partition("=== cycle 1")[0])
|
||||
self.assertIn("the chunk finished", out)
|
||||
|
||||
def test_runs_cycles_until_the_judge_rules_it_finished_then_starts_the_next_chunk(self) -> None:
|
||||
@@ -1027,7 +1027,7 @@ class TheStatus(DoEpicTest):
|
||||
self.assertIn("Jira answered 503\n", err)
|
||||
|
||||
|
||||
BANNER = "dry run: nothing is written to Jira and no window starts, so a line below that says an issue is labelled, split or scored shows what a real run would do"
|
||||
BANNER = "dry run: nothing is written to Jira and no window starts, so a line below that says an issue is labelled, split or scored shows what a real run would do. A real run would also start in Jira the issue of each chunk it starts: assign it and, where config.toml says so, move it and add it to a sprint"
|
||||
|
||||
|
||||
class TheDryRun(DoEpicTest):
|
||||
|
||||
Reference in New Issue
Block a user