44
44
recorded by using the --fixes option. For each bug marked as fixed, an
45
45
entry is included in the 'bugs' revision property stating '<url> <status>'.
46
46
(The only ``status`` value currently supported is ``fixed.``)
47
Support for Launchpad's central bug tracker is built in. For other bug
48
trackers, configuration is required in advance so that the correct URL
51
In addition to Launchpad, Bazaar directly supports the generation of
52
URLs appropriate for Bugzilla and Trac. If your project uses a different
53
bug tracker, it is easy to add support for it.
48
The --fixes option allows you to specify a bug tracker and a bug identifier
49
rather than a full URL. This looks like
51
bzr commit --fixes <tracker>:<id>
53
where "<tracker>" is an identifier for the bug tracker, and "<id>" is the
54
identifier for that bug within the bugtracker, usually the bug number.
56
Bazaar knows about a few bug trackers that have many users. If
57
you use one of these bug trackers then there is no setup required to
58
use this feature, you just need to know the tracker identifier to use.
59
These are the bugtrackers that are built in:
61
URL | Abbreviation | Example
62
https://bugs.launchpad.net/ | lp | lp:12345
63
http://bugs.debian.org/ | deb | deb:12345
64
http://bugzilla.gnome.org/ | gnome | gnome:12345
66
For the bug trackers not listed above configuration is required.
67
Support for generating the URLs for any project using Bugzilla or Trac
68
is built in, along with a template mechanism for other bugtrackers with
69
simple URL schemes. If your bug tracker can't be described by one
70
of the schemes described below then you can write a plugin to support
54
73
If you use Bugzilla or Trac, then you only need to set a configuration
55
74
variable which contains the base URL of the bug tracker. These options
56
75
can go into ``bazaar.conf``, ``branch.conf`` or into a branch-specific
added
removed
bzrlib/bugtracker.py
