1 ***********************
2 Distributed Bugtracking
3 ***********************
8 Case 1: Tracking the status of bugs in remote repo branches
9 -----------------------------------------------------------
12 #bea86499-824e-4e77-b085-2d581fa9ccab/12c986be-d19a-4b8b-b1b5-68248ff4d331#.
13 Here, it doesn't matter whether the remote repository is a branch of
14 the local repository, or a completely separate project
15 (e.g. upstream, ...). So long as the remote project provides access
16 via some REPO format, you can use::
20 to run your query, or::
24 to see the changes between the local and remote repositories.
27 Case 2: Importing bugs from other repositories
28 ----------------------------------------------
30 Case 2.1: If the remote repository is a branch of the local repository::
34 Case 2.2: If the remote repository is not a branch of the local repository
35 (Hypothetical command)::
37 $ be import <REPO> <ID>
43 Providing public repositories
44 -----------------------------
46 e.g. for non-dev users. These are just branches that expose a public
47 interface (HTML, email, ...). Merge and query like any other
54 Many bugtrackers implement some sort of permissions system, and they
55 are certainly required for a central system with diverse user roles.
56 However DVCSs also support the "pull my changes" workflow, where
57 permissions are irrelevant.