Zum Inhalt

The life of an issue

← All features

Questions of the assistant or the maintainer mark an issue needs-info; after 15 days the reporter gets a reminder that names the day the issue closes, and after 30 days it closes on that day. An answer, in a comment or by an edit of the issue, ends the waiting, and reopens an issue that closed for a missing one. A maintainer who reopens it by hand ends the waiting as well.

Labels say where an issue stands, and the lifecycle moves it on; each box has the colour of its label:

The life of an issue and its labels: A new issue gets needs-triage, the labels of its form and a first analysis, and the maintainer takes over. When information is missing, or the maintainer asks the reporter, it gets needs-info and waits for the reporter: on day 15 it gets stale and a reminder, and on day 30 it closes as not planned; an answer, also after the closing, brings it back to the maintainer. A sure duplicate gets possible-duplicate and a notice and closes as a duplicate on day 3, unless an objection, a comment or a thumbs down of the reporter or of someone who may push, brings it back to the maintainer. A merged fix gives it fixed-in-next-release, and the release closes it with a link; a comment within 30 days that it is still broken brings it back to the maintainer.The life of an issue and its labels: A new issue gets needs-triage, the labels of its form and a first analysis, and the maintainer takes over. When information is missing, or the maintainer asks the reporter, it gets needs-info and waits for the reporter: on day 15 it gets stale and a reminder, and on day 30 it closes as not planned; an answer, also after the closing, brings it back to the maintainer. A sure duplicate gets possible-duplicate and a notice and closes as a duplicate on day 3, unless an objection, a comment or a thumbs down of the reporter or of someone who may push, brings it back to the maintainer. A merged fix gives it fixed-in-next-release, and the release closes it with a link; a comment within 30 days that it is still broken brings it back to the maintainer.

An issue that waits for its reporter keeps what the comments of the assistant promise:

  • An answer is a comment or an edit of the text, as the questions offer. Either ends the waiting, also when the event job missed it, since the sweep reads the comments and the history of the text. A new title alone answers nothing, and the AI gets no follow-up to write for it.
  • The reminder names the day, and the issue closes on it. The waiting counts days of the calendar in UTC, and the hidden marker of the reminder records the day, so the sweep of that morning closes the issue, whatever minute it starts.
  • A comment of the reporter, or an edit of the text, reopens the issue that the sweep closed for a missing answer, as the closing comment promises, whatever its labels say: also when an answer came in while the sweep closed it and took them. A new title, or a click on the box of the form alone, reopens nothing, and neither does an edit once the sweep has locked the issue. After a release or the closing as a duplicate, only a comment counts, as their comments ask for one.
  • A comment of the reporter on an issue closed as a duplicate goes to the maintainers, as the closing comment promises: the issue gets needs-triage and stays closed, since whether it is a duplicate is theirs to decide. The digest lists it under Waiting on the maintainers, and the sweep doesn't lock it, until a maintainer answers in a comment; reopen it, close it for another reason, or take away needs-triage, and it leaves the list and may be locked again. So does a comment of the reporter after the release of a muted issue, which no AI reads, also after the 30 days: the comment of that release asks for it.
  • A reopening by hand ends the waiting. When a maintainer, or anyone else who may, reopens an issue that the sweep closed for a missing answer, the next sweep takes away needs-info and stale, adds needs-triage and leaves the issue open, instead of closing it again. A new question, or /assistant waiting, starts a new waiting from then on.
  • A follow-up waits for no maintainer. The AI writes for a minute or two; the job that posts its follow-up checks again, and posts nothing once a maintainer joined the conversation.