Timeline credits the mover, at the time of the action

The idea

Crewshal Timeline credits a ticket move only to the person that the board's history names as the mover, never to the person who holds the ticket. A late or repeated GitHub, Jira, Slack or Notion webhook takes the time of its action, not the time it arrived, up to three days back.

The problem
Holders got credit for moves they did not make, and late webhooks landed at the wrong time.
Why it matters
Each person's feed shows only their own actions, in true order.
Where it stands
In production as of One production check with an operator test account and scripted webhook deliveries and board reports; no outside team has used it yet.

Crewshal team · · 4 min read

Recorded run · Production, operator test account · November 14, 2026

Who did it, and when?

Late webhook deliveries take the time of their actions, and a ticket move goes to the mover the board names, never to the holder.

Step 1 of 5When

GitHub-style webhookThree deliveries arrive out of order

A test account starts a Timeline-only organization with a webhook-only GitHub connection: no token, so the platform never calls GitHub. The check sends three signed deliveries about one pull request, in this order: a review approved 1 hour earlier (dana-q), the opening of the pull request 3 hours earlier (carol-q), and the dismissal of that review (erin-q), which carries no time of its own. All 3 are accepted.

InputDeliveries, in arrival order

  • 1. dana-q approved the review (action 1 hour earlier)
  • 2. carol-q opened pull request 7 (action 3 hours earlier)
  • 3. erin-q dismissed the review (no time of its own)

CheckRecorded checks

  • Timeline-only organizationPassed
  • All 3 deliveries accepted, 1 event eachPassed

Where it ran. A check in production at crewshal.com on November 14, 2026 at 02:12:18 UTC (the evening of the 13th in US Central), with an operator test account in a Timeline-only organization. The check sent signed webhook deliveries through a webhook-only connection with its own secret, and board reports through the public work-state API; no real repository or board sent them.

The recorded files behind this replay
  • Production check: who and when, 12 checks sha256 ce6a3c0f978d
  • The check script (the deliveries and board reports it sent) sha256 dfbab8953d5b
  • Release note: who did it and when sha256 5a2887b748ca
  • The new tests on the old code, then with the change sha256 80db49953c17
  • Production capture: the feed after the check sha256 00add7f0bae5

Why it matters

Timeline is an automatic feed of what each person, outside agent, AI worker or automation did across connected systems. Nobody reports into it, and it needs no AI worker.

Two common errors make a feed tell a wrong story. Webhooks arrive late, twice or out of order, so a feed in arrival order shows a three-hour-old action as new. And many boards show only who holds a ticket, so a feed that credits the holder puts other people's moves in that person's history. A manager who reads such a feed sees the wrong person at the wrong time.

How it works

  1. The action's own time. GitHub, Jira, Slack and Notion webhook events carry the time of their action. A late or repeated delivery takes that place in the feed, kept within the three days before it arrived. An event with no time of its own takes its arrival time.
  2. The audit log keeps the arrival. The audit log keeps the time each delivery arrived, in its hash chain. Only the feed's order changes.
  3. Only the named mover. A board report credits a status move only to the mover that the board's history names, at the history's time. Holding a ticket is not evidence of moving it.
  4. Otherwise, the board. Without a named mover, the move is the board's entry, and it says that the board did not name the mover. The holder's own feed does not show it.
  5. No skipped entries. The feed merges several streams of records. A page stops where a full stream stopped, so a busy feed does not skip entries while it reports that it is complete.

What the run showed

The replay above is a recorded check in production on November 14, 2026, at 02:12 UTC (the evening of November 13 in US Central), with an operator test account in a Timeline-only organization. The check sent signed webhook deliveries through a webhook-only connection with its own secret, and board reports through the public work-state API.

  • Three deliveries about one pull request arrived in this order: a review approved 1 hour earlier, the opening of the pull request 3 hours earlier, and the dismissal of that review, with no time of its own.
  • The feed listed them by the time of each action: the dismissal at its arrival, then the review, then the opening at 23:12 UTC, 3 hours before it arrived. A read of the hour around the opening found only the opening.
  • A board report showed tickets QA-1 and QA-2 in progress, both assigned to Nia. A second report moved QA-1 to Testing with no mover named, and QA-2 to Done with Sol named as the mover, 2 hours earlier.
  • QA-1's move went to the tracker board, which said that it did not name the mover. QA-2's move went to Sol Q at 00:12 UTC, the history's time. Nia's own feed showed neither move. All 12 checks passed.
  • Before the release, 19 of 34 new automated test cases failed on the old code: a busy feed lost entries, entries came in arrival order, a late delivery was missing from its time range, and a move went to the holder.

Limits

  • Test inputs. The check sent the deliveries and the board reports itself. No real repository or board sent them, and an outside team has not used it yet.
  • GitHub deliveries in this run. Jira, Slack and Notion webhooks follow the same time rule; this run did not send them.
  • Other webhooks. GitLab, Linear, Confluence and Teams deliveries keep the time they arrived.
  • The Jira collector names no mover. Its Jira tool gives no status history, so every move it reports stays the board's entry.
  • Three days. An action time more than three days before the delivery arrived is placed three days back.
  • A board without history. When a board names no mover, Timeline cannot know who moved the ticket, so the move stays the board's entry.

Frequently asked questions

Why not use the time a webhook arrives?

A webhook can arrive late, twice or out of order, and a reader expects the time of the action. GitHub, Jira, Slack and Notion deliveries carry that time. The audit log still keeps the time of arrival.

Who gets the credit when the board does not say who moved a ticket?

Nobody: the move shows as the board's entry and says that the board did not name the mover. It never goes to the person who holds the ticket.

Does a late delivery change the audit log?

No. The audit log keeps the time the delivery arrived, in its hash chain. Only the feed places the entry at the time of the action.

  • One event shows once

    When a webhook and collectors record the same GitHub change, the feed shows it once with a count of sources, while every record stays in the audit log.

    Recorded walkthrough

  • Current state of outside boards

    Collectors report the current status of items on outside boards; a status change becomes one entry and feeds Today and Blockers in formats.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.