Skip to content
JiraVision

JiraVision overview

What the product is, where each feature lives and how the pieces fit together.

JiraVision overview

JiraVision is an AI-assisted project management workspace. This page maps the product so you know where to go for each job.

What you get

  • Delivery: tasks, a kanban board, a backlog, sprints, goals and a calendar
  • AI: an AI Scrum Master that drafts sprint plans and writes a rationale you can reject
  • People: team wellbeing check-ins, gamification, ethical metrics and team chat
  • Operations: reports with CSV/JSON export, an activity feed, automations, billing and settings
  • Governance: team workspace settings, role changes with an audit log, and a super-admin content manager for the marketing pages

Where things live

  1. Sign in at /login (or create an account at /signup).
  2. The dashboard shell lives at /dashboard. The left navigation is grouped into Main, Planning, AI Features, Team, Metrics and Applications.
  3. Every dashboard page reads and writes through /api routes — there is no mock data layer in the signed-in app.
  4. Marketing pages (home, pricing, products, solutions, resources) are editable by a super-admin from /admin/cms.

How data flows

  • Your session is one HttpOnly cookie (jv_session) backed by a row in auth_sessions. See the authentication doc.
  • Dashboard mutations write a row to Postgres and then create a notification for the people affected.
  • Notifications reach open browsers through the SSE feed at /api/notifications/live, which is what drives the bell in the top bar.

What this product is not

  • There is no public SDK and no bearer-token API. The API is the same cookie-session API the dashboard uses.
  • Direct Jira site import is configuration-only in this build; the CSV importer is the real path.
  • Wellbeing never reads message content. Check-ins are self-reported and aggregated.