Clone this repo:


  1. 9f9ade5 Merge branch 'main' into avm99963-monorail by Adrià Vilanova Martínez · 6 months ago main
  2. 1663d14 Remove mentions to Chromium by Adrià Vilanova Martínez · 8 months ago
  3. de94280 Merge branch 'main' into avm99963-monorail by Adrià Vilanova Martínez · 8 months ago
  4. 2356fff Adapt footer to our instance by Adrià Vilanova Martínez · 10 months ago
  5. 7cc6337 Add mr-vulnz-banner by Adrià Vilanova Martínez · 10 months ago

Monorail Issue Tracker -

This repo is a fork of the open-source Monorail issue tracker designed to run at I've made the code public so it can inspire other developers to host relatively cheap Monorail instances.

Monorail development should generally be contributed upstream, this repo will only accept changes specific to small and relatively cheap instances.

The original file is here below (slightly modified where applicable):

Monorail Issue Tracker

Monorail is the Issue Tracker used by the Chromium project and other related projects. It is hosted at

If you wish to file a bug against Monorail itself, please do so in our self-hosting tracker. We also discuss development of Monorail at

Getting started with Monorail development

For Googlers: Monorail's codebase is open source and can be installed locally on your workstation of choice.

For local development on Linux, see Linux development instructions

Instructions for deploying Monorail to an existing instance or setting up a new instance are here.

See also: Common Development Problems

Feature Launch Tracking

To set up FLT/Approvals in Monorail:

  1. Visit the gear > Development Process > Labels and fields
  2. Add at least one custom field with type "Approval" (this will be your approval
  3. Visit gear > Development Process > Templates
  4. Check "Include Gates and Approval Tasks in issue"
  5. Fill out the chart - The top row is the gates/phases on your FLT issue and you can select radio buttons for which gate each approval goes


To run all Python unit tests, in the appengine/monorail directory run:

make test

For quick debugging, if you need to run just one test you can do the following. For instance for the test IssueServiceTest.testUpdateIssues_Normal in services/test/

../../ test appengine/monorail:services.test.issue_svc_test.IssueServiceTest.testUpdateIssues_Normal --no-coverage

Frontend testing

To run the frontend tests for Monorail, you first need to set up your Go environment. From the Monorail directory, run:

eval `../../go/`

Then, to run the frontend tests, run:

make karma

If you want to skip the coverage for karma, run:

make karma_debug

To run only one test or a subset of tests, you can add .only to the test function you want to isolate:

// Run one test.
it.only(() => {

// Run a subset of tests.
describe.only(() => {

Just remember to remove them before you upload your CL.

Development resources

Supported browsers

Monorail supports all browsers defined in the Chrome Ops guidelines.

File a browser compatability bug here.

Frontend code practices

See: Monorail Frontend Code Practices

Monorail's design

Triage process

See: Monorail Triage Guide.

Release process

See: Monorail Deployment

User guide

For information on how to use Monorail, see the Monorail User Guide.

Setting up a new instance of Monorail

See: Creating a new Monorail instance