Skip to content
JiraVision

Getting help

How to reach us and what to include so the first reply is useful.

Getting help

Where to go

  • /contact — the support and sales form. It posts to /api/contact, is rate limited, and stores the message so someone can pick it up.
  • /faq — the full question set, grouped by Product, Pricing, Migration, Company and Security, with a link from each answer to the page that explains it properly.
  • /status — current service state before you report an outage.
  • /accessibility — how to report an accessibility barrier specifically.

There is no community forum, no chat widget and no ticketing system in this product. The contact form is the supported channel.

What to include

  1. The route you were on, for example /dashboard/reports.
  2. What you did, in order.
  3. What you expected and what happened instead.
  4. The API call from the network tab: method, path, status code and response body.
  5. Whether it reproduces in a private window with extensions disabled.

Item 4 is the one that turns a day of guessing into a fix. Item 5 rules out the most common false positive: a browser extension injecting markup and causing a hydration error that is not in the app.

Before you write

  • Check the common issues doc — the bell, empty pages, 403 and 409 cases are all covered there.
  • Check /status for a known incident.
  • Confirm your session is live with GET /api/user/current.

Reporting a security problem

Use /contact and say plainly that it is a security report. Do not post credentials, tokens or customer data in the message; describe where they are instead.

Accessibility reports

Send them through /contact with the page, the assistive technology and browser, and what broke. The accessibility statement page lists the conformance target and the known gaps.