Welcome to BugLink’s documentation!

BugLink is a Mercurial extension that helps link changesets with Issue IDs.

The final goal is to be able to ask the list of issue being tackled between two changesets.

BugLink is composed of three components:

• client-side extension
• server-side extension
• web interface

The typical workflow is as follow:

1. A developper is working on an issue on his computer where the client-side extension is enabled, during developement, he indicates the issue ID he is working on.
2. The developper reached a milestone and decides to push his progress to the server. During the push operation, the information about the issue(s) being worked-on is transfered to the server.
3. The server upon reception of the information updates the database with the changesets and their corresponding issue ID.
4. Management heard some progress have been made toward the next release, they point their web-browser to the local web shop, and smile as they see that three more issues have been worked at since the last time they looked at it.

BugLink workflow

The developpers push to the server which updates the database, and management access the database through a web interface

• QuickStart
  • Setup
  • Support call arrives
  • Issue get worked at
  • Issue get tested
  • New release is made
• Installation
  • Client-side extension
  • Server-side extension
  • Web Interface
• Mercurial Extension
  • Client side
  • Server side
• Web interface
  • Introduction
  • Dependencies
• Frequently Asked Questions
  • Why not using the commit message ?
  • Do I need the server-side stuff ?
  • Why not storing the bug state ?
  • How do I import all my issues as a batch ?
• For Developpers
  • Write tests
  • Unit-tests
  • Flask-tests
  • Upgrade the DB Schema
• ToDo List