Skip to the page

See · History engine

Keep the history your systems forget. Charts your systems cannot draw.

Many systems only know how things are right now. nexibi keeps a dated copy of a list on the schedule you pick, and keeps every change from that day on, so a board can draw a sprint burndown, or open tickets by status, week by week. For systems with a web API.

Works with Assistant Dashboards History Connections

starts the day you turn it on

Tarnwick Supply Co.Boards · Delivery teamSample data
Open tickets by status · weekly, from a daily copy
To doIn progressIn review
0204060Wk 38Wk 39Wk 40Wk 4155Wk 42Wk 43Wk 4436Wk 45
3Starts the day you turn it on
Sprint 14 burndown · daily copy of Issues, 02:00
Story points leftEven pace
0204060Day 0Day 2Day 4Day 6Day 8Day 10today30 left
1A copy kept each night
Daily copy of Issues · every night at 02:00 your time · details kept 90 days
2Only changes are stored
  • 1A copy kept each night
  • 2Only changes are stored
  • 3Starts the day you turn it on

Your system knows today. It forgets yesterday.

Many project tools show only today's tasks. Ask what the sprint looked like last Tuesday, or how many tickets were open each week, and they have no answer: they keep how things are now, not how they were. The history engine keeps the days for you, from the day you start.

No code, no SQL, no scheduler to run and no database to set up: you pick the list and the schedule, or ask the assistant.

IssuesSample data
Issues · today42open
How did this look last Tuesday?
Issues · keptSample data
Issues · today42open
Tue 4 Nov51 open Tue 11 Nov42 open

Three ways to start a copy.

The Track history window

In four steps, from any web-system connection: pick the list; pick the field that identifies a record; pick what to chart, such as a daily count of records by status; pick how often to copy it and how long to keep the details. Then Start tracking. You can leave some records out of a count, such as rejected ones, or chart a field that shows only on each record's own detail page.

Keep a daily copySample data
PlanProjects → Issues per project
WhenDaily at 02:00, your company's time zone
KeepDetails 90 days
ChartCount by status; burndown per sprint
ApproveNot now
Nothing starts until you approve it

Ask the assistant

Say "keep a daily copy of our open tickets and chart them by status". It proposes the copy on a card: the lists, the schedule, the time and time zone, and how long to keep it, all editable. Nothing starts until you approve it. It takes the first snapshot and checks it before drawing a chart. Burndown, burn-up and velocity rows per sprint are set up this way.

Linked lists as one plan

Keep every project and each project's issues together, linked, up to 200 projects a run.

Your schedule, measured first.

  • How often. Every 15 minutes, every hour, daily or weekly in the window; any number of minutes, hours, days or weeks through the History page or the assistant. Never more often than every minute.
  • When. Daily or weekly at a time of day in your own time zone, following the clock change.
  • How long. Keep the detailed versions 30, 90 or 365 days. The daily counts and burndown rows stay after the details age out.
  • Measured before it starts. The window measures the list first: how many records it holds now, the page size the system really serves, and how many requests each copy costs. It warns you if the paging cannot be confirmed.
  • Checked before it is scheduled. Every setting is tried against your system first, so a wrong project number is refused now, not failed every night.
  • Told what to expect. A chart needs one column per copy, so twelve weekly columns take twelve weeks; the window says so.
Track history · IssuesStep 4 of 4Sample data
1List2Record3Chart4Schedule
Check for changesevery hour (recommended)
Keep history for90 days

History starts now. Tomorrow you will have your first snapshot.

BackStart tracking

What is kept.

  • A new version is saved only when a record changed. Unchanged records cost nothing.
  • What changed is kept field by field, with when: "status: Open → In progress → Done".
  • Records that disappear are marked with the time they went, not erased. One that comes back is counted again.
  • A copy taken every few minutes or hours charts a point per minute or per hour, not one a day.
  • A second run on the same day replaces that day's numbers. "Check now" never doubles a bar.

only changes are stored

