locust

locust is the issue tracker of GNU Taler and GNUnet. It serves MantisBT 2.28’s pages, at MantisBT’s page names without the .php, and goes beyond them where a tracker that carries a funded project’s work has to: deadlines that mean something in the plan, a measured clock instead of guessed hours, work that recurs on a schedule, meetings kept with the issues they are about, and a door for the agents that now read and file bugs.

This manual is written for five kinds of reader, and each chapter is addressed to one of them. Nobody is expected to read the others.

Chapters

• Reporters
  • An account
  • Before you report
  • Reporting an issue
  • Following what happens
  • Your account
  • A good report, in one list
• Developers
  • Finding the work
  • The life of an issue
  • Planning
  • The clock
  • Timesheets
  • What to do next
  • Deadlines
  • Fast-track
  • Questions
  • Relationships, duplicates and trees
  • Work that comes back, and meetings
  • Agents
  • Conventions worth keeping
• Managers
  • Running a project
  • Work that comes back
  • Meetings
  • The plan
  • Work packages and budgets
  • Reports and exports
  • What this tracker will not do
• Administrators
  • Requirements
  • Installing
  • Configuring
  • Users and access
  • Mail
  • Rate limits and abuse
  • Importing from MantisBT
  • The cutover
  • Backups
  • Upgrading
  • Monitoring
  • Agents
  • This manual
  • Troubleshooting
• Integrators
  • Getting in
  • Conventions
  • The routes
  • locust’s own fields
  • Other ways out
  • Agents
  • A worked example

Which chapter is yours

Reporters

You found something that is wrong and want it fixed. Getting an account, finding out whether it is already known, writing a report somebody can act on, and following what happens to it.

Developers

You work on the software the tracker tracks. The states an issue walks and who may set them, taking work and the roles that go with it, the clock, deadlines and priorities, what a trivial change may skip, and how an agent is given the same work.

Managers

You decide what gets done and answer for what it cost. Work that recurs, the standing meeting, the plan and the charts that show it, the timesheets you sign, and the projects you run.

Administrators

You install, configure, import, back up and upgrade the tracker. Everything from a fresh database to the cutover from MantisBT.

Integrators

You write something that talks to the tracker. The REST API, which is MantisBT’s, the tokens that open it, the exports, and the door for language models.

How to read a page name

Every page of this tracker has a name, and the name is the URL: the issue list is view_all_bug_page, an issue is view?id=123, a project’s settings are manage_proj_edit_page. Where this manual names a page, that name after your installation’s address opens it, and a MantisBT link with .php in it still works – it is answered with a redirect to the same page without it.

About this manual

It describes locust 0.2.1, the version that serves it: an installation serves its own manual under /manual/, so what you are reading matches the tracker you are reading it from. The pictures are screenshots of a tracker filled with example data (compat/screenshots.py in the source tree takes them); your projects, users and issues will be your own.

The manual is part of locust and shares its licence, the GNU Affero General Public License, version 3 or later. A mistake in it is a bug in locust: report it the way Reporters describes, against the project the tracker itself is filed under.