A Jira backlog shows you one thing: where everything stands right now. What it can't show you is how it got there — which areas caught fire this quarter, where work piled up and sat, which corner quietly went green while you weren't looking.
Teppe already turns a sprawling backlog into a single picture you can take in at a glance. Time-lapse adds the missing dimension: time. Press play, and that picture comes to life — every issue moving through To Do → In Progress → Done, exactly as it really happened.
Watch a year of work in a few seconds
Here's the full Apache Spark project — roughly 5,000 issues — replayed across a year of real history:
The whole project, one year, played back from Jira's own status history.
Each tile is a piece of work; each block of tiles is an area. The colour is the issue's status category, so the whole carpet breathes as the project moves: grey work turns blue as it's picked up, blue turns green as it ships. Watch it once and you can see the rhythm of the project — the steady areas, the late-quarter surges, the parts that stalled.
Nothing here is simulated. Time-lapse is reconstructed from the real status-change history already recorded against your issues — the same timeline you'd piece together by hand from each issue's activity log, except across the entire backlog at once.
Drill into a single area of work
The whole project is the headline, but the story usually lives in one corner of it. Time-lapse is scoped to whatever node you're looking at — so you can drill into one area and replay just that.
Here's the Connect area of Spark on its own:
One area of work, same window — the detail you'd lose in the project-wide view.
This is the view for a retro or a team update: "here's how Connect actually went this quarter," shown rather than asserted.
Pick the window that tells your story
When you open Time-lapse, you choose the window first — before anything is built — so you never have to guess and re-run:
By sprint — pick one sprint or a run of them, and the playback spans exactly that work.
By date — any start and end date, for teams that don't run sprints or want a custom range.
Then it's a simple transport: play / pause, a scrubber to jump to any moment, and a speed control to slow down a busy stretch or skim a quiet one.
Share it, don't describe it
A time-lapse is worth more in a standup than in your own head. Every playback can be exported — as an animated SVG that stays crisp at any size and drops straight into a doc or a stakeholder update, or as a GIF to paste into Slack or a retro board. The colours are baked in at export, so it looks right in light or dark, wherever it lands.
Honest by design
Time-lapse keeps the same promises the rest of Teppe makes:
It never touches Jira. Teppe reads your project; it never creates, edits, or moves a single issue. Time-lapse is a replay of history, not a change to it.
Your data never leaves Atlassian. Teppe runs entirely on the Atlassian platform — no external services, no data egress. The history is read, rendered, and animated in place.
It respects reduced motion. If your system asks for reduced motion, playback starts paused and every frame is legible on its own, so you're never forced into animation you didn't ask for.
Try it
Open any project in Teppe for Jira, click Time-lapse, pick a sprint or a date range, and press play. Start with the whole project, then drill into the one area you actually want to talk about — and export the clip that makes the point for you.
Top comments (0)