ChangesOpen issuesSample data
Tue 11 Nov, 02:00 · 3 changed, 1 removed
ISS-418status: In progress → Done
ISS-425assignee: Sami → Dana
ISS-431priority: Normal → High
ISS-409removed · marked at 02:00, not erased
Query StudioEvery version · ISS-418Sample data
ISS-418Open 3 NovIn progress 6 NovDone 10 Nov
What changed, and when

It will not draw a wrong bar.

  • A run that cannot read the whole list stores nothing that day, rather than a short bar that looks right and is not: when the system is down, when paging never ends, or when the list passes 50,000 records.
  • With linked lists, a project it cannot reach means no bar that day, not a bar missing a project.
  • It warns when every record changed at once, which usually means a setting changed, not the work. It says when a field it counts has vanished, instead of charting it as "(none)".
  • It waits out rate limits and short outages. After downtime it makes one catch-up run, never a burst at your system.
  • A scheduled copy only reads. Anything that would change data is refused.
  • The History page says in plain words whether each copy still feeds its charts: Healthy, Waiting, Failing, Overdue, Paused, Disconnected, Capturing nothing or Check this, with the reason and the fix on the row.
  • Each company's kept history sits in its own history database.
HistoryYour copiesSample data
Open issuesHealthy43 days of history · next check in 38 min
Deal stagesCapturing nothingThe stage field is empty on every record: choose another field
Sprint issuesWaitingFirst snapshot tonight at 02:00
Projects → IssuesHealthyPlan · per project

Who sees it, and how it signs in.

  • What is kept appears as a "History" source. Whoever the connection is shared with sees it, and it stays inside a sealed department if the connection is in one.
  • It keeps a copy only of the lists you choose to track. The assistant sets one up only when you ask: after a plain question it answers, and may offer a copy in one line.
  • A series can move from a personal connection to a shared one without a break.
  • A system where each person signs in as themselves is copied with the copy owner's own sign-in, checked when the copy is made. If that sign-in lapses, the run fails with a clear reason.
  • A copy can sign in with nobody watching: none, an API key, a token, a username and password, a custom header, an Odoo-style sign-in, or OAuth 2 with a machine grant. A system that needs a person at a browser to sign in is refused, with the reason.

It works with the other engines.

Dashboards

Each copy brings ready-made queries: every version, as it stands, a daily rollup and a daily breakdown. The board designer shows them in a "History" group and says when each is taken. Stacked columns over time come out right: the date axis is pinned to the day, so counts are not added up.

Dashboards

Query Studio

See each record as it was on a date, or how one value moved.

The assistant

Set up copies by asking, and ask why a chart stopped growing.

AI Assistant

Analysis & prediction

New data from a copy runs the forecasts and predictions that read it again, and they say when a copy feeding them has gone stale.

Analysis & prediction

Data connections

"Track history" sits on each web-system connection, with a chip showing the next check.

Data connections

Who uses it.

ProductHow did open tickets move by status, week by week?

A daily copy lets a board draw how they moved, from the day the copy starts.

For product
OperationsHow many work orders were open each morning this month? For operations
CEO or ownerHow have our open deals moved between stages, week by week?

A weekly copy of your deals lets a board show how they moved, from the day the copy starts.

For CEOs and owners

What it does not do yet.

So you know before the demo.

  • Databases, files and mailboxes cannot be kept: web systems and ready-made connectors only.
  • It cannot fill in the past. History starts on the day you turn the copy on.
  • A copy stops at 50,000 records a run, and linked lists at 200 parents a run.
  • Burndown rows are set up by asking the assistant; the window offers counts by a field.
  • A board cannot yet show a copy as it stood on a past date; Query Studio can.
  • Nobody is e-mailed when a copy fails: the History page, the chip on the connection and the assistant say it.
  • The assistant cannot pause, change or delete a copy; the History page can.
  • Each person sees their own copies on the History page; an owner has no company-wide list yet.

Pick one list. Start keeping its history.

In the demo we connect one of your systems, and you ask the questions.