Where JiraVision is going — without pretending we can promise dates
A now / next / later view of what is being built, what is queued and what we are only thinking about. Updated by hand whenever the work changes — never quietly.
- Three columns, one rule: “Done” only comes from the public changelog.
- Commitment levels, not calendars — no dates are promised anywhere on this page.
- Items can move backwards, and we say so when they do.
How this roadmap works
How to read this roadmap
Each column answers one question: how hard are we working on this right now? That is a statement about today, not a forecast. Nothing here is a contract — the only facts on this page are the changelog entries in the Done band.
- Now
- Actively being built in the current phase of this project. Code is being written and reviewed now. Still no date — being in progress is not a delivery promise.
- Next
- Committed direction, uncommitted shape. Sequenced after the Now work, worth planning around, but the design may change and no date exists yet.
- Later
- Exploratory — not a commitment. Things we genuinely consider and have not started. They may never ship, and that is a legitimate outcome.
- Done
- Only ever filled from the dated changelog. If you cannot find it on /changelog, it is not done and will not appear in that band.
Ground rules
Three rules this page sticks to
Roadmaps are usually the most dishonest page on a vendor site. These rules exist to keep ours from becoming that.
No dates. On purpose.
A small team with external dependencies (Jira's APIs, our hosting, the owner's day job) that publishes public dates eventually sells broken promises. Columns describe effort, not calendars.
Done lives elsewhere.
The Done band on this page is generated from the changelog, not hand-written. Work gets a dated entry there first; only then does it appear here as shipped.
Movement is visible.
Items get added, promoted, parked and occasionally dropped. If something that lived in Now or Next disappears, we mark the removal with a reason instead of silently editing.
Housekeeping
How this page gets updated
Every release ends with a pass over this page. Four checks, in order:
- Step 1
Review
After each release, the owner checks each item against what actually changed in the code — not against optimism in a planning doc.
- Step 2
Move
Items change columns only when the underlying work changes state. Nothing is promoted for optics and nothing is parked because it got inconvenient.
- Step 3
Ship, then announce
Shipping earns a changelog entry. The Done band is rebuilt from that changelog, so it can only ever contain verifiable facts.
- Step 4
Note removals
If an item leaves the board, its last column and the reason get mentioned here before the entry is archived.
Now — being built in this phase
What we are working on right now
Active work in the current phase of this project. In progress is a description of today, not a delivery promise — the changelog is where progress becomes fact.
- Step 1
Roadmap & status, rebuilt
The two transparency pages you are using — this board and the upgraded /status manifest — are the work in progress. They ship together, and this sentence is the honest way to describe a roadmap item while it is still happening.
- Step 2
Comparison pages (/compare)
Factual, dated comparisons against the tools teams usually leave behind. Every claim cites a source or is flagged as our own measurement — no invented feature matrices.
- Step 3
Migration hub
Guided, step-by-step checklists for moving off spreadsheets or another tracker. Checklists save locally in your browser as you work through them.
- Step 4
Template library page
The working-set templates already shown in the homepage carousel grow into a proper filterable page with previews for each template.
- Step 5
Printable one-pagers
A one-page summary per product, for teams where the decision needs a document the person who signs the invoice can actually read.
- Step 6
Tests & QA pass
Smoke tests across the marketing flows, unit tests for the sandbox, gamification and calculator logic that already shipped, plus the final performance and SEO cleanup.
Next — committed direction, uncommitted shape
Queued behind the current work, without dates
These are sequenced and worth planning around, but the design may change. Nothing here is a contract; ask us on /contact what we would tell you today.
Automated health checks for /status
Today /status is a hand-maintained manifest. The next step is measured checks per component so the page can report observed reality. Until then it will keep saying it is manual — that caveat is part of the product.
GitHub integration
PR and review-load signals as a second data source behind the board views. Jira stays the anchor; GitHub has been the first name on our planned-integrations list since we published it.
Roadmap feedback loop
A way to attach your request or use case directly to an item here, routed through the same validated intake as the contact form. Until it exists, /contact is the door — and every message is read.
Translation beyond the chrome
Swahili and French are live for navigation and footer strings; body copy is not. Translating the marketing content section by section is queued, not dated.
Later — exploratory, not a commitment
Things we are genuinely considering
The honest bottom of the funnel: real candidates we have thought about and not started. Some will ship, some will quietly die, and none of them entitle anyone to anything.
- GitLab integration
- Merge and pipeline signals alongside Jira data. Listed as planned in our integrations table; nothing has been started.
- Slack surfaces
- Digests and check-ins delivered in the channel where the work already happens, instead of a dashboard you have to remember to open.
- Microsoft Teams notifications
- The same notification idea for the other chat platform enterprise buyers keep asking about. Design not started.
- Meeting-load context from calendars
- Using Google Calendar meeting load as context for workload signals, so after-hours charts are not blamed for what was actually a meeting-heavy week.
- Hosted data layer
- Our form and newsletter storage uses a swappable JSON-file adapter with a hosted-database interface already sketched. Moving it to a real database is a when-it-hurts decision, not a roadmap one.
Shipped
Done means shipped — every item below is in the changelog
2026-10-23
Feature
AI sprint reports
Capacity-aware sprint drafts now ship with a written rationale per suggested item, so planning decisions can be reviewed and edited before approval.
2026-09-30
Improvement
Wellbeing signals move to team-level aggregation
Check-in and workload indicators are now aggregated before display by default. Individual responses are never surfaced raw.
2026-08-28
Feature
Ethical metrics methodology view
Every fairness and workload metric now links to the exact formula and data window behind it.
2026-07-15
Improvement
Skill trees recognise review and mentoring work
Gamification paths now include code review, pairing and knowledge-sharing activities, opt-in per team.
2026-06-10
Feature
JiraVision goes public
Initial launch: AI Scrum Master, Team Wellbeing, Gamification and Ethical Metrics for teams connecting Jira workspaces.
Straight talk
What will never reach this roadmap — ever
Works well if
- You judge a roadmap by what the vendor refuses to promise, not by how long the list is
- You want team data to stay aggregate-by-default — that stance has never wavered and will not
- You would rather we ship ten features you can audit than forty that need surveillance to work
Not for teams that
- Per-person activity scores, keyboard time or lines of code — our published refusal list applies to the roadmap too
- Individual velocity leaderboards — they will not ship in any configuration, on any plan
- Dated public commitments — we will not trade honesty for a roadmap that looks decisive in a sales call
Prioritisation
How priorities are actually made
Not a scoring framework designed to look rigorous. This is the real sequence a small team uses, in the order the filters fire:
- Step 1
Repeated, specific demand
The same problem from several unrelated teams outranks one very loud request. “Nice idea” feedback is thanked and set aside.
- Step 2
The ethics filter
If a feature requires anything from our refusal list — per-person activity scores, keyboard time, lines of code — it is dead here, permanently, no matter how much demand there is.
- Step 3
Does it make the core loop true?
Work that makes the Jira sync, the sprint drafts or the wellbeing signals more trustworthy outranks polish, always.
- Step 4
Can we maintain it?
A small team owns this forever. Anything that needs new infrastructure, a new vendor or dedicated operations has to prove it survives that question.
Inputs
Where the items on this page come from
Five sources, weighted. If something gets here from anywhere else, it does not belong here.
- Contact & demo requests
- Every submission through /contact is stored, read and themed. Requests are the loudest honest signal a pre-scale product has.
- Early-access conversations
- What broke, what disappointed and what got quietly worked around in real usage. These become Now and Next items more often than feature requests do.
- Our own dogfooding
- We run our boards through JiraVision. Items born from our own friction skip the debate about whether the problem is real.
- The refusal list
- We publish what we will not build (see below). Repeated requests against that list become an explanation task, not a backlog item.
- The changelog itself
- Follow-through we promised in earlier entries. A shipped feature that created a gap is due a closing item here.
This page is a conversation starter, not a suggestion box that eats mail
The strongest signal is not a vote — it is your specific story. What are you trying to do, what does it cost you today, and what would make you wrong for us? Write that to us and it lands in the same intake that built this page.
Receipts
Check the receipts
Changelog
The only source for anything claimed as Done. Dated entries describing real shipped work, newest first.
Status
How every component of the service is doing right now, maintained by hand and labelled as such.
Ethical Metrics
Where the refusal list lives as a product feature — the boundary this roadmap is built on.
The only roadmap that matters is what shipped
If this page convinced you of anything, go check it against the changelog. That comparison is the point of building it this way.