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 <tag>:<id>
53
where "<tag>" 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 a well-know location. 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 tag to use. These are the
59
bugtrackers that are built in:
61
------------------------------------------------------------
62
https://bugs.launchpad.net/ | lp | lp:12345
63
http://bugs.debian.org/ | debian | debian:12345
64
http://bugzilla.gnome.org/ | gnome | gnome:12345
66
For the bug trackers that don't have a well known location some
67
configuration is required. Support for generating the URLs for any
68
project using Bugzilla or Trac is built in, along with a template
69
mechanism for other bugtrackers with simple URL schemes.
54
71
If you use Bugzilla or Trac, then you only need to set a configuration
55
72
variable which contains the base URL of the bug tracker. These options
56
73
can go into ``bazaar.conf``, ``branch.conf`` or into a branch-specific
added
removed
bzrlib/bugtracker.py
