Skip to content
Tickets

A Kanban that follows your code.

Create tickets, drag them from one status to the next and link them to one or more repositories. The whole team knows where the project stands.

01

Columns that fit you

To do, In progress, In review, Done with the Standard template: change status with drag and drop.

02

Multiple assignees

A ticket can be shared by several people, with search by name or email.

03

Types and priorities

Feature, Bug, Improvement or Task; Low, Normal, High or Urgent priority, on every card.

04

Quick filters

My tickets, High priority, No repository: what matters, one click away.

A complete ticket view

Title, description, type, status, priority, repositories and assignees: the ticket gathers everything you need to move forward, right down to the needs from your design that it fulfills.

  • Sub-tickets, comments with mentions, and attachments
  • Linked pull requests, shown on the ticket
  • Links to the needs the ticket fulfills

Notifications that matter

Assignment, mention, status change: you hear about what concerns you, without the noise.

  • Unread count in the header
  • “Mark all as read” in one click
  • Direct link to the ticket in question

Frequently asked questions

Another question? Read the FAQ or write to us.

Can I customize the statuses?

The columns depend on the Kanban template chosen for the project: the Standard template offers To do, In progress, In review and Done. You can change the template in the project settings.

Are tickets synced with GitHub issues?

No. Grepo tickets are independent of issues, but can be linked to one or more repositories.

Is there a limit on tickets?

No, whatever your plan.

Try Grepo with your team.

The Free plan has no time limit. Move to Pro when your team grows.