Introduction

ProjectVerse is an issue tracker for software teams that also watches production. You plan work in issues, cycles and projects; your services report errors, request logs and health to the same place; and AI assistants like Claude, ChatGPT, Claude Code and Codex can work in it alongside you.

#How it's organised

• Workspace: your company or group. It has members, teams, labels and settings, and lives at its own address like /acme.
• Teams: each team has its own issues, workflow states and cycles. A team has a short key, and its issues are numbered with it: WEB-12 is issue 12 of the WEB team.
• Issues: a title, a description written in a rich text editor, a status, a priority, an assignee, labels, an estimate and a due date. Issues can block, relate to or duplicate each other, and can have sub-issues.
• Cycles: time-boxed rounds of work for a team, with a burn-up chart. Unfinished issues roll over to the next cycle.
• Projects: work that spans issues and teams, with milestones, links and written updates.
• Initiatives: group projects across teams into one larger goal.
• Views, favorites and drafts: save filtered views of issues, pin the things you open most, and keep half-written issues for later.
• Inbox: mentions, assignments and changes to the issues you follow.

#Beyond issues

• Errors and services: add the JavaScript SDK to a service and ProjectVerse groups its errors, keeps its request logs, runs health checks and opens incidents. A new error can open an issue on its own.
• AI assistants: connect Claude, ChatGPT, Claude Code or Codex over MCP with a sign-in. They work as you, with your role.
• Integrations: Slack, GitHub, signed outgoing webhooks, and imports from Linear, Jira, GitHub and CSV.
• The API: everything in the app is in the REST API, with personal API tokens for scripts.

#Where to go next

• New here? Start with Getting started.
• Running your own copy? See Self-hosting and Operations.