tree: 336f2b5a2f2294256b8f958f69c0a4e39758febd [path history] [tgz]
  1. api/
  2. businesslogic/
  3. doc/
  4. features/
  5. framework/
  6. google/
  7. mrproto/
  8. project/
  9. schema/
  10. search/
  11. services/
  12. sitewide/
  13. static/
  14. static_src/
  15. templates/
  16. testing/
  17. third_party/
  18. tools/
  19. tracker/
  20. .babelrc
  21. .coveragerc
  22. .eslintrc.json
  23. .expect_tests.cfg
  25. .gitignore
  26. .npmrc
  27. .prettierrc.json
  28. .style.yapf
  29. .testcoveragerc
  30. .vpython3
  31. app.yaml
  33. codereview.settings
  34. cron.yaml
  35. dev-services.yml
  36. dispatch.yaml
  38. jsconfig.json
  39. karma.conf.js
  41. Makefile
  42. module-api.yaml
  43. module-besearch.yaml
  44. module-latency-insensitive.yaml
  45. OWNERS
  46. package-lock.json
  47. package.json
  49. queue.yaml
  53. requirements.py2.txt
  54. requirements.txt
  57. tsconfig.json
  58. webpack.config.js

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 For local development on MacOS and Debian, see MacOs 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