Skip to content
JiraVision
Status
Core systems normal; email delivery degraded

How every part of JiraVision is actually doing

A plain-language manifest for each component of the service, maintained by hand and labelled as such. No uptime theatre, no invented incident history.

  • Every component listed — including the one that is currently degraded.
  • “Operational” means a person verified it recently, not a measured guarantee.
  • Spotted something? /contact is how problems surface today, and it works.

Current posture

  • Marketing websiteoperational
  • Auth & dashboardoperational
  • Contact & forms APIoperational
  • Email deliverydegraded
  • Jira syncoperational

Last reviewed — by a human, not a probe.

The manifest

Component states, right now

Every part of the service and its current state. These rows are verified during manual review passes; the caveat on automated checks sits directly below the table.

Current status of each JiraVision service component
ComponentStatusNotes
Marketing websiteoperationalThis site and its public pages. If you can read this row, the check passed.
Auth & dashboardoperationalLogin, signup and the analytics dashboard. Verified by manual sign-in during each release review.
Contact & forms APIoperationalContact, demo, quote, careers and newsletter submissions are validated, rate-limited and stored.
Email deliverydegradedOutbound team notifications depend on a Resend key the owner configures. A valid key is not confirmed in this environment yet, so submissions are stored but the notification email may not go out. We would rather show this row as degraded than hide it.
Jira syncoperationalWorkspace data sync behind the dashboard, as listed in the original manifest.

This page reflects the current service manifest. Automated health checks are on the roadmap — until then, report issues via support@jiravision.app.

Method

How this page is kept honest

What backs the claims above, and — just as important — what does not back them yet.

What this is
A manually maintained manifest, stored in content/status.ts alongside the rest of the site's content. Every row is a sentence we verified, not a dashboard widget.
Review cadence
Each component gets checked by a human during every release and whenever a report comes in through /contact. The “last reviewed” timestamp above reflects that pass.
Automated checks
On the roadmap, not shipped. Until real health checks exist this page will keep saying so — the caveat is the deal, not a footnote.
What we won't publish
Uptime percentages, response-time stats and incident counts. We are not measuring them continuously, so a number here would be decoration.

The components

What each row covers

The table tells you the state. This tells you what the state is about, in the same words we would use on a support call.

Marketing website

Every public page you are reading now — product pages, pricing, changelog, this page. Static content on a hosted deployment; there is no clever about it, and that is why it is nearly always fine.

Auth & dashboard

Accounts, login, signup and the product dashboard where Jira data renders. The auth logic itself was untouched by the redesign — restyling stopped at the chrome.

Contact & forms API

The endpoints behind contact, demo, quote, careers and newsletter forms. Submissions are validated, rate-limited and stored even when delivery below is degraded — nothing is silently dropped.

Email delivery

Outbound notifications to the team when forms arrive, plus newsletter confirmation links. Depends on a provider key the owner configures; without a valid one, messages are logged instead of sent. Degraded until confirmed — not hidden.

Jira sync

The data pipeline behind the dashboard: workspace connection, board and sprint sync, metric recalculation. The product's core loop, and the row we watch hardest.

Incident process

What happens if something breaks

This is our process, not a history. There is no archive of past incidents below, because there have been none worth archiving — and we will not invent some to make this section look experienced.

  1. Step 1

    Someone notices

    Usually you, sometimes the manual review pass. Automated detection is on the roadmap, and until it ships we will not claim to catch everything first.

  2. Step 2

    The row changes first

    The affected component moves to degraded or outage on this page, with a plain-language note, before any wider announcement. Changing the page is the first fix, not the last.

  3. Step 3

    Updates in the thread you opened

    If you reported it via /contact or email, follow-ups come back through that channel. There is no status-subscribe system yet and we will not fake one.

  4. Step 4

    It ends in the changelog

    Any user-visible fix or behaviour change gets a dated changelog entry, so the record of what happened lives somewhere durable rather than only in this page's history.

Plainly stated

What this page does not do yet

A status page earns trust by naming its own gaps. Here are ours, before you find them:

01

No uptime percentage

We do not measure continuously, so we do not publish a number. When health checks ship, the honest history comes first and the pretty stats can follow.

02

No incident archive

This section describes process. Publishing a fabricated incident log to look battle-tested would defeat the point of the page.

03

No per-region detail

There is one global deployment; pretending otherwise would be theatre. Regional breakdowns arrive the day real regions do.

Commitments

What we promise about this page itself

The manifest says what it is
Manual review, labelled manual. If automated checks ever ship, this page will say so — and link to the code that says so.
Degraded stays visible
While email delivery depends on an owner-configured key that is not confirmed working, that row stays degraded. Hiding it would be the actual incident.
No invented numbers
No uptime %, no “99.99%”, no response-time promises. This is the same no-fabrication rule the rest of the site runs on — see how we operate it on /about.
Corrections get context
If a status here turns out to be wrong, we fix the page and say what changed rather than editing quietly.

Shipped

Recent changes that touched these systems

  1. 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.

  2. 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.

  3. 2026-08-28

    Feature

    Ethical metrics methodology view

    Every fairness and workload metric now links to the exact formula and data window behind it.

Full changelog

See something we should know?

A report from a real user outranks any dashboard we could build. Forms on this site are stored even when email delivery is degraded, so nothing you send is silently dropped.