All Features

Issues that belong to teams, not repositories.

Repolaris organizes work around teams, not code. Define workflows that match your process. Track issues with readable keys like ENG-123. Plan sprints, create views, and collaborate in real-time.

Why teams matter

Traditional tools force issues into repositories. But work doesn't always map to code that cleanly. Repolaris organizes issues around teams—the people who actually do the work.

  • Issues can span multiple repositories
  • Teams have their own workflows and settings
  • Clear ownership and accountability
  • Readable issue keys: ENG-123, OPS-45, DESIGN-8

Team Workspace

Inbox

New issues that need triage

Active

Work currently in progress

Backlog

Prioritized future work

Archive

Completed and closed issues

Powerful issues

Default workflow: Triage → Backlog → Unstarted → Started → In Review → Completed → Canceled

Rich Issue Tracking

  • Customizable workflows

    Define states that match your process. Not just "open" and "closed".

  • Sub-issues

    Break complex work into manageable pieces. Track progress at every level.

  • Relations

    Blocks, blocked by, related to, duplicate of, parent/child connections.

  • Custom fields

    Add fields specific to your workflow. (Enterprise)

Issue Details

  • Markdown descriptions

    Rich formatting with full Markdown support.

  • Priority levels

    Urgent, High, Medium, Low, None.

  • Estimates & due dates

    Plan and track deadlines.

  • Labels & assignees

    Categorize and assign ownership.

Real-time Kanban boards

Live updates

See changes as they happen. Drag a card and everyone sees it move—instantly.

Concurrent editing

Multiple team members can reorganize the board simultaneously. No conflicts.

Presence indicators

See who's viewing the board right now.

Columns & swimlanes

Customize to match your workflow. Group by assignee or priority.

WIP limits

Set work-in-progress limits. Visual indicators when exceeded.

Planning tools

Cycles (Sprints)

  • Flexible duration: 1-week, 2-week, or custom
  • Capacity planning: See how much work fits
  • Automatic rollover: Unfinished work moves forward
  • Progress tracking: Burndown and burnup charts

Views

  • Personal views: Your own saved filters
  • Team views: Shared with your team
  • Organization views: Visible across the org
  • Multiple types: List, board, table, timeline (coming)

Initiatives

  • Cross-team alignment: Span multiple teams
  • Progress rollup: See aggregate completion
  • Roadmap visibility: Communicate what's coming

Deep Git connection

While issues belong to teams, they connect naturally to code.

  • Linked repositories

    Associate issues with relevant repos.

  • Branch creation

    Create branches directly from issues.

  • PR references

    Fixes ENG-123 links and updates automatically.

  • Commit tracking

    See commits related to an issue.

Status Automation

  • Issues update when linked PRs are opened
  • Issues close when linked PRs merge
  • CI status visible on related issues

How we compare

FeatureRepolarisLinearGitHubJira
Team-centric model——
Readable issue keys—
Custom workflowsLimited
Real-time boards——
Sub-issues—
Integrated with Git——
Integrated CI/CD——

Why teams switch

From Jira

  • Faster, more responsive interface
  • Native Git integration
  • No context switching
  • Modern design

From GitHub Issues

  • Team-centric organization
  • Readable issue keys
  • Custom workflows
  • Real-time boards

From Linear

  • Integrated Git hosting
  • Built-in CI/CD
  • EU data residency
  • Self-hosted option

Ready to manage projects differently?

Try team-centric project management today.