Features / Unfeatures

Want to jump right in and experience it for yourself? Try taking the tour!

We consider these features to be the core requirements of a bug tracker. You can read more about what we haven't included and (most importantly, why) on our blog.


  • Editor basics

    The Basics

    Tickets have a few basic attributes:

    • A title and number (for easy bug reviews).
    • A status, one of:
    • A priority, just: Priorityhigh Prioritynormal or Prioritylow
    • An assignee. Who's on this right now.
    • A reporter. Whoever created the ticket.
    • And finally the list it is currently in.
  • Editor comment

    Markdown Comments

    Markdown makes crafting clear descriptions and comments super satisfying. You can also use some custom extensions to link to tickets (e.g. [ticket:5] or [list:1.0]).

  • Code highlighting1

    Code Blocks & Highlighting

    Enclose your code in fences like so:

    ~~~ language
    # code...

    And you'll get nice colored output in practically any language you can think of.

  • Mentions

    Mentions w/ Auto-watchlist

    Just type an @ and you get a familiar (because every other app in the world does the same thing) interface to choose a team member. Mentioned people will be automatically added to the ticket watchlist.

  • Editor attachment

    Detailed History

    Every edit or change to a ticket shows up in its history, letting you follow a ticket back to the beginning giving you a full audit trail.

  • Editor tags

    Tiny Tagging

    Tags are useful for marking things with extra metadata when displayed in lists. You might use a tag like 'bucket' for the inevitable all-encompasing ticket. Or maybe you want to mark problems that only affect the 'admin' part of your app.

  • Editor watchlist


    Get emails about any ticket you like by adding yourself (or someone else for that matter) to the watchlist. Configure what you want to watch by default on your profile page, and get the notifications that you need.

  • Slack

    Slack Integration

    Connect Bugrocket to a channel in your Slack team and ticket notifications will be posted automatically.


  • Org

    Project → List → Ticket

    As many projects as you need and as many sub-lists of tickets as makes sense. Easily organize by release, feature or type of issue (feature request, bug, etc).

  • Miniwiki

    Describe Your Lists

    Annotate lists with markdown. Scheduled deploy date? Pre/post steps? Pep-talk? It's kind of like a mini wiki at the top of every list.

  • Changelog

    See the Big Picture

    Per-project changelogs show you every edit made, by who and when. This is great for project managers who need to see what's been happening, or just as a email-less way to keep up on changes.

  • Acl

    Project Access Permissions

    Super simple access control*. You will really need this if you have independent teams working inside one Bugrocket account on multiple projects.

    No need for multiple accounts and multiple logins, just setup each project with a ACL and give users access who need it, simple as that.

Navigation / Search

  • Flexible views

    Flexible Views

    View the specific list you care about, a project's changelog, all tickets assigned to you, reported by you, or watched by you. You can change your default 'landing page' in your profile so you always see your assigned tickets first, or whatever makes sense for how you work.

  • Filtering

    Awesome List Filtering

    Super fast live filtering of list views with some simple controls based on status, priority and assignee/reporter. Even better your filters are persisted, so navigate between pages and back and you'll still see the same filtered list.

  • Apache solr

    Full-text Search

    Ticket title, tags and comments are indexed for full-text search. You can also use some fancy incantations to find only tickets with a certain status or assigned to a specific person.

Account Management

  • Custom logo default

    Custom Logo

    Upload your company logo. It will be used on all pages in your account as well as emails.

  • Avatar

    User Information

    Names, emails and avatars for easy identification. If you use gravatar, you don't even need to do anything.

  • Userinfo

    User 'Roles'

    Set users as account admins (they can create projects and lists/etc), or not. Activate them or deactivate them (preventing them from logging in). Set the primary user (who will receive account level communications like receipts).

  • Prefs


    Set where you want to land when you login, what you watch by default, the by-id sort direction of tickets, and of course your avatar/email/name/timezone.

API Access

  • Api

    Read API

    0 configuration read API access, credentials visible to admins. Use it to back up your own data or move it elsewhere — we don't hold your data hostage!

    Write API

    Our write API is coming soon!