Sitemoth fix tickets

Sitemoth sends the problems in a crawl to your tracker as tickets a developer can act on. Press Send to tracker on the Overview, or on any problem to send just that one.

Connect a tracker

Sitemoth needs one credential per tracker. It stores them encrypted on your computer and sends requests straight to the tracker:

  • Jira Cloud needs your site URL, account email and an API token.
  • Linear needs a personal API key.
  • Asana needs a personal access token.
  • ClickUp needs a personal API token.
  • Trello needs an API key and a token.
  • GitHub needs a token with access to the repository's issues.

Press Connect, then pick the project, team, list or repository the tickets go to. A client's default tracker is filled in for that client's crawls.

How Sitemoth groups tickets

Sitemoth makes one ticket per problem and page template, such as every product page with the same missing description. A problem on 10 pages or fewer becomes one ticket. Each ticket holds the problem in plain English, why it matters, how to fix it, its severity, the first 25 URLs and a CSV of all of them. Sitemoth remembers what it sent, so sending again skips tickets that already exist.

sitemoth tickets acme.sitemoth --provider linear --list-targets
sitemoth tickets acme.sitemoth --provider linear --target TEAM_ID --dry-run
sitemoth tickets acme.sitemoth --provider jira --target PROJ --min-severity warning

The command line reads credentials from environment variables such as SITEMOTH_JIRA_TOKEN.

Back to getting started with Sitemoth · Sitemoth home