Build in public

Plan in private.Publish what you choose.

Take bug reports, show your roadmap and publish your changelog and docs from the same place you plan the work.

What’s included

Everything on this page needs a paid plan. See pricing

  • A public tracker where visitors file bugs and requests, with spam protection and similar-issue hints.

  • Signed-in visitors vote and comment, and you triage and moderate.

  • A public roadmap with vote totals.

  • A public changelog with email subscribers, who confirm before they get anything, and RSS.

  • Two-way sync with GitHub Issues, plus a one-time import.

  • Security issues can be reported privately.

  • Intake forms and an embeddable submit widget.

  • Reporters get email updates on their issue.

  • Publish customer docs at a public URL, and opt in to the docs directory and sitemap.

The public tracker

Let people tell youwhat’s broken.

Everything on this page is on paid plans. Turn on a public tracker for a project and visitors can file bugs and feature requests without an account. Spam protection sits in front of the form, and as someone types a title they see similar issues that already exist, so a duplicate can become a vote.

Signed-in visitors vote and comment. You triage what comes in, set the public status and moderate comments. Reporters who leave an email get updates when their issue moves.

Security problems have their own private form, so they never land on the public list. You can build intake forms with the fields you need, and put a submit widget on your own site. See ours.

Public issues

  • 23votes

    #41 Export a board to CSV

    Feature requestPlanned
  • 9votes

    #38 Dark mode resets after sign-in

    BugIn progress
  • 1vote

    #35 Search ignores archived items

    BugOpen
Illustration. Names and numbers are examples.

Roadmap and changelog

Show what’s next.Say what shipped.

The public roadmap sorts items into Now, Next and Later, with what has shipped listed below. Each item shows its vote total, so people can see what has been asked for.

The changelog is where release notes go. Visitors subscribe by email and confirm before they get anything, then get one email per release. There is an RSS feed for anyone who would rather read it there.

Changelog

RSS

v2.4.0 · Released 3 March

CSV export and faster search

  • Export any board to CSV.
  • Search now includes archived items.
  • Fixed: dark mode no longer resets after sign-in.

Get release notes by email

One email per release.

you@example.comSubscribe

A confirmation link goes out first. Nothing else is sent until it’s opened.

Illustration. Names, versions and dates are examples.

GitHub Issues

Keep GitHub Issues.Stay in step with it.

Link a repository and your public issues sync with GitHub Issues both ways. Titles, descriptions, labels and comments cross in either direction, and a close on one side shows up on the other.

Moving over from GitHub? A one-time import brings a repository’s issues into the tracker, numbered in your project’s own sequence.

ezmodo

Public issue #41

GitHub Issues

acme/app #187

  • Title and descriptionBoth ways
  • LabelsBoth ways
  • CommentsBoth ways
  • Open and closedBoth ways
Illustration. The repository and issue numbers are examples.

Public docs

Publish your docswhere you write them.

Write customer documentation in ezmodo and publish it at a public URL. Nobody needs an account to read it.

If you want it found, opt in to the public docs directory and the sitemap. If you don’t, it stays at its own address and is listed nowhere else.

Connect your agent.The record writes itself.