Ticket comments

The real scope of a ticket often lives in its comments: “we agreed to drop the export”, “the ledger setting is switched on in production now”. Limn reads the comments of every ticket it reads, shows them in the story view, and gives them to the story check as the team’s discussion of the ticket.

#What you see

• Comments (n), open, at the end of the Ticket section of the story view. That is the ticket tab, a pull request’s Ticket tab and the panel on This Sprint. It works on every tracker, and for a ticket with no pull request.
• The newest three comments, oldest first, with the author and the date. Show all opens the rest.
• New since the check on a comment written after the latest story check.
• Comments by bots and tracker automations are left out.

#How the story check uses them

• Before every story check, Limn reads the ticket’s comments from the tracker again, so the check sees the latest ones. It does not re-read the rest of the ticket at that moment.
• The check is told that comments are discussion, not the ticket. A comment can clarify or change the scope when it says so plainly, a later comment outweighs an earlier one, and a comment alone is never a new requirement.
• When a verdict relies on a comment, the check names its author and date.
• Only people’s comments are given to the check, at most about 6,000 characters of the newest.

#Met outside code changes

Some criteria are not code: a setting, some content, a manual step, a decision. When no pull request delivers a criterion, none needs to, and a person’s comment says plainly that it was done, the check marks it Met outside code changes.

1. Select the citation, “Per Dana Wu’s comment, 4 Mar”.
2. The Comments section opens in full and moves to that comment, so you can read it.

It counts as done, is never posted as a gap and is never given to Fill gaps. Counts name it apart, for example “4 met + 1 outside code of 6”. Limn keeps the verdict only when the comment it cites is a real comment by a person on the ticket, and the check did not say the work belongs in code.

#When a new comment arrives

A new comment by a person makes the latest check out of date only while the check has a criterion that is not done, because the comment may settle it. If every criterion is done, the comment is marked New since the check and nothing else changes. With automatic checks on, the new comment starts the two-minute wait like a push does, and the line says “waiting 2 quiet minutes after the last comment on the ticket”.