aboutsummaryrefslogtreecommitdiffstats
path: root/phpBB/phpbb/controller/resolver.php
diff options
context:
space:
mode:
Diffstat (limited to 'phpBB/phpbb/controller/resolver.php')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.1 (git 2.21.0) at 2025-09-12 23:14:34 +0000
id='n84' href='#n84'>84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 3072 3073 3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 

The Bugzilla Guide

Matthew P. Barnson

   barnboy@trilobyte.net

   This is the documentation for Bugzilla, the Mozilla bug-tracking
   system.
     _________________________________________________________________

   Table of Contents
   1. About This Guide

        1.1. Purpose and Scope of this Guide
        1.2. Copyright Information
        1.3. Disclaimer
        1.4. New Versions
        1.5. Credits
        1.6. Contributors
        1.7. Feedback
        1.8. Translations
        1.9. Document Conventions

   2. Installing Bugzilla

        2.1. UNIX Installation
        2.2. Win32 (Win98+/NT/2K) Installation

   3. Administering Bugzilla

        3.1. Post-Installation Checklist
        3.2. User Administration
        3.3. Product, Component, Milestone, and Version Administration
        3.4. Bugzilla Security

   4. Using Bugzilla

        4.1. What is Bugzilla?
        4.2. Why Should We Use Bugzilla?
        4.3. How do I use Bugzilla?
        4.4. What's in it for me?
        4.5. Using Bugzilla-Conclusion

   5. Integrating Bugzilla with Third-Party Tools

        5.1. Bonsai
        5.2. CVS
        5.3. Perforce SCM
        5.4. Tinderbox

   6. The Future of Bugzilla

        6.1. Reducing Spam
        6.2. Better Searching
        6.3. Description Flags and Tracking Bugs
        6.4. Bug Issues
        6.5. Database Integrity
        6.6. Bugzilla 3.0

   A. The Bugzilla FAQ
   B. The Bugzilla Database

        B.1. Database Schema Chart
        B.2. MySQL Bugzilla Database Introduction
        B.3. MySQL Permissions & Grant Tables
        B.4. Cleaning up after mucking with Bugzilla

   C. Useful Patches and Utilities for Bugzilla

        C.1. The setperl.pl Utility
        C.2. Command-line Bugzilla Queries
        C.3. The Quicksearch Utility

   D. GNU Free Documentation License

        0. PREAMBLE
        1. APPLICABILITY AND DEFINITIONS
        2. VERBATIM COPYING
        3. COPYING IN QUANTITY
        4. MODIFICATIONS
        5. COMBINING DOCUMENTS
        6. COLLECTIONS OF DOCUMENTS
        7. AGGREGATION WITH INDEPENDENT WORKS
        8. TRANSLATION
        9. TERMINATION
        10. FUTURE REVISIONS OF THIS LICENSE
        How to use this License for your documents

   Glossary

   List of Examples
   3-1. Creating some Components
   3-2. Common Use of Versions
   3-3. A Different Use of Versions
   3-4. Using SortKey with Target Milestone
   3-5. When to Use Group Security
   3-6. Creating a New Group
   4-1. Some Famous Software Versions
   4-2. Mozilla Webtools Components
   1. A Sample Product
     _________________________________________________________________

Chapter 1. About This Guide

1.1. Purpose and Scope of this Guide

   This document was started on September 17, 2000 by Matthew P. Barnson
   after a great deal of procrastination updating the Bugzilla FAQ, which
   I left untouched for nearly half a year. After numerous complete
   rewrites and reformatting, it is the document you see today.

   Despite the lack of updates, Bugzilla is simply the best piece of
   bug-tracking software the world has ever seen. This document is
   intended to be the comprehensive guide to the installation,
   administration, maintenance, and use of the Bugzilla bug-tracking
   system.

   This release of the Bugzilla Guide is the 2.11 release. It is so named
   that it may match the current version of Bugzilla. The numbering
   tradition stems from that used for many free software projects, in
   which even-numbered point releases (1.2, 1.14, etc.) are considered
   "stable releases", intended for public consumption; on the other hand,
   odd-numbered point releases (1.3, 2.09, etc.) are considered unstable
   development releases intended for advanced users, systems
   administrators, developers, and those who enjoy a lot of pain.

   Newer revisions of the Bugzilla Guide will follow the numbering
   conventions of the main-tree Bugzilla releases, available at
   Mozilla.org, with the exception that intermediate releases will have a
   minor revision number following a period. For instance, if the current
   version of Bugzilla is 4.2, the current "stable" version of the
   Bugzilla guide, in, say, it's fifth revision, would be numbered
   "4.2.5". Got it? Good.

   I wrote this in response to the enormous demand for decent Bugzilla
   documentation. I have incorporated instructions from the Bugzilla
   README, Frequently Asked Questions, Database Schema Document, and
   various mailing lists to create it. Chances are, there are glaring
   errors in this documentation; please contact <barnboy@trilobyte.net>
   to correct them.
     _________________________________________________________________

1.2. Copyright Information



   Permission is granted to copy, distribute and/or modify this document
   under thei terms of the GNU Free Documentation License, Version 1.1 or
   any later version published by the Free Software Foundation; with no
   Invariant Sections, no Front-Cover Texts, and with no Back-Cover
   Texts. A copy of the license is included in the section entitled "GNU
   Free Documentation LIcense".

   --Copyright (c) 2000-2001 Matthew P. Barnson

   If you have any questions regarding this document, its' copyright, or
   publishing this document in non-electronic form, please contact
   <barnboy@trilobyte.net>
     _________________________________________________________________

1.3. Disclaimer

   No liability for the contents of this document can be accepted. Use
   the concepts, examples, and other content at your own risk. As this is
   a new edition of this document, there may be errors and inaccuracies
   that may damage your system. Use of this document may cause your
   girlfriend to leave you, your cats to pee on your furniture and
   clothing, your computer to cease functioning, your boss to fire you,
   and global thermonuclear war. Proceed with caution.

   All copyrights are held by their respective owners, unless
   specifically noted otherwise. Use of a term in this document should
   not be regarded as affecting the validity of any trademark or service
   mark. In particular, I like to put down Microsoft(tm). Live with it.

   Naming of particular products or brands should not be seen as
   endorsements, with the exception of the term "GNU/Linux". Use
   GNU/Linux. Love it. Bathe with it. It is life and happiness. I endorse
   it wholeheartedly and encourage you to do the same.

   You are strongly recommended to make a backup of your system before
   installing Bugzilla and at regular intervals thereafter. Heaven knows
   it's saved my bacon time after time; if you implement any suggestion
   in this Guide, implement this one!

   Bugzilla has not undergone a complete security review. Security holes
   probably exist in the code. Great care should be taken both in the
   installation and usage of this software. Carefully consider the
   implications of installing other network services with Bugzilla.
     _________________________________________________________________

1.4. New Versions

   This is the initial release of the Bugzilla Guide.

   This document can be found in the following places:

     * TriloBYTE
     * Mozilla.org
     * The Linux Documentation Project

   The latest version of this document can be checked out via CVS. Please
   follow the instructions available at the Mozilla CVS page, and check
   out the mozilla/webtools/bugzilla/docs/ branch.
     _________________________________________________________________

1.5. Credits

   The people listed below have made enormous contributions to the
   creation of this Guide, through their dedicated hacking efforts,
   numerous e-mail and IRC support sessions, and overall excellent
   contribution to the Bugzilla community:

   Terry Weissman for initially converting Bugzilla from BugSplat! and
   writing the README upon which this documentation is largely based.

   Tara Hernandez for keeping Bugzilla development going strong after
   Terry left Mozilla.org

   Dave Lawrence for providing insight into the key differences between
   Red Hat's customized Bugzilla, and being largely responsible for the
   "Red Hat Bugzilla" appendix

   Dawn Endico for being a hacker extraordinaire and putting up with my
   incessant questions and arguments on irc.mozilla.org in #mozwebtools

   Last but not least, all the members of the
   netscape.public.mozilla.webtools newsgroup. Without your discussions,
   insight, suggestions, and patches, this could never have happened.
     _________________________________________________________________

1.6. Contributors

   Thanks go to these people for significant contributions to this
   documentation:

   Zach Lipton, Andrew Pearson, Spencer Smith, Eric Hansen
     _________________________________________________________________

1.7. Feedback

   I welcome feedback on this document. Without your submissions and
   input, this Guide cannot continue to exist. Please mail additions,
   comments, criticisms, etc. to <barnboy@trilobyte.net>. Please send
   flames to <devnull@localhost>
     _________________________________________________________________

1.8. Translations

   The Bugzilla Guide needs translators! Please volunteer your
   translation into the language of your choice. If you will translate
   this Guide, please notify the members of the mozilla-webtools mailing
   list at <mozilla-webtools@mozilla.org>
     _________________________________________________________________

1.9. Document Conventions

   This document uses the following conventions

   Descriptions Appearance
   Warnings

   Caution

   Warnings.
   Hint

     Tip: Hint.

   Notes

     Note: Note.

   Information requiring special attention

   Warning

   Warning.
   File Names file.extension
   Directory Names directory
   Commands to be typed command
   Applications Names application
   Prompt of users command under bash shell bash$
   Prompt of root users command under bash shell bash#
   Prompt of user command under tcsh shell tcsh$
   Environment Variables VARIABLE
   Emphasized word word
   Code Example
   <para>Beginning and end of paragraph</para>
     _________________________________________________________________

Chapter 2. Installing Bugzilla

2.1. UNIX Installation

     Note: Please consult the README included with the Bugzilla
     distribution as the current canonical source for UNIX installation
     instructions. We do, however, have some installation notes for
     errata from the README.

     Note: If you are installing Bugzilla on S.u.S.e. Linux, or some
     other distributions with "paranoid" security options, it is
     possible that the checksetup.pl script may fail with the error:
     cannot chdir(/var/spool/mqueue): Permission denied This is because
     your /var/spool/mqueue directory has a mode of "drwx------". Type
     chmod 755 /var/spool/mqueue as root to fix this problem.

     Note:
     _________________________________________________________________

2.2. Win32 (Win98+/NT/2K) Installation

   These directions have not been extensively tested. We need testers!
   Please try these out and post any changes to the newsgroup.
     _________________________________________________________________

2.2.1. Win32 Installation: Step-by-step

     Note: You should be familiar with, and cross-reference, the UNIX
     README while performing your Win32 installation. Unfortunately,
     Win32 directions are not yet as detailed as those for UNIX.

     The most critical difference for Win32 users is the lack of support
     for a crypt() function in MySQL for Windows. It does not have it!
     All ENCRYPT statements must be modified.

    1. Install Apache Web Server for Windows.

     Note: You may also use Internet Information Server or Personal Web
     Server for this purpose. However, setup is slightly more difficult.
     If ActivePerl doesn't seem to handle your file associations
     correctly (for .cgi and .pl files), please consult the FAQ, in the
     "Win32" section.
     If you are going to use IIS, if on Windows NT you must be updated
     to at least Service Pack 4.
    2. Install ActivePerl
       Please also check the following links to fully understand the
       status of ActivePerl on Win32: Perl Porting, and Hixie Click Here
    3. Use ppm from your perl\bin directory to install the following
       packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, and
       GD. You may need to extract them from .zip format using Winzip or
       other unzip program first. These additional ppm modules can be
       downloaded from ActiveState.
       The syntax for ppm is: C:> ppm install <module>.ppd
       You can find ActiveState ppm modules at
       http://www.activestate.com/PPMPackages/5.6plus
    4. Download and install the Windows GNU tools from www.cygwin.com.
       Make sure the GNU utilities are in your $PATH.
    5. Install MySQL for NT.

     Note: Your configuration file for MySQL must be named C:\MY.CNF.
    6. Setup MySQL
         a. C:> C:\mysql\bin\mysql -u root mysql
         b. mysql> DELETE FROM user WHERE Host='localhost' AND User='';
         c. mysql> UPDATE user SET Password=PASSWORD ('new_password')
            WHERE user='root';
         d. mysql> GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, ALTER,
            CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost
            IDENTIFIED BY 'bugs_password';
         e. mysql> FLUSH PRIVILEGES;
         f. mysql> create database bugs;
         g. mysql> exit
         h. C:> C:\mysql\bin\mysqladmin -u root -p reload
    7. Configure Bugzilla. For Win32, this involves editing
       "defparams.pl" and "localconfig" to taste. Running "checksetup.pl"
       should create localconfig for you. Note that getgrnam() doesn't
       work, and should be deleted. Change this line: "my $webservergid =
       getgrnam($my_webservergroup); " to "my $webservergid =
       $my_webservergroup; "
    8.

     Note: There are several alternatives to Sendmail that will work on
     Win32. The one mentioned here is a suggestion, not a requirement.
     Some other mail packages that can work include BLAT, Windmail,
     Mercury Sendmail, and the CPAN Net::SMTP Perl module (available in
     .ppm). Every option requires some hacking of the Perl scripts for
     Bugzilla to make it work. The option here simply requires the
     least.
       Download NTsendmail, available from www.ntsendmail.com. In order
       for it to work, you must set up some new environment variables
       (detailed on the ntsendmail home page). Figuring out where to put
       those variables is left as an exercise for the reader. You must
       have a "real" mail server which allows you to relay off it in your
       $ENV{"NTsendmail"} (which you should probably place in globals.pl)
       Once downloaded and installed, modify all open(SENDMAIL) calls to
       open "| c:\ntsendmail\ntsendmail -t" instead of
       "|/usr/lib/sendmail -t".

     Note: We need someone to test this and make sure this works as
     advertised.
    9. Modify globals.pl and CGI.pl to remove the word "encrypt".

     Note: I'm not sure this is all that is involved to remove crypt.
     Any NT Bugzilla hackers want to pipe up?
   10. Change all references to "processmail" to "processmail.pl" in all
       files, and rename "processmail" to "processmail.pl"

     Note: I really think this may be a change we want to make for
     main-tree Bugzilla. It's painless for the UNIX folks, and will make
     the Win32 people happier.
   11. Modify the path to perl on the first line (#!) of all files to
       point to your Perl installation, and add "perl" to the beginning
       of all Perl system calls that use a perl script as an argument.
       This may take you a while. There is a "setperl.pl" utility to
       speed part of this procedure, available in the "Patches and
       Utilities" section of The Bugzilla Guide.
   12. In processmail.pl, add "binmode(HANDLE)" before all read() calls.
       This may not be necessary, but in some cases the read() under
       Win32 doesn't count the EOL's without using a binary read().
     _________________________________________________________________

2.2.2. Additional Windows Tips

     Tip: From Andrew Pearson:

     "You can make Bugzilla work with Personal Web Server for Windows 98
     and higher, as well as for IIS 4.0. Microsoft has information
     available at
     http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP

     Basically you need to add two String Keys in the registry at the
     following location:

     HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Paramete
     rs\ScriptMap

     The keys should be called ".pl" and ".cgi", and both should have a
     value something like: c:/perl/bin/perl.exe "%s" "%s"

     The KB article only talks about .pl, but it goes into more detail
     and provides a perl test script.
     _________________________________________________________________

Chapter 3. Administering Bugzilla

   Or, I just got this cool thing installed. Now what the heck do I do
   with it?

   So you followed the README isntructions to the letter, and just logged
   into bugzilla with your super-duper god account and you are sitting at
   the query screen. Yet, you have nothing to query. Your first act of
   bisuness needs to be to setup the operating parameters for bugzilla.
     _________________________________________________________________

3.1. Post-Installation Checklist

   After installation, follow the checklist below to ensure that you have
   a successful installation. If you do not see a recommended setting for
   a parameter, consider leaving it at the default while you perform your
   initial tests on your Bugzilla setup.
    1. Set "maintainer" to your email address. This allows Bugzilla's
       error messages to display your email address and allow people to
       contact you for help.
    2. Set "urlbase" to the URL reference for your Bugzilla installation.
       If your bugzilla query page is at
       http://www.foo.com/bugzilla/query.cgi, your url base is
       http://www.foo.com/bugzilla/
    3. Set "usebuggroups" to "1" only if you need to restrict access to
       products. I suggest leaving this parameter off while initially
       testing your Bugzilla.
    4. Set "usebuggroupsentry" to "1" if you want to be able to restrict
       access to products. Once again, if you are simply testing your
       installation, I suggest against turning this parameter on; the
       strict security checking may stop you from being able to modify
       your new entries.
    5. Set "shadowdb" to "bug_shadowdb" if you will be running a *very*
       large installation of Bugzilla. The shadow database enables many
       simultaneous users to read and write to the database without
       interfering with one another.

     Note: Enabling "shadowdb" can adversely affect the stability of
     your installation of Bugzilla. You may frequently need to manually
     synchronize your databases, or schedule nightly syncs via "cron"
       Once again, in testing you should avoid this option -- use it if
       or when you need to use it, and have repeatedly run into the
       problem it was designed to solve -- very long wait times while
       attempting to commit a change to the database.
       If you use the "shadowdb" option, it is only natural that you
       should turn the "queryagainstshadowdb" option "On" as well.
       Otherwise you are replicating data into a shadow database for no
       reason!
    6. If you have custom logos or HTML you must put in place to fit
       within your site design guidelines, place the code in the
       "headerhtml", "footerhtml", "errorhtml", "bannerhtml", or
       "blurbhtml" text boxes.

     Note: The "headerhtml" text box is the HTML printed out before any
     other code on the page. If you have a special banner, put the code
     for it in "bannerhtml". You may want to leave these settings at the
     defaults initially.
    7. Add any text you wish to the "passwordmail" parameter box. For
       instance, many people choose to use this box to give a quick
       training blurb about how to use Bugzilla at your site.
    8. Set "newemailtech" to "on". Your users will thank you. This is the
       default in the post-2.12 world.
    9. Do you want to use the qa contact ("useqacontact") and status
       whiteboard ("usestatuswhiteboard") fields? These fields are useful
       because they allow for more flexibility, particularly when you
       have an existing Quality Assurance and/or Release Engineering
       team, but they may not be needed for smaller installations.
   10. Set "whinedays" to the amount of days you want to let bugs go in
       the "New" or "Reopened" state before notifying people they have
       untouched new bugs. If you do not plan to use this feature, simply
       do not set up the whining cron job described in the README, or set
       this value to "0".
   11. Set the "commenton" options according to your site policy. It is a
       wise idea to require comments when users resolve, reassign, or
       reopen bugs.

     Note: It is generally far better to require a developer comment
     when resolving bugs than not. Few things are more annoying to bug
     database users than having a developer mark a bug "fixed" without
     any comment as to what the fix was (or even that it was truly
     fixed!)
   12. Set "supportwatchers" to "On". This feature is helpful for team
       leads to monitor progress in their respective areas, and can offer
       many other benefits, such as allowing a developer to pick up a
       former engineer's bugs without requiring her to change all the
       information in the bug.
     _________________________________________________________________

3.2. User Administration

   User administration is one of the easiest parts of Bugzilla. Keeping
   it from getting out of hand, however, can become a challenge.
     _________________________________________________________________

3.2.1. Creating the Default User

   When you first run checksetup.pl after installing Bugzilla, it will
   prompt you for the administrative username (email address) and
   password for this "super user". If for some reason you were to delete
   the "super user" account, re-running checksetup.pl will again prompt
   you for this username and password.

     Tip: If you wish to add more administrative users, you must use the
     MySQL interface. Run "mysql" from the command line, and use these
     commands ("mysql>" denotes the mysql prompt, not something you
     should type in): mysql> use bugs; mysql> update profiles set
     groupset=0x7ffffffffffffff where login_name = "(user's login
     name)";
     _________________________________________________________________

3.2.2. Managing Other Users

3.2.2.1. Logging In

    1. Open the index.html page for your Bugzilla installation in your
       browser window.
    2. Click the "Query Existing Bug Reports" link.
    3. Click the "Log In" link at the foot of the page.
    4. Type your email address, and the password which was emailed to you
       when you created your Bugzilla account, into the spaces provided.

   Congratulations, you are logged in!
     _________________________________________________________________

3.2.2.2. Creating new users

   Your users can create their own user accounts by clicking the "New
   Account" link at the bottom of each page. However, should you desire
   to create user accounts ahead of time, here is how you do it.

    1. After logging in, click the "Users" link at the footer of the
       query page.
    2. To see a specific user, type a portion of their login name in the
       box provided and click "submit". To see all users, simply click
       the "submit" button. You must click "submit" here to be able to
       add a new user.

     Tip: More functionality is available via the list on the right-hand
     side of the text entry box. You can match what you type as a
     case-insensitive substring (the default) of all users on your
     system, a case-sensitive regular expression (please see the "man
     regexp" manual page for details on regular expression syntax), or a
     reverse regular expression match, where every user name which does
     NOT match the regular expression is selected.
    3. Click the "Add New User" link at the bottom of the user list
    4. Fill out the form presented. This page is self-explanatory. When
       done, click "submit".

     Note: Adding a user this way will not send an email informing them
     of their username and password. In general, it is preferable to log
     out and use the "New Account" button to create users, as it will
     pre-populate all the required fields and also notify the user of
     her account name and password.
     _________________________________________________________________

3.2.2.3. Disabling Users

   I bet you noticed that big "Disabled Text" entry box available from
   the "Add New User" screen, when you edit an account? By entering any
   text in this box and selecting "submit", you have prevented the user
   from using Bugzilla via the web interface. Your explanation, written
   in this text box, will be presented to the user the next time she
   attempts to use the system.

   Warning

   Don't disable your own administrative account, or you will hate life!
     _________________________________________________________________

3.2.2.4. Modifying Users

   Here I will attempt to describe the function of each option on the
   user edit screen.

     * Login Name: This is generally the user's email address. However,
       if you have edited your system parameters, this may just be the
       user's login name or some other identifier.

     Tip: For compatability reasons, you should probably stick with
     email addresses as user login names. It will make your life easier.
     * Real Name: Duh!
     * Password: You will only see asterisks in versions of Bugzilla
       newer than 2.10 or early 2.11. You can change the user password
       here.
     * Email Notification: You may choose from one of three options:
         1. All qualifying bugs except those which I change: The user
            will be notified of any change to any bug for which she is
            the reporter, assignee, Q/A contact, CC recipient, or
            "watcher".
         2. Only those bugs which I am listed on the CC line: The user
            will not be notified of changes to bugs where she is the
            assignee, reporter, or Q/A contact, but will receive them if
            she is on the CC list.

     Note: She will still receive whining cron emails if you set up the
     "whinemail" feature.
         3. All Qualifying Bugs: This user is a glutton for punishment.
            If her name is in the reporter, Q/A contact, CC, assignee, or
            is a "watcher", she will get email updates regarding the bug.
       Disable Text: If you type anything in this box, including just a
       space, the user account is disabled from making any changes to
       bugs via the web interface, and what you type in this box is
       presented as the reason.

                       Warning
       Don't disable the administrator account!

     Note: As of this writing, the user can still submit bugs via the
     e-mail gateway, if you set it up, despite the disabled text field.
     The e-mail gateway should not be enabled for secure installations
     of Bugzilla.
     * CanConfirm: This field is only used if you have enabled
       "unconfirmed" status in your parameters screen. If you enable this
       for a user, that user can then move bugs from "Unconfirmed" to
       "Confirmed" status (ergo: "New" status). Be judicious about
       allowing users to turn this bit on for other users.
     * Creategroups: This option will allow a user to create and destroy
       groups in Bugzilla. Unless you are using the Bugzilla GroupSentry
       security option "usebuggroupsentry" in your parameters, this
       setting has no effect.
     * Editbugs: Unless a user has this bit set, they can only edit those
       bugs for which they are the assignee or the reporter.

     Note: Leaving this option unchecked does not prevent users from
     adding comments to a bug! They simply cannot change a bug priority,
     severity, etc. unless they are the assignee or reporter.
     * Editcomponents: This flag allows a user to create new products and
       components, as well as modify and destroy those that have no bugs
       associated with them. If a product or component has bugs
       associated with it, those bugs must be moved to a different
       product or component before Bugzilla will allow them to be
       destroyed. The name of a product or component can be changed
       without affecting the associated bugs, but it tends to annoy the
       hell out of your users when these change a lot.
     * Editkeywords: If you use Bugzilla's keyword functionality,
       enabling this feature allows a user can create and destroy
       keywords. As always, the keywords for existing bugs containing the
       keyword the user wishes to destroy must be changed before Bugzilla
       will allow it to die. You must be very careful about creating too
       many new keywords if you run a very large Bugzilla installation;
       keywords are global variables across products, and you can often
       run into a phenomenon called "keyword bloat". This confuses users,
       and then the feature goes unused.
     * Editusers: This flag allows a user do what you're doing right now:
       edit other users. This will allow those with the right to do so to
       remove administrator priveleges from other users or grant them to
       themselves. Enable with care.
     * PRODUCT: PRODUCT bugs access. This allows an administrator, with
       product-level granularity, to specify in which products a user can
       edit bugs. The user must still have the "editbugs" privelege to
       edit bugs in this area; this simply restricts them from even
       seeing bugs outside these boundaries if the administrator has
       enabled the group sentry parameter "usebuggroupsentry". Unless you
       are using bug groups, this option has no effect.
     _________________________________________________________________

3.3. Product, Component, Milestone, and Version Administration



   Dear Lord, we have to get our users to do WHAT?
     _________________________________________________________________

3.3.1. Products

   Formerly, and in some spots still, called "Programs"

   Products are the broadest category in Bugzilla, and you should have
   the least of these. If your company makes computer games, you should
   have one product per game, and possibly a few special products
   (website, meetings...)

   A Product (formerly called "Program", and still referred to that way
   in some portions of the source code) controls some very important
   functions. The number of "votes" available for users to vote for the
   most important bugs is set per-product, as is the number of votes
   required to move a bug automatically from the UNCONFIRMED status to
   the NEW status. One can close a Product for further bug entry and
   define various Versions available from the Edit Product screen.

   To create a new product:

    1. Select "components" from the yellow footer

     Tip: It may seem counterintuitive to click "components" when you
     want to edit the properties associated with Products. This is one
     of a long list of things we want in Bugzilla 3.0...
    2. Select the "Add" link to the right of "Add a new product".
    3. Enter the name of the product and a description. The Description
       field is free-form.

     Tip: Don't worry about the "Closed for bug entry", "Maximum Votes
     per person", "Maximum votes a person can put on a single bug",
     "Number of votes a bug in this Product needs to automatically get
     out of the UNCOMFIRMED state", and "Version" options yet. We'll
     cover those in a few moments.
     _________________________________________________________________

3.3.2. Components

   Components are subsections of a Product.

   Example 3-1. Creating some Components

   The computer game you are designing may a "UI" component, an "API"
   component, a "Sound System" component, and a "Plugins" component, each
   overseen by a different programmer. It often makes sense to divide
   Components in Bugzilla according to the natural divisions of
   responsibility within your Product or company.

   Each component has a owner and (if you turned it on in the
   parameters), a qa contact. The owner should be the primary person who
   fixes bugs in that component. The QA Contact should be the person who
   will ensure these bugs are completely fixed. The Owner, QA Contact,
   and Reporter will get email when new bugs are created in this
   Component and when these bugs change. Default Owner and Default QA
   Contact fields only dictate the default assignments; the Owner and Q/A
   Contact fields in a bug are otherwise unrelated to the Component.

   To create a new Component:

    1. Select the "Edit components" link from the "Edit Product" page
    2. Select the "Add" link to the right of the "Add a new component"
       text on the "Select Component" page.
    3. Fill out the "Component" field, a short "Description", and the
       "Initial Owner". The "Component" field should not contain a space.
       The "Description" field is free-form. The "Initial Owner" field
       must be that of a valid user already existing in the database. If
       the initial owner does not exist, Bugzilla will refuse to create
       the component.

     Tip: Is your "Default Owner" a user who is not yet in the database?
     No problem.
         a. Select the "Log out" link on the footer of the page.
         b. Select the "New Account" link on the footer of the "Relogin"
            page
         c. Type in the email address of the default owner you want to
            create in the "E-mail address" field, and her full name in
            the "Real name" field, then select the "Submit Query" button.
         d. Now select "Log in" again, type in your login information,
            and you can modify the product to use the Default Owner
            information you require.

    4. Either "edit" more components or return to the "query" page on the
       ensuing "Addming new component" page. To return to the Product you
       were editing, you must select the "components" link as before.
     _________________________________________________________________

3.3.3. Versions

   Versions are the revisions of the product, such as "Flinders 3.1",
   "Flinders 95", and "Flinders 2000". Using Versions helps you isolate
   code changes and are an aid in reporting.

   Example 3-2. Common Use of Versions

   A user reports a bug against Version "Beta 2.0" of your product. The
   current Version of your software is "Release Candidate 1", and no
   longer has the bug. This will help you triage and classify bugs
   according to their relevance. It is also possible people may report
   bugs against bleeding-edge beta versions that are not evident in older
   versions of the software. This can help isolate code changes that
   caused the bug

   Example 3-3. A Different Use of Versions

   This field has been used to good effect by an online service provider
   in a slightly different way. They had three versions of the product:
   "Production", "QA", and "Dev". Although it may be the same product, a
   bug in the development environment is not normally as critical as a
   Production bug, nor does it need to be reported publicly. When used in
   conjunction with Target Milestones, one can easily specify the
   environment where a bug can be reproduced, and the Milestone by which
   it will be fixed.

   To create and edit Versions:

    1. From the "Edit Product" screen, select "Edit Versions"
    2. You will notice that the product already has the default version
       "undefined". If your product doesn't use version numbers, you may
       want to leave this as it is or edit it so that it is "---". You
       can then go back to the edit versions page and add new versions to
       your product.
       Otherwise, click the "Add" button to the right of the "Add a new
       version" text.
    3. Enter the name of the Version. This can be free-form characters up
       to the limit of the text box. Then select the "Add" button.
    4. At this point you can select "Edit" to edit more Versions, or
       return to the "Query" page, from which you can navigate back to
       the product through the "components" link at the foot of the Query
       page.
     _________________________________________________________________

3.3.4. Milestones

   Milestones are "targets" that you plan to get a bug fixed by. For
   example, you have a bug that you plan to fix for your 3.0 release, it
   would be assigned the milestone of 3.0. Or, you have a bug that you
   plan to fix for 2.8, this would have a milestone of 2.8.

     Note: Milestone options will only appear for a Product if you
     turned the "usetargetmilestone" field in the "Edit Parameters"
     screen "On".

   To create new Milestones, set Default Milestones, and set Milestone
   URL:

    1. Select "edit milestones"
    2. Select "Add" to the right of the "Add a new milestone" text
    3. Enter the name of the Milestone in the "Milestone" field. You can
       optionally set the "Sortkey", which is a positive or negative
       number (-255 to 255) that defines where in the list this
       particular milestone appears. Select "Add".
       Example 3-4. Using SortKey with Target Milestone
       Let's say you create a target milestone called "Release 1.0", with
       Sortkey set to "0". Later, you realize that you will have a public
       beta, called "Beta1". You can create a Milestone called "Beta1",
       with a Sortkey of "-1" in order to ensure people will see the
       Target Milestone of "Beta1" earlier on the list than "Release 1.0"
    4. If you want to add more milestones, select the "Edit" link. If you
       don't, well shoot, you have to go back to the "query" page and
       select "components" again, and make your way back to the Product
       you were editing.

     Note: This is another in the list of unusual user interface
     decisions that we'd like to get cleaned up. Shouldn't there be a
     link to the effect of "edit the Product I was editing when I ended
     up here"? In any case, clicking "components" in the footer takes
     you back to the "Select product" screen, from which you can begin
     editing your product again.
    5. From the Edit Product screen again (once you've made your way
       back), enter the URL for a description of what your milestones are
       for this product in the "Milestone URL" field. It should be of the
       format "http://www.foo.com/bugzilla/product_milestones.html"
       Some common uses of this field include product descriptions,
       product roadmaps, and of course a simple description of the
       meaning of each milestone.
    6. If you're using Target Milestones, the "Default Milestone" field
       must have some kind of entry. If you really don't care if people
       set coherent Target Milestones, simply leave this at the default,
       "---". However, controlling and regularly updating the Default
       Milestone field is a powerful tool when reporting the status of
       projects.
       Select the "Update" button when you are done.
    7.
     _________________________________________________________________

3.3.5. Voting

   The concept of "voting" is a poorly understood, yet powerful feature
   for the management of open-source projects. Each user is assigned so
   many Votes per product, which they can freely reassign (or assign
   multiple votes to a single bug). This allows developers to gauge user
   need for a particular enhancement or bugfix. By allowing bugs with a
   certain number of votes to automatically move from "UNCONFIRMED" to
   "NEW", users of the bug system can help high-priority bugs garner
   attention so they don't sit for a long time awaiting triage.

   The daunting challenge of Votes is deciding where you draw the line
   for a "vocal majority". If you only have a user base of 100 users,
   setting a low threshold for bugs to move from UNCONFIRMED to NEW makes
   sense. As the Bugzilla user base expands, however, these thresholds
   must be re-evaluated. You should gauge whether this feature is worth
   the time and close monitoring involved, and perhaps forego
   implementation until you have a critical mass of users who demand it.

   To modify Voting settings:

    1. Navigate to the "Edit Product" screen for the Product you wish to
       modify
    2. Set "Maximum Votes per person" to your calculated value. Setting
       this field to "0" disables voting.
    3. Set "Maximum Votes a person can put on a single bug" to your
       calculated value. It should probably be some number lower than the
       "Maximum votes per person". Setting this field to "0" disables
       voting, but leaves the voting options open to the user. This is
       confusing.
    4. Set "Number of votes a bug in this product needs to automatically
       get out of the UNCONFIRMED state" to your calculated number.
       Setting this field to "0" disables the automatic move of bugs from
       UNCONFIRMED to NEW. Some people advocate leaving this at "0", but
       of what use are Votes if your Bugzilla user base is unable to
       affect which bugs appear on Development radar?

     Tip: You should probably set this number to higher than a small
     coalition of Bugzilla users can influence it. Most sites use this
     as a "referendum" mechanism -- if users are able to vote a bug out
     of UNCONFIRMED, it is a really bad bug!
    5. Once you have adjusted the values to your preference, select the
       "Update" button.
     _________________________________________________________________

3.3.6. Groups and Group Security

   Groups can be very useful in bugzilla, because they allow users to
   isolate bugs or products that should only be seen by certain people.
   Groups can also be a complicated minefield of interdependencies and
   weirdness if mismanaged.

   Example 3-5. When to Use Group Security

   Many Bugzilla sites isolate "Security-related" bugs from all other
   bugs. This way, they can have a fix ready before the security
   vulnerability is announced to the world. You can create a "Security"
   product which, by default, has no members, and only add members to the
   group (in their individual User page, as described under User
   Administration) who should have priveleged access to "Security" bugs.
   Alternately, you may create a Group independently of any Product, and
   change the Group mask on individual bugs to restrict access to members
   only of certain Groups.

   Groups only work if you enable the "usebuggroups" paramater. In
   addition, if the "usebuggroupsentry" parameter is "On", one can
   restrict access to products by groups, so that only members of a
   product group are able to view bugs within that product. Group
   security in Bugzilla can be divided into two categories: Generic and
   Product-Based.

     Note: Groups in Bugzilla are a complicated beast that evolved out
     of very simple user permission bitmasks, apparently itself derived
     from common concepts in UNIX access controls. A "bitmask" is a
     fixed-length number whose value can describe one, and only one, set
     of states. For instance, UNIX file permissions are assigned bitmask
     values: "execute" has a value of 1, "write" has a value of 2, and
     "read" has a value of 4. Add them together, and a file can be read,
     written to, and executed if it has a bitmask of "7". (This is a
     simplified example -- anybody who knows UNIX security knows there
     is much more to it than this. Please bear with me for the purpose
     of this note.) The only way a bitmask scheme can work is by
     doubling the bit count for each value. Thus if UNIX wanted to offer
     another file permission, the next would have to be a value of 8,
     then the next 16, the next 32, etc.

     Similarly, Bugzilla offers a bitmask to define group permissions,
     with an internal limit of 64. Several are already occupied by
     built-in permissions. The way around this limitation is to avoid
     assigning groups to products if you have many products, avoid
     bloating of group lists, and religiously prune irrelevant groups.
     In reality, most installations of Bugzilla support far fewer than
     64 groups, so this limitation has not hit for most sites, but it is
     on the table to be revised for Bugzilla 3.0 because it interferes
     with the security schemes of some administrators.

   To enable Generic Group Security ("usebuggroups"):

    1. Turn "On" "usebuggroups" in the "Edit Parameters" screen.
    2. You will generally have no groups set up. Select the "groups" link
       in the footer.
    3. Take a moment to understand the instructions on the "Edit Groups"
       screen. Once you feel confident you understand what is expected of
       you, select the "Add Group" link.
    4. Fill out the "New Name" (remember, no spaces!), "New Description",
       and "New User RegExp" fields. "New User RegExp" allows you to
       automatically place all users who fulfill the Regular Expression
       into the new group.
       Example 3-6. Creating a New Group
       I created a group called "DefaultGroup" with a description of
       "This is simply a group to play with", and a "New User RegExp" of
       "*@velio.com". This new group automatically includes all Bugzilla
       users with "@velio.com" at the end of their user id. When I
       finished, my new group was assigned bit #128.
       When you have finished, select the "Add" button.

   To enable Product-Based Group Security ("usebuggroupsentry"):

   Warning

   Don't forget that you only have 64 groups masks available, total, for
   your installation of Bugzilla! If you plan on having more than 50
   products in your individual Bugzilla installation, and require group
   security for your products, you should consider either running
   multiple Bugzillas or using Generic Group Security instead of
   Product-Based ("usebuggroupsentry") Group Security.

    1. Turn "On" "usebuggroups" and "usebuggroupsentry" in the "Edit
       Parameters" screen.

       Warning
   "usebuggroupsentry" has the capacity to prevent the administrative
   user from directly altering bugs because of conflicting group
   permissions. If you plan on using "usebuggroupsentry", you should plan
   on restricting administrative account usage to administrative duties
   only. In other words, manage bugs with an unpriveleged user account,
   and manage users, groups, Products, etc. with the administrative
   account.
    2. You will generally have no Groups set up, unless you enabled
       "usebuggroupsentry" prior to creating any Products. To create
       "Generic Group Security" groups, follow the instructions given
       above. To create Product-Based Group security, simply follow the
       instructions for creating a new Product. If you need to add users
       to these new groups as you create them, you will find the option
       to add them to the group available under the "Edit User" screens.
     _________________________________________________________________

3.4. Bugzilla Security



   Putting your money in a wall safe is better protection than depending
   on the fact that no one knows that you hide your money in a mayonnaise
   jar in your fridge.

     Note: Poorly-configured MySQL, Bugzilla, and FTP installations have
     given attackers full access to systems in the past. Please take
     these guidelines seriously, even for Bugzilla machines hidden away
     behind your firewall. 80% of all computer trespassers are insiders,
     not anonymous crackers.

   First thing's first: Secure your installation.

     Note: These instructions must, of necessity, be somewhat vague
     since Bugzilla runs on so many different platforms. If you have
     refinements of these directions for specific platforms, please
     submit them to mozilla-webtools@mozilla.org

    1. Ensure you are running at least MysQL version 3.22.32 or newer.
       Earlier versions had notable security holes and poorly secured
       default configuration choices.
    2. There is no substitute for understanding the tools on your system!
       Read The MySQL Privelege System until you can recite it from
       memory!
       At the very least, ensure you password the "mysql -u root" account
       and the "bugs" account, establish grant table rights (consult the
       Keystone guide in Appendix C: The Bugzilla Database for some
       easy-to-use details) that do not allow CREATE, DROP, RELOAD,
       SHUTDOWN, and PROCESS for user "bugs". I wrote up the Keystone
       advice back when I knew far less about security than I do now : )
    3. Lock down /etc/inetd.conf. Heck, disable inet entirely on this
       box. It should only listen to port 25 for Sendmail and port 80 for
       Apache.
    4. Do not run Apache as "nobody". This will require very lax
       permissions in your Bugzilla directories. Run it, instead, as a
       user with a name, set via your httpd.conf file.
    5. Ensure you have adequate access controls for $BUGZILLA_HOME/data/
       and $BUGZILLA_HOME/localconfig. The localconfig file stores your
       "bugs" user password, which would be terrible to have in the hands
       of a criminal. Also some files under $BUGZILLA_HOME/data store
       sensitive information.
       On Apache, you can use .htaccess files to protect access to these
       directories, as outlined in Bug 57161 for the localconfig file,
       and Bug 65572 for adequate protection in your data/ and shadow/
       directories.
       Note the instructions which follow are Apache-specific. If you use
       IIS, Netscape, or other non-Apache web servers, please consult
       your system documentation for how to secure these files from being
       transmitted to curious users.
       Place the following text into a file named ".htaccess", readable
       by your web server, in your $BUGZILLA_HOME/data directory.
             <Files comments>
             allow from all
             </Files>
             deny from all

       Place the following text into a file named ".htaccess", readable
       by your web server, in your $BUGZILLA_HOME/ directory.
             <Files localconfig>
             deny from all
             </Files>
             allow from all

       Place the following text into a file named ".htaccess", readable
       by your web server, in your $BUGZILLA_HOME/shadow directory.
             deny from all

    6.
     _________________________________________________________________

Chapter 4. Using Bugzilla



   What, Why, How, & What's in it for me?
     _________________________________________________________________

4.1. What is Bugzilla?

   Bugzilla is one example of a class of programs called "Defect Tracking
   Systems", or, more commonly, "Bug-Tracking Systems". Defect Tracking
   Systems allow individual or groups of developers to keep track of
   outstanding bugs in their product effectively. At the time Bugzilla
   was originally written, as a port from Netscape Communications'
   "Bugsplat!" program to Perl from TCL, there were very few competitors
   in the market for bug-tracking software. Most commercial
   defect-tracking software vendors at the time charged enormous
   licensing fees. Bugzilla quickly became a favorite of the open-source
   crowd (with its genesis in the open-source browser project, Mozilla)
   and is now the de-facto standard defect-tracking system against which
   all others are measured.

   Bugzilla has matured immensely, and now boasts many advanced features.
   These include:

     * integrated, product-based granular security schema
     * inter-bug dependencies and dependency graphing
     * advanced reporting capabilities
     * a robust, stable RDBMS back-end
     * extensive configurability
     * a very well-understood and well-thought-out natural bug resolution
       protocol
     * email, XML, and HTTP APIs
     * integration with several automated software configuration
       management systems
     * too many more features to list

   Despite its current robustness and popularity, however, Bugzilla faces
   some near-term challenges, such as reliance on a single database, a
   lack of abstraction of the user interface and program logic, verbose
   email bug notifications, a powerful but daunting query interface,
   little reporting configurability, problems with extremely large
   queries, some unsupportable bug resolution options, no
   internationalization, and dependence on some nonstandard libraries.

   Despite these small problems, Bugzilla is very hard to beat. It is
   under very active development to address the current issues, and a
   long-awaited overhaul in the form of Bugzilla 3.0 is expected sometime
   later this year.
     _________________________________________________________________

4.2. Why Should We Use Bugzilla?



   No, Who's on first...

   For many years, defect-tracking software has remained principally the
   domain of large software development houses. Even then, most shops
   never bothered with bug-tracking software, and instead simply relied
   on shared lists and email to monitor the status of defects. This
   procedure is error-prone and tends to cause those bugs judged least
   significant by developers to be dropped or ignored

   These days, many companies are finding that integrated defect-tracking
   systems reduce downtime, increase productivity, and raise customer
   satisfaction with their systems. Along with full disclosure, an open
   bug-tracker allows manufacturers to keep in touch with their clients
   and resellers, to communicate about problems effectively throughout
   the data management chain. Many corporations have also discovered that
   defect-tracking helps reduce costs by providing IT support
   accountability, telephone support knowledge bases, and a common,
   well-understood system for accounting for unusual system or software
   issues.

   But why should you use Bugzilla?

   Bugzilla is very adaptable to various situations. Known uses currently
   include IT support queues, Systems Administration deployment
   management, chip design and development problem tracking (both
   pre-and-post fabrication), and software bug tracking for luminaries
   such as Redhat, Loki software, Linux-Mandrake, and VA Systems.
   Combined with systems such as CVS, Bonsai, or Perforce SCM, Bugzilla
   provides a powerful, easy-to-use solution to configuration management
   and replication problems

   Bugzilla can dramatically increase the productivity and accountability
   of individual employees by providing a documented workflow and
   positive feedback for good performance. How many times do you wake up
   in the morning, remembering that you were supposed to do *something*
   today, but you just can't quite remember? Put it in Bugzilla, and you
   have a record of it from which you can extrapolate milestones, predict
   product versions for integration, and by using Bugzilla's e-mail
   integration features be able to follow the discussion trail that led
   to critical decisions.

   Ultimately, Bugzilla puts the power in your hands to improve your
   value to your employer or business while providing a usable framework
   for your natural attention to detail and knowledge store to flourish.
     _________________________________________________________________

4.3. How do I use Bugzilla?



   Hey! I'm Woody! Howdy, Howdy, Howdy!

   Bugzilla is a large and complex system. Describing how to use it
   requires some time. If you are only interested in installing or
   administering a Bugzilla installation, please consult the Installing
   and Administering Bugzilla portions of this Guide. This section is
   principally aimed towards developing end-user mastery of Bugzilla, so
   you may fully enjoy the benefits afforded by using this reliable
   open-source bug-tracking software.

   Throughout this portion of the Guide, we will refer to user account
   options available at the Bugzilla test installation,
   landfill.tequilarista.org. Although Landfill serves as a great
   introduction to Bugzilla, it does not offer all the options you would
   have as a user on your own installation of Bugzilla, nor can it do
   more than serve as a general introduction to Bugzilla. However, please
   use it if you want to follow this tutorial.
     _________________________________________________________________

4.3.1. Create a Bugzilla Account

   First thing's first! If you want to use Bugzilla, first you need to
   create an account. Consult with the administrator responsible for your
   installation of Bugzilla for the URL you should use to access it. If
   you're test-driving the end-user Bugzilla experience, use this URL:
   http://landfill.tequilarista.org/mozilla/bugzilla/

    1. Click the "Open a new Bugzilla account" link.
    2. Enter your "E-mail address" and "Real Name" (or whatever name you
       want to call yourself) in the spaces provided, then select the
       "Create Account" button.
    3. Within 5-10 minutes, you should receive an email to the address
       you provided above, which contains your login name (generally the
       same as the email address), and a password you can use to access
       your account. This password is randomly generated, and should be
       changed at your nearest opportunity (we'll go into how to do it
       later).
    4. Click the "Log In" link in the yellow area at the bottom of the
       page in your browser, then enter your "E-mail address" and
       "Password" you just received into the spaces provided, and select
       "Login".

     Note: If you ever forget your password, you can come back to this
     page, enter your "E-mail address", then select the "E-mail me a
     password" button to have your password mailed to you again so that
     you can login.

       Caution
   Many modern browsers include an "Auto-Complete" or "Form Fill" feature
   to remember the user names and passwords you type in at many sites.
   Unfortunately, sometimes they attempt to "guess" what you will put in
   as your password, and guess wrong. If you notice a text box is already
   filled out, please overwrite the contents of the text box so you can
   be sure to input the correct information.

   Congratulations! If you followed these directions, you now are the
   proud owner of a user account on landfill.tequilarista.org (Landfill)
   or your local Bugzilla install. You should now see in your browser a
   page called the "Bugzilla Query Page". It may look daunting, but with
   this Guide to walk you through it, you will master it in no time.
     _________________________________________________________________

4.3.2. The Bugzilla Query Page

   The Bugzilla Query Page is the heart and soul of Bugzilla. It is the
   master interface where you can find any bug report, comment, or patch
   currently in the Bugzilla system. We'll go into how to create your own
   bug report later on.

   There are efforts underway to simplify query usage. If you have a
   local installation of Bugzilla 2.12 or higher, you should have
   "quicksearch.html" available to use and simplify your searches. There
   is also, or shortly will be, a helper for the query interface, called
   "queryhelp.cgi". Landfill tends to run the latest code, so these two
   utilities should be available there for your perusal.

   At this point, please visit the main Bugzilla site,
   bugzilla.mozilla.org, to see a more fleshed-out query page.

   The first thing you need to notice about the Bugzilla Query Page is
   that nearly every box you see on your screen has a hyperlink nearby,
   explaining what it is or what it does. Near the upper-left-hand corner
   of your browser window you should see the word "Status" underlined.
   Select it.

   Notice the page that popped up? Every underlined word you see on your
   screen is a hyperlink that will take you to context-sensitive help.
   Click around for a while, and learn what everything here does. To
   return to the query interface after pulling up a help page, use the
   "Back" button in your browser.

   I'm sure that after checking out the online help, you are now an
   Expert on the Bugzilla Query Page. If, however, you feel you haven't
   mastered it yet, let me walk you through making a few successful
   queries to find out what there are in the Bugzilla bug-tracking system
   itself.

    1. Ensure you are back on the "Bugzilla Query Page" Do nothing in the
       boxes marked "Status", "Resolution", "Platform", "OpSys",
       "Priority", or "Severity". The default query for "Status" is to
       find all bugs that are NEW, ASSIGNED, or REOPENED, which is what
       we want. If you don't select anything in the other 5 scrollboxes
       there, then you are saying that "any of these are OK"; we're not
       locking ourselves into only finding bugs on the "DEC" Platform, or
       "Windows 95" OpSys (Operating System). You're smart, I think you
       have it figured out.
       Basically, selecting anything on the query page narrows your
       search down. Leaving stuff unselected, or text boxes unfilled,
       broadens your search!
    2. You see the box immediately below the top six boxes that contains
       an "Email" text box, with the words "matching as", a drop-down
       selection box, then some checkboxes with "Assigned To" checked by
       default? This allows you to filter your search down based upon
       email address. Let's put my email address in there, and see what
       happens.
       Type "barnboy@trilobyte.net" in the top Email text box.
    3. Let's narrow the search some more. Scroll down until you find the
       box with the word "Program" over the top of it. This is where we
       can narrow our search down to only specific products (software
       programs or product lines) in our Bugzilla database. Please notice
       the box is a scrollbox. Using the down arrow on the scrollbox,
       scroll down until you can see an entry called "Webtools". Select
       this entry.
    4. Did you notice that some of the boxes to the right changed when
       you selected "Webtools"? Every Program (or Product) has different
       Versions, Components, and Target Milestones associated with it. A
       "Version" is the number of a software program.
       Example 4-1. Some Famous Software Versions
       Do you remember the hype in 1995 when Microsoft Windows 95(r) was
       released? It may have been several years ago, but Microsoft(tm)
       spent over $300 Million advertising this new Version of their
       software. Three years later, they released Microsoft Windows
       98(r), another new version, to great fanfare, and then in 2000
       quietly released Microsoft Windows ME(Millenium Edition)(r).
       Software "Versions" help a manufacturer differentiate their
       current product from their previous products. Most do not identify
       their products by the year they were released. Instead, the
       "original" version of their software will often be numbered "1.0",
       with small bug-fix releases on subsequent tenths of a digit. In
       most cases, it's not a decimal number; for instance, often 1.9 is
       an older version of the software than 1.11, but is a newer version
       than 1.1.1.
       In general, a "Version" in Bugzilla should refer to released
       products, not products that have not yet been released to the
       public. Forthcoming products are what the Target Milestone field
       is for.
       A "Component" is a piece of a Product. It may be a standalone
       program, or some other logical division of a Product or Program.
       Normally, a Component has a single Owner, who is responsible for
       overseeing efforts to improve that Component.
       Example 4-2. Mozilla Webtools Components
       Mozilla's "Webtools" Product is composed of several pieces
       (Components):

       Bonsai, a tool to show recent changes to Mozilla
       Bugzilla, a defect-tracking tool
   Build, a tool to automatically compile source code into
   machine-readable form
       Despot, a program that controls access to the other Webtools
   LXR, a utility that automatically marks up text files to make them
   more readable
       MozBot, a "robot" that announces changes to Mozilla in Chat
       TestManager, a tool to help find bugs in Mozilla
       Tinderbox, which displays reports from Build
       A different person is responsible for each of these Components.
       Tara Hernandez keeps the "Bugzilla" component up-to-date.
       A "Milestone", or "Target Milestone" is a often a planned future
       "Version" of a product. In many cases, though, Milestones simply
       represent significant dates for a developer. Having certain
       features in your Product is frequently tied to revenue (money) the
       developer will receive if the features work by the time she
       reaches the Target Milestone. Target Milestones are a great tool
       to organize your time. If someone will pay you $100,000 for
       incorporating certain features by a certain date, those features
       by that Milestone date become a very high priority. Milestones
       tend to be highly malleable creatures, though, that appear to be
       in reach but are out of reach by the time the important day
       arrives.
       The Bugzilla Project has set up Milestones for future Bugzilla
       versions 2.14, 2.16, 2.18, 3.0, etc. However, a Target Milestone
       can just as easily be a specific date, code name, or weird
       alphanumeric combination, like "M19".
    5. OK, now let's select the "Bugzilla" component from its scrollbox.
    6. Skip down the page a bit -- do you see the "submit query" button?
       Select it, and let's run this query!
    7. Congratulations! You've completed your first Query, and have
       before you the Bug List of the author of this Guide, Matthew P.
       Barnson (barnboy@trilobyte.net). If I'm doing well, you'll have a
       cryptic "Zarro Boogs Found" message on your screen. It is just a
       happy hacker's way of saying "Zero Bugs Found". However, I am
       fairly certain I will always have some bugs assigned to me that
       aren't done yet, so you won't often see that message!

   I encourage you to click the bug numbers in the left-hand column and
   examine my bugs. Also notice that if you click the underlined links
   near the top of this page, they do not take you to context-sensitive
   help here, but instead sort the columns of bugs on the screen! When
   you need to sort your bugs by priority, severity, or the people they
   are assigned to, this is a tremendous timesaver.

   A couple more interesting things about the Bug List page:

   Change Columns: by selecting this link, you can show all kinds of
   information in the Bug List
   Change several bugs at once: If you have sufficient rights to change
   all the bugs shown in the Bug List, you can mass-modify them. This is
   a big time-saver.
   Send mail to bug owners: If you have many related bugs, you can
   request an update from every person who owns the bugs in the Bug List
   asking them the status.
   Edit this query: If you didn't get exactly the results you were
   looking for, you can return to the Query page through this link and
   make small revisions to the query you just made so you get more
   accurate results.

     Note: There are many more options to the Bugzilla Query Page and
     the Bug List than I have shown you. But this should be enough for
     you to learn to get around. I encourage you to check out the
     Bugzilla Home Page to learn about the Anatomy and Life Cycle of a
     Bug before continuing.
     _________________________________________________________________

4.3.3. Creating and Managing Bug Reports



   And all this time, I thought we were taking bugs out...
     _________________________________________________________________

4.3.3.1. Writing a Great Bug Report

   Before we plunge into writing your first bug report, I encourage you
   to read Mozilla.org's Bug Writing Guidelines. While some of the advice
   is Mozilla-specific, the basic principles of reporting Reproducible,
   Specific bugs, isolating the Product you are using, the Version of the
   Product, the Component which failed, the Hardware Platform, and
   Operating System you were using at the time of the failure go a long
   way toward ensuring accurate, responsible fixes for the bug that bit
   you.

   While you are at it, why not learn how to find previously reported
   bugs? Mozilla.org has published a great tutorial on finding duplicate
   bugs, available at
   http://www.mozilla.org/quality/help/beginning-duplicate-finding.html.

   I realize this was a lot to read. However, understanding the mentality
   of writing great bug reports will help us on the next part!

    1. Go back to http://landfill.tequilarista.org/mozilla/bugzilla/ in
       your browser.
    2. Select the Enter a new bug report link.
    3. Select a product.
    4. Now you should be at the "Enter Bug" form. The "reporter" should
       have been automatically filled out for you (or else Bugzilla
       prompted you to Log In again -- you did keep the email with your
       username and password, didn't you?).
    5. Select a Component in the scrollbox.
    6. Bugzilla should have made reasonable guesses, based upon your
       browser, for the "Platform" and "OS" drop-down boxes. If those are
       wrong, change them -- if you're on an SGI box running IRIX, we
       want to know!
    7. Fill in the "Assigned To" box with the email address you provided
       earlier. This way you don't end up sending copies of your bug to
       lots of other people, since it's just a test bug.
    8. Leave the "CC" text box blank. Fill in the "URL" box with
       "http://www.mozilla.org".
    9. Enter "The Bugzilla Guide" in the Summary text box, and place any
       comments you have on this tutorial, or the Guide in general, into
       the Description box.

   Voila! Select "Commit" and send in your bug report! Next we'll look at
   resolving bugs.
     _________________________________________________________________

4.3.3.2. Managing your Bug Reports

   OK, you should have a link to the bug you just created near the top of
   your page. It should say "Bug XXXX posted", with a link to the right
   saying "Back to BUG# XXXX". Select this link.

    1. Scroll down a bit on the subsequent page, until you see the
       "Resolve bug, changing resolution to (dropdown box). Normally, you
       would "Accept bug (change status to ASSIGNED)", fix it, and then
       resolve. But in this case, we're going to short-circuit the
       process because this wasn't a real bug. Change the dropdown next
       to "Resolve Bug" to "INVALID", make sure the radio button is
       marked next to "Resolve Bug", then click "Commit".
    2. Hey! It said it couldn't take the change in a big red box! That's
       right, you must specify a Comment in order to make this change.
       Select the "Back" button in your browser, add a Comment, then try
       Resolving the bug with INVALID status again. This time it should
       work.

   You have now learned the basics of Bugzilla navigation, entering a
   bug, and bug maintenance. I encourage you to explore these features,
   and see what you can do with them! We'll spend no more time on
   individual Bugs or Queries from this point on, so you are on your own
   there.

   But I'll give a few last hints!

   There is a CLUE on the Query page that will teach you more how to use
   the form.

   If you click the hyperlink on the Component box of the Query page, you
   will be presented a form that will describe what all the components
   are.

   Possibly the most powerful feature of the Query page is the Boolean
   Chart section. It's a bit confusing to use the first time, but can
   provide unparalleled flexibility in your queries, allowing you to
   build extremely powerful requests.

   Finally, you can build some nifty Reports using the "Bug Reports" link
   near the bottom of the query page, and also available via the
   "Reports" link at the footer of each page.
     _________________________________________________________________

4.4. What's in it for me?



   Indiana, it feels like we walking on fortune cookies!

   These ain't fortune cookies, kid...

   Customized User Preferences offer tremendous versatility to your
   individual Bugzilla experience. Let's plunge into what you can do! The
   first step is to click the "Edit prefs" link at the footer of each
   page once you have logged in to Landfill.
     _________________________________________________________________

4.4.1. Account Settings

   On this page, you can change your basic Account Settings, including
   your password and full name. For security reasons, in order to change
   anything on this page you must type your current password into the
   "Old Password" field. If you wish to change your password, type the
   new password you want into the "New Password" field and again into the
   "Re-enter new password" field to ensure you typed your new password
   correctly. Select the "Submit" button and you're done!
     _________________________________________________________________

4.4.2. Email Settings

4.4.2.1. Email Notification

   Ahh, here you can reduce or increase the amount of email sent you from
   Bugzilla! In the drop-down "Notify me of changes to", select one of

   All qualifying bugs: sends you every change to every bug where your
   name is somewhere on it, regardless of who changed it.
   Only those bugs which I am listed in the CC line: prevents you from
   receiving mail for which you are the reporter,' owner, or QA contact.
   If you are on the CC list, presumably someone had a good reason for
   you to get the email.
   All qulifying bugs except those which I change: This is the default,
   and a sensible setting. If someone else changes your bugs, you will
   get emailed, but if you change bugs yourself you will receive no
   notification of the change.
     _________________________________________________________________

4.4.2.2. New Email Technology

     Note: This option may not be available in all Bugzilla
     installations, depending upon the preferences of the systems
     administrator responsible for the setup of your Bugzilla. However,
     if you really want this functionality, ask her to "enable
     newemailtech in Params" and "make it the default for all new
     users", referring her to the Administration section of this Guide.

   Disregard the warnings about "experimental and bleeding edge"; the
   code to handle email in a cleaner manner than that historically used
   for Bugzilla is quite robust and well-tested now.

   I recommend you enable the option, "Click here to sign up (and risk
   any bugs)". Your email-box will thank you for it. The fundamental
   shift in "newemailtech" is away from standard UNIX "diff" output,
   which is quite ugly, to a prettier, better laid-out email.
     _________________________________________________________________

4.4.2.3. "Watching" Users

     Note: This option may not be available in all Bugzilla
     installations, depending upon the preferences of the systems
     administrator responsible for the setup of your Bugzilla. However,
     if you really want this functionality, ask her to "enable watchers
     in Params".

   By entering user email names into the "Users to watch" text entry box,
   delineated by commas, you can watch bugs of other users. This powerful
   functionality enables seamless transitions as developers change
   projects, managers wish to get in touch with the issues faced by their
   direct reports, or users go on vacation. If any of these three
   situations apply to you, you will undoubtedly find this feature quite
   convenient.
     _________________________________________________________________

4.4.3. Page Footer

     Note: By default, this page is quite barren. However, go explore
     the Query Page some more; you will find that you can store numerous
     queries on the server, so if you regularly run a particular query
     it is just a drop-down menu away. On this page of Preferences, if
     you have many stored queries you can elect to have them always
     one-click away!

   If you have many stored queries on the server, here you will find
   individual drop-downs for each stored query. Each drop-down gives you
   the option of that query appearing on the footer of every page in
   Bugzilla! This gives you powerful one-click access to any complex
   searches you may set up, and is an excellent way to impress your
   boss...

     Tip: By default, the "My Bugs" link appears at the bottom of each
     page. However, this query gives you both the bugs you have
     reported, as well as those you are assigned. One of the most common
     uses for this page is to remove the "My Bugs" link, replacing it
     with two other queries, commonly called "My Bug Reports" and "My
     Bugs" (but only referencing bugs assigned to you). This allows you
     to distinguish those bugs you have reported from those you are
     assigned. I commonly set up complex Boolean queries in the Query
     page and link them to my footer in this page. When they are
     significantly complex, a one-click reference can save hours of
     work.
     _________________________________________________________________

4.4.4. Permissions

   This is a purely informative page which outlines your current
   permissions on this installation of Bugzilla. If you have permissions
   to grant certain permissions to other users, the "other users" link
   appears on this page as well as the footer. For more information
   regarding user administration, please consult the Administration
   section of this Guide.
     _________________________________________________________________

4.5. Using Bugzilla-Conclusion

   Thank you for reading through this portion of the Bugzilla Guide. I
   anticipate it may not yet meet the needs of all readers. If you have
   additional comments or corrections to make, please submit your
   contributions to the mozilla-webtools mailing list/newsgroup. The
   mailing list is mirrored to the netscape.public.mozilla.webtools
   newsgroup, and the newsgroup is mirrored to
   mozilla-webtools@mozilla.org
     _________________________________________________________________

Chapter 5. Integrating Bugzilla with Third-Party Tools

5.1. Bonsai

   We need Bonsai integration information.
     _________________________________________________________________

5.2. CVS

   We need CVS integration information
     _________________________________________________________________

5.3. Perforce SCM

   Richard Brooksby and his team have an integration tool in public beta.
   You can find it at http://www.ravenbrook.com/project/p4dti.
     _________________________________________________________________

5.4. Tinderbox

   We need Tinderbox integration information
     _________________________________________________________________

Chapter 6. The Future of Bugzilla

   This section largely contributed by Matthew Tuck
     _________________________________________________________________

6.1. Reducing Spam

   Those who use Bugzilla frequently are probably used to notification sp
   am
   - unwanted or unnecessary notifications.  A number of proposals have
   been put forward to attempt to reduce this.
   1. Reduce CC Spam
   Some of you probably know me as that guy who CCs on heaps and heaps of
   bugs.  Just as you get a lot of CC changes from me, so do I get a lot
   from others.  Why should CC changes send out email notifications?
   It's not necessarily the best idea to just remove the CC spam, there a
   re
   other issues too, like the difficulty of adding to large CC fields.
   For these reasons and more, an RFE for a per user "BCC" facility exist
   s
   that people could use to silently and privately track bugs, in a simil
   ar
   way to voting today, but applying to an unlimited number of bugs.  See
   "http://bugzilla.mozilla.org/show_bug.cgi?id=7345".
   2. Bulk Changes
   You know the drill - a large milestone change, a component movement,
   whatever, and lots of notifications are generated.  If there's enough
   maybe you'll just go delete, delete, delete, whoops, there goes anothe
   r
   notification that wasn't from the bulk change you missed.
   Shouldn't bulk changes send out one notification?  A proposal for this
   is at "http://bugzilla.mozilla.org/show_bug.cgi?id=26943".
   3. Configurable Notification Criteria
   It would be good if you could choose what you want to receive.  There
   are two parts to this.
   (a) Choose a selection of bugs you're interested in.  This would be
   similar to CC except you let the set be computed from selection criter
   ia
   rather than limited to the bugs your name is on.  There is currently a
   limited version of this in the bugzilla preferences, ie "all qualifyin
   g
   bugs"/"all qualifying bugs except the ones I change"/"only those bugs
   which I am listed on the cc line".
   (b) Choose what changes will trigger a notification for the bugs you a
   re
   watching.  With this, you could choose whether you want to receive cc,
   dependency and keyword changes, for example.
   Both of these proposals live at
   "http://bugzilla.mozilla.org/show_bug.cgi?id=14137".
     _________________________________________________________________

6.2. Better Searching

   Current searching tools in Bugzilla include the querying mechanism,
   special summary reports and dependency trees.  This message is about n
   ew
   facilities.
   1. General Summary Reports
   For some time now it has been apparent to me that the query bug list
   leaves a little to be desired in its linear nature.  There is a need t
   o
   have categorised subsets, and counts of each category.  If you don't
   believe me, how about these facilities already in place or which peopl
   e
   have asked for:
   Most Doomed Reports - Categorised On Assignee, Shows and Counts Number
   of Bugs For Each Assignee
   Bug #15806 (Most Voted For Bugs) - Categorised On Product, Shows Bugs
   Voters Most Want Fixed
   Bug #9789 (BugAThon Tracking Page) - Categorised On Developer (Subset)
   ,
   Counts Number of Bugs
   Bug #9409 and #9411 - The desire to be able to report on more subsets.
   Hopefully you can see the gist of what is desired here.  It's a genera
   l
   reporting mechanism.
   This mechanism lets you choose the subset of bugs to operate on (like
   query), let's you categorise them, possibly along with subcategories a
   nd
   counts the number of bugs within each category.  It might or might not
   show the actual bugs themselves, and it might limit the number of bugs
   within a category, or categories to report on.
   I'm further sure that many applications of this mechanism would only b
   e
   recognised once it was implemented.
   The general summary reports bug is at
   "http://bugzilla.mozilla.org/show_bug.cgi?id=12282".
   2. Related Bugs
   It would be nice to have a field where you could enter other bugs
   related to the current bug - it would be handy for navigation and
   possibly even finding duplicates.  See
   "http://bugzilla.mozilla.org/show_bug.cgi?id=12286".
   3. Column Specification Support
   Currently query seems to get what columns to report on from whatever t
   he
   user last used.  This doesn't work well for "prepackaged queries", whe
   re
   you followed a link.  You can probably add a column by specifying a so
   rt
   column, but this is difficult and suboptimal.
   Furthermore, I find that when I want to add a column to a query, it's
   usually a one off and I would prefer it to go away for the next query.

   Hence, it would be nice to specify the columns that appear on the quer
   y
   (and general summary report) pages.  The default query mechanism shoul
   d
   be able to let you specify your default columns.
   This proposal lives at
   "http://bugzilla.mozilla.org/show_bug.cgi?id=12284".
     _________________________________________________________________

6.3. Description Flags and Tracking Bugs

   Since I last posted on this issue, we now have "keywords" that solve
   many of the issues of description and status whiteboard keywords.  We
   have seen a migration towards keywords, but there is still further to
   go.
   Description ( + Status Whiteboard ) Keywords
   --------------------------------------------
   Some description keywords remain.  I'd like to hear what reasons, othe
   r
   than time, there are for these staying as they are.  I'm suspecting ma
   ny
   are not really being used.  Hopefully we can totally remove these
   eventually.
   Tracking Bugs
   -------------
   When I suggested keywords, I did so to get rid of tracking bugs too,
   though we've had less success on that front.
   There are many disadvantages to tracking bugs.
   - They can pollute bugs counts, and you must make sure you exclude
   them.  I believe the meta keyword might be used for this purpose.
   - They have an assignee but there is nothing to fix, and that person c
   an
   get whined at by Bugzilla.
   - It would be better to craft your own "dependency tree" rather than
   rely on a fixed hierachy in the bug system.
   - In creating a nice little hierachy, many bugs duplicate information
   that should be available in other ways, eg
   "http://bugzilla.mozilla.org/show_bug.cgi?id=12833" which is
   about beta 1 networking issues.  These could fall behind the actual
   data.  What tracking bugs are good for, ad hoc lists, is what keywords
   are better for.
   - An automatically generated dependency structure between one "trackin
   g
   bug" and another would be better than a manual one, since it gives exa
   ct
   rather than manually set up classifications.
   Probably the only feature preventing tracking bugs being replaced is t
   he
   dependency tree.  The quintessential tracking bug seems to be bug #722
   9
   "chofmann's watch list", which probably has about a couple of hundred
   bugs at various levels, which allows a nice visualisation.
   Before keywords can replace tracking bugs better visualisation is goin
   g
   to be required.  General summary reports and dependency forests of a b
   ug
   list ("http://bugzilla.mozilla.org/show_bug.cgi?id=12992") could both
   help, but neither solves the problem totally.  Perhaps keywords within
   keywords would help here.  In any case, I'm still thinking about this
   one.
   Some tracking bugs could definitely be turned into keywords immediatel
   y
   though, and I'll point the finger at
   "http://bugzilla.mozilla.org/show_bug.cgi?id=7954" here since that's
   what came to mind first.
     _________________________________________________________________

6.4. Bug Issues

   1. Inline Bug Changes
   Why do I see so many "moving to M5" and "reassigning to blahblah"
   messages, and in other circumstances none are entered?  Why aren't the
   se
   automatically generated?  A comment should be only necessary when ther
   e
   is something to add, and if I'm not interested in this sort of
   information, I should be able to hide it.
   At the moment we're in a hybrid world where we don't get everything, b
   ut
   we can't get rid of the bug change "messages" either.  Furthermore,
   "View Bug Activity" requires me to manually cross reference events on
   another page, rather than being able to visually see the chronological
   order.  Shouldn't I be able to see all the information on one page?
   A proposal to allow bugs to be shown either way is at
   "http://bugzilla.mozilla.org/show_bug.cgi?id=11368".
   2.  Hard Wrapping Comments
   One thing that annoys me is the fact that comments are "hard wrapped"
   to
   a certain column width.  This is a mistake Internet Mail and News has
   made, unlike every word processor in existence, and as a consequence,
   Usenet suffers to this day from bad software.  Why has Bugzilla repeat
   ed
   the problem?
   Hard wrapping to a certain column width is open to abuse (see old
   Mozilla browsers that didn't wrap properly, resulting in many ugly bug
   reports we have to read to this day), and furthermore doesn't expand t
   o
   fill greater screen sizes.  I'm also under the impression the current
   hard wrap uses a non-standard HTML facility.  See
   "http://bugzilla.mozilla.org/show_bug.cgi?id=11901".
   3. REMIND and LATER Are Evil
   I really hate REMIND and LATER.  Not because they mean something
   won't be implemented, but because they aren't the best solutions.
   Why are they bad?  Well, basically because they are not resolved, yet
   they are marked as such.  Hence queries have to be well crafted to
   include them.
   LATER, according to Bugzilla, means it won't be done this release.
   There is a better mechanism of doing this, that is assigning to
   nobody@mozilla.org and making the milestone blank.  It's more likely t
   o
   appear in a casual query, and it doesn't resolve the bug.
   REMIND, according to Bugzilla, means it might still be implemented thi
   s
   release.  Well, why not just move it to a later milestone then?  You'r
   e
   a lot less likely to forget it.  If it's really needed, a keyword woul
   d
   be better.
   Some people can't use blank milestones to mean an untargetted mileston
   e,
   since they use this to assess new bugs that have no target.  Hence, it
   would be nice to distinguish between bugs that have not yet been
   considered, and those that really are not assigned to any milestone in
   the future (assumedly beyond).
   All this is covered at
   "http://bugzilla.mozilla.org/show_bug.cgi?id=13534".
   4. Create An Enhancement Field
   Currently enhancement is an option in severity.  This means that
   important enhancements (like for example, POP3 support) are not proper
   ly
   distinguished as such, because they need a proper severity.  This
   dilutes the meaning of enhancement.
   If enhancement was separated, we could properly see what was an
   enhancement.  See "http://bugzilla.mozilla.org/show_bug.cgi?id=9412".
    I
   see keywords like [RFE] and [FEATURE] that seem to be compensating for
   this problem.
     _________________________________________________________________

6.5. Database Integrity

   Bugzilla could be more proactive in detecting suboptimal situations an
   d
   prevent them or whine about them.
   1. Bugzilla Crime #1: Marking A Bug Fixed With Unresolved Dependencies
   It can't be marked fixed with unresolved dependencies.  Either mark it
   INVALID (tracking bugs), fix the dependencies at the same time, or
   resolve the blockers.
   See "http://bugzilla.mozilla.org/show_bug.cgi?id=24496".
   2. Keyword Restrictions
   Some keywords should only apply in certain circumstances, eg beta1 =>
   Milestone <
   M14, css1 => Component = Style System are possibilities.  See
   "http://bugzilla.mozilla.org/show_bug.cgi?id=26940".
   3. Whine About Old Votes
   Old votes can just sit on resolved bugs.  This is problematic with
   duplicates especially.  Automatic transferral/removal is not
   appropriate since bugs can be reopened, but a whining solution might
   work.  See "http://bugzilla.mozilla.org/show_bug.cgi?id=27553".
   4. Whine And Warn About Milestone Mismatches
   Here's a fun one.  Bug X (M17) depends on Bug Y (M15).  Bug Y gets mov
   ed
   out to M19.  The notification to the assignee of Bug X gets ignored (o
   f
   course) and Bug X is now due to be fixed before one of its blockers.
   Warnings about this when it is detected as well as whining about it in
   email would help bring these issues to the attention of people sooner.
   Note that this would be less of a problem if we didn't have so many
   tracking bugs since they aren't updated that often and often have this
   problem.
   See "http://bugzilla.mozilla.org/show_bug.cgi?id=16743".
     _________________________________________________________________

6.6. Bugzilla 3.0

   One day, Bugzilla 3.0 will have lots of cool stuff.
     _________________________________________________________________

Appendix A. The Bugzilla FAQ

   1. General Questions

        A.1.1. Where can I find information about Bugzilla?
        A.1.2. What license is Bugzilla distributed under?
        A.1.3. How do I get commercial support for Bugzilla?
        A.1.4. What major companies or projects are currently using
                Bugzilla for bug-tracking?

        A.1.5. Who maintains Bugzilla?
        A.1.6. How does Bugzilla stack up against other bug-tracking
                databases?

        A.1.7. How do I change my user name in Bugzilla?
        A.1.8. Why doesn't Bugzilla offer this or that feature or
                compatability with this other tracking software?

        A.1.9. Why MySQL? I'm interested in seeing Bugzilla run on
                Oracle/Sybase/Msql/PostgreSQL/MSSQL?

        A.1.10. Why do the scripts say "/usr/bonsaitools/bin/perl"
                instead of "/usr/bin/perl" or something else?

   2. Red Hat Bugzilla

        A.2.1. What about Red Hat Bugzilla?
        A.2.2. What are the primary benefits of Red Hat Bugzilla?
        A.2.3. What's the current status of Red Hat Bugzilla?

   3. Loki Bugzilla (AKA Fenris)

        A.3.1. What about Loki Bugzilla?
        A.3.2. Who maintains Fenris (Loki Bugzilla) now?
        A.3.3.

   4. Pointy-Haired-Boss Questions

        A.4.1. Is Bugzilla web-based or do you have to have specific
                software or specific operating system on your machine?

        A.4.2. Has anyone you know of already done any Bugzilla
                integration with Perforce (SCM software)?

        A.4.3. Does Bugzilla allow the user to track multiple projects?
        A.4.4. If I am on many projects, and search for all bugs assigned
                to me, will Bugzilla list them for me and allow me to
                sort by project, severity etc?

        A.4.5. Does Bugzilla allow attachments (text, screenshots, urls
                etc)? If yes, are there any that are NOT allowed?

        A.4.6. Does Bugzilla allow us to define our own priorities and
                levels? Do we have complete freedom to change the labels
                of fields and format of them, and the choice of
                acceptable values?

        A.4.7. Does Bugzilla provide any reporting features, metrics,
                graphs, etc? You know, the type of stuff that management
                likes to see. :)

        A.4.8. Is there email notification and if so, what do you see
                when you get an email? Do you see bug number and title or
                is it only the number?

        A.4.9. Can email notification be set up to send to multiple
                people, some on the To List, CC List, BCC List etc?

        A.4.10. If there is email notification, do users have to have any
                particular type of email application?

        A.4.11. If I just wanted to track certain bugs, as they go
                through life, can I set it up to alert me via email
                whenever that bug changes, whether it be owner, status or
                description etc.?

        A.4.12. Does Bugzilla allow data to be imported and exported? If
                I had outsiders write up a bug report using a MS Word bug
                template, could that template be imported into "matching"
                fields? If I wanted to take the results of a query and
                export that data to MS Excel, could I do that?

        A.4.13. Does Bugzilla allow fields to be added, changed or
                deleted? If I want to customize the bug submission form
                to meet our needs, can I do that using our terminology?

        A.4.14. Has anyone converted Bugzilla to another language to be
                used in other countries? Is it localizable?

        A.4.15. Can a user create and save reports? Can they do this in
                Word format? Excel format?

        A.4.16. Can a user re-run a report with a new project, same
                query?

        A.4.17. Can a user modify an existing report and then save it
                into another name?

        A.4.18. Does Bugzilla have the ability to search by word, phrase,
                compound search?

        A.4.19. Can the admin person establish separate group and
                individual user privileges?

        A.4.20. Does Bugzilla provide record locking when there is
                simultaneous access to the same bug? Does the second
                person get a notice that the bug is in use or how are
                they notified?

        A.4.21. Are there any backup features provided?
        A.4.22. Can users be on the system while a backup is in progress?

        A.4.23. What type of human resources are needed to be on staff to
                install and maintain Bugzilla? Specifically, what type of
                skills does the person need to have? I need to find out
                if we were to go with Bugzilla, what types of individuals
                would we need to hire and how much would that cost vs
                buying an "Out-of-the-Box" solution.

        A.4.24. What time frame are we looking at if we decide to hire
                people to install and maintain the Bugzilla? Is this
                something that takes hours or weeks to install and a
                couple of hours per week to maintain and customize or is
                this a multi-week install process, plus a full time job
                for 1 person, 2 people, etc?

        A.4.25. Is there any licensing fee or other fees for using
                Bugzilla? Any out-of-pocket cost other than the bodies
                needed as identified above?

   5. Bugzilla Installation

        A.5.1. How do I download and install Bugzilla?
        A.5.2. How do I install Bugzilla on Windows NT?
        A.5.3. Is there an easy way to change the Bugzilla cookie name?

   6. Bugzilla Security

        A.6.1. How do I completely disable MySQL security if it's giving
                me problems (I've followed the instructions in the
                README!)?

        A.6.2. Are there any security problems with Bugzilla?
        A.6.3. I've implemented the security fixes mentioned in Chris
                Yeh's security advisory of 5/10/2000 advising not to run
                MySQL as root, and am running into problems with MySQL no
                longer working correctly.

   7. Bugzilla Email

        A.7.1. I have a user who doesn't want to receive any more email
                from Bugzilla. How do I stop it entirely for this user?

        A.7.2. I'm evaluating/testing Bugzilla, and don't want it to send
                email to anyone but me. How do I do it?

        A.7.3. I want whineatnews.pl to whine at something more, or other
                than, only new bugs. How do I do it?

        A.7.4. I don't like/want to use Procmail to hand mail off to
                bug_email.pl. What alternatives do I have?

        A.7.5. How do I set up the email interface to submit/change bugs
                via email?

        A.7.6. Email takes FOREVER to reach me from bugzilla -- it's
                extremely slow. What gives?

        A.7.7. How come email never reaches me from bugzilla changes?

   8. Bugzilla Database

        A.8.1. I've heard Bugzilla can be used with Oracle?
        A.8.2. Bugs are missing from queries, but exist in the database
                (and I can pull them up by specifying the bug ID). What's
                wrong?

        A.8.3. I think my database might be corrupted, or contain invalid
                entries. What do I do?

        A.8.4. I want to manually edit some entries in my database. How?
        A.8.5. I try to add myself as a user, but Bugzilla always tells
                me my password is wrong.

        A.8.6. I think I've set up MySQL permissions correctly, but
                bugzilla still can't connect.

        A.8.7. How do I synchronize bug information among multiple
                different Bugzilla databases?

        A.8.8. Why do I get bizarre errors when trying to submit data,
                particularly problems with "groupset"?

        A.8.9. How come even after I delete bugs, the long descriptions
                show up?

   9. Bugzilla and Win32

        A.9.1. What is the easiest way to run Bugzilla on Win32
                (Win98+/NT/2K)?

        A.9.2. Is there a "Bundle::Bugzilla" equivalent for Win32?
        A.9.3. CGI's are failing with a "something.cgi is not a valid
                Windows NT application" error. Why?

        A.9.4. Can I have some general instructions on how to make
                Bugzilla on Win32 work?

        A.9.5. I'm having trouble with the perl modules for NT not being
                able to talk to to the database.

   10. Bugzilla Usage

        A.10.1. The query page is very confusing. Isn't there a simpler
                way to query?

        A.10.2. I'm confused by the behavior of the "accept" button in
                the Show Bug form. Why doesn't it assign the bug to me
                when I accept it?

        A.10.3. I can't upload anything into the database via the "Create
                Attachment" link. What am I doing wrong?

        A.10.4. Email submissions to Bugzilla that have attachments end
                up asking me to save it as a "cgi" file.

        A.10.5. How do I change a keyword in Bugzilla, once some bugs are
                using it?

   11. Bugzilla Hacking

        A.11.1. What bugs are in Bugzilla right now?
        A.11.2. What's the best way to submit patches? What guidelines
                should I follow?

1. General Questions

   A.1.1. Where can I find information about Bugzilla?

   You can stay up-to-date with the latest Bugzilla information at
   http://www.mozilla.org/projects/bugzilla/

   A.1.2. What license is Bugzilla distributed under?

   Bugzilla is covered by the Mozilla Public License. See details at
   http://www.mozilla.org/MPL/

   A.1.3. How do I get commercial support for Bugzilla?

   www.collab.net offers Bugzilla as part of their standard offering to
   large projects. They do have some minimum fees that are pretty hefty,
   and generally aren't interested in small projects.

   There are several experienced Bugzilla hackers on the mailing
   list/newsgroup who are willing to whore themselves out for generous
   compensation. Try sending a message to the mailing list asking for a
   volunteer.

   A.1.4. What major companies or projects are currently using Bugzilla
   for bug-tracking?

   There are dozens of major comapanies with public Bugzilla sites to
   track bugs in their products. A few include:

   Netscape/AOL
   Mozilla.org
   AtHome Corporation
   Red Hat Software
   Loki Entertainment Software
   SuSe Corp
   The Horde Project
   The Eazel Project
   AbiSource
   Real Time Enterprises, Inc
   Eggheads.org
   Strata Software
   RockLinux
   Creative Labs (makers of SoundBlaster)
   The Apache Foundation
   The Gnome Foundation
   Linux-Mandrake

   Suffice to say, there are more than enough huge projects using
   Bugzilla that we can safely say it's extremely popular.

   A.1.5. Who maintains Bugzilla?

   There are many, many contributors from around the world maintaining
   Bugzilla. The designated "Maintainer" is Tara Hernandez, with QA
   support by Matthew Tuck. Dan Mosedale and Dawn Endico are employees of
   Mozilla.org responsible for the installation of Bugzilla there, and
   are very frequent code contributors. Terry Weissman originally ported
   Bugzilla, but "these days, Terry just hangs around and heckles." The
   rest of us are mostly transient developers; Bugzilla suits our needs,
   and we contribute code as we have needs for updates.

   A.1.6. How does Bugzilla stack up against other bug-tracking
   databases?

   A year has gone by, and I still can't find any head-to-head
   comparisons of Bugzilla against other defect-tracking software.
   However, from my personal experience with other bug-trackers, Bugzilla
   offers superior performance on commodity hardware, better price
   (free!), more developer- friendly features (such as stored queries,
   email integration, and platform independence), improved scalability,
   open source code, greater flexibility, and superior ease-of-use.

   If you happen to be a commercial Bugzilla vendor, please step forward
   with a rebuttal so I can include it in the FAQ. We're not in pursuit
   of Bugzilla ueber alles; we simply love having a powerful, open-source
   tool to get our jobs done.

   A.1.7. How do I change my user name in Bugzilla?

   You can't. However, the administrative account can, by simply opening
   your user account in editusers.cgi and changing the login name.

   A.1.8. Why doesn't Bugzilla offer this or that feature or
   compatability with this other tracking software?

   It may be that the support has not been built yet, or that you have
   not yet found it. Bugzilla is making tremendous strides in usability,
   customizability, scalability, and user interface. It is widely
   considered the most complete and popular open-source bug-tracking
   software in existence.

   That doesn't mean it can't use improvement! You can help the project
   along by either hacking a patch yourself that supports the
   functionality you require, or else submitting a "Request for
   Enhancement" (RFE) using the bug submission interface at
   bugzilla.mozilla.org.

   A.1.9. Why MySQL? I'm interested in seeing Bugzilla run on
   Oracle/Sybase/Msql/PostgreSQL/MSSQL?

   Terry Weissman answers,

     You're not the only one. But I am not very interested. I'm not a
     real SQL or database person. I just wanted to make a useful tool,
     and build it on top of free software. So, I picked MySQL, and
     learned SQL by staring at the MySQL manual and some code lying
     around here, and wrote Bugzilla. I didn't know that Enum's were
     non-standard SQL. I'm not sure if I would have cared, but I didn't
     even know. So, to me, things are "portable" because it uses MySQL,
     and MySQL is portable enough. I fully understand (now) that people
     want to be portable to other databases, but that's never been a
     real concern of mine.

   Things aren't quite that grim these days, however. Terry pretty much
   sums up much of the thinking many of us have for Bugzilla, but there
   is light on the horizon for database-independence! Here are some
   options:

   Red Hat Bugzilla: Runs a modified Bugzilla 2.8 atop an Oracle
   database.
   Interzilla: A project to run Bugzilla on Interbase. No code released
   yet, however.
   Bugzilla 3.0: One of the primary stated goals is multiple database
   support.

   A.1.10. Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
   "/usr/bin/perl" or something else?

   Mozilla.org uses /usr/bonsaitools/bin/perl. The prime rule in making
   submissions is "don't break bugzilla.mozilla.org". If it breaks it,
   your patch will be reverted faster than you can do a diff.

   Here's Terry Weissman's comment, for some historical context:

     [This was] purely my own convention. I wanted a place to put a
     version of Perl and other tools that was strictly under my control
     for the various webtools, and not subject to anyone else. Edit it
     to point to whatever you like.

     Note: We always recommend that, if possible, you keep the path as
     /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools and
     /usr/bonsaitools/bin directory, then symlink your version of perl
     to /usr/bonsaitools/bin/perl. This will make upgrading your
     Bugzilla much easier in the future.

     Obviously, if you do not have root access to your Bugzilla box, our
     suggestion is irrelevant.

2. Red Hat Bugzilla

   A.2.1. What about Red Hat Bugzilla?

   Red Hat Bugzilla is arguably more user-friendly, customizable, and
   scalable than stock Bugzilla. Check it out at
   http://bugzilla.redhat.com and the sources at
   ftp://people.redhat.com/dkl/. They've set their Bugzilla up to work
   with Oracle out of the box. Note that Redhat Bugzilla is based upon
   the 2.8 Bugzilla tree; Bugzilla has made some tremendous advances
   since the 2.8 release. Why not download both Bugzillas to check out
   the differences for yourself?

   Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:

     Somebody needs to take the ball and run with it. I'm the only
     maintainer and am very pressed for time.

   If you, or someone you know, has the time and expertise to do the
   integration work so main-tree Bugzilla 2.12 and higher integrates the
   Red Hat Bugzilla Oracle modifications, please donate your time to
   supporting the Bugzilla project.

   A.2.2. What are the primary benefits of Red Hat Bugzilla?

   Dave Lawrence:

     For the record, we are not using any template type implementation
     for the cosmetic changes maded to Bugzilla. It is just alot of html
     changes in the code itself. I admit I may have gotten a little
     carried away with it but the corporate types asked for a more
     standardized interface to match up with other projects relating to
     Red Hat web sites. A lot of other web based internal tools I am
     working on also look like Bugzilla.

     I do want to land the changes that I have made to Bugzilla but I
     may have to back out a good deal and make a different version of
     Red Hat's Bugzilla for checking in to CVS. Especially the cosmetic
     changes because it seems they may not fit the general public. I
     will do that as soon as I can. I also still do my regular QA
     responsibilities along with Bugzilla so time is difficult sometimes
     to come by.

     There are also a good deal of other changes that were requested by
     management for things like support contracts and different
     permission groups for making bugs private. Here is a short list of
     the major changes that have been made:

    1. No enum types. All old enum types are now separate smaller tables.
    2. No bit wise operations. Not all databases support this so they
       were changed to a more generic way of doing this task
    3. Bug reports can only be altered by the reporter, assignee, or a
       privileged bugzilla user. The rest of the world can see the bug
       but in a non-changeable format (unless the bug has been marked
       private). They can however add comments, add and remove themselves
       from the CC list
    4. Different group scheme. Each group has an id number related to it.
       There is a user_group table which contains userid to groupid
       mappings to determine which groups each user belongs to.
       Additionally there is a bug_group table that has bugid to groupid
       mappings to show which groups can see a particular bug. If there
       are no entries for a bug in this table then the bug is public.
    5. Product groups. product_table created to only allow certain
       products to be visible for certain groups in both bug entry and
       query. This was particulary helpful for support contracts.
    6. Of course many (too many) changes to Bugzilla code itself to allow
       use with Oracle and still allow operation with Mysql if so
       desired. Currently if you use Mysql it is set to use Mysql's old
       permission scheme to keep breakage to a minimum. Hopefully one day
       this will standardize on one style which may of course be
       something completely different.
    7. Uses Text::Template perl module for rendering of the dynamic HTML
       pages such as enter_bug.cgi, query.cgi, bug_form.pl, and for the
       header and footer parts of the page. This allows the html to be
       separate from the perl code for customizing the look and feel of
       the page to one's preference.
    8. There are many other smaller changes. There is also a port to
       Oracle that I have been working on as time permits but is not
       completely finished but somewhat usable. I will merge it into our
       standard code base when it becomes production quality.
       Unfortunately there will have to be some conditionals in the code
       to make it work with other than Oracle due to some differences
       between Oracle and Mysql.

     Both the Mysql and Oracle versions of our current code base are
     available from ftp://people.redhat.com/dkl. If Terry/Tara wants I
     can submit patch files for all of the changes I have made and he
     can determine what is suitable for addition to the main bugzilla
     cade base. But for me to commit changes to the actual CVS I will
     need to back out alot of things that are not suitable for the rest
     of the Bugzilla community. I am open to suggestions.

   A.2.3. What's the current status of Red Hat Bugzilla?

     Note: This information is somewhat dated; I last updated it 7 June
     2000.

   Dave Lawrence:

     I suppose the current thread warrants an update on the status of
     Oracle and bugzilla ;) We have now been running Bugzilla 2.8 on
     Oracle for the last two days in our production environment. I tried
     to do as much testing as possible with it before going live which
     is some of the reason for the long delay. I did not get enough
     feedback as I would have liked from internal developers to help
     weed out any bugs still left so I said "Fine, i will take it live
     and then I will get the feedback I want :)" So it is now starting
     to stabilize and it running quite well after working feverishly the
     last two days fixing problems as soon as they came in from the
     outside world. The current branch in cvs is up2date if anyone would
     like to grab it and try it out. The oracle _setup.pl is broken
     right now due to some last minute changes but I will update that
     soon. Therefore you would probably need to create the database
     tables the old fashioned way using the supplied sql creation
     scripts located in the ./oracle directory. We have heavy
     optimizations in the database it self thanks to the in-house DBA
     here at Red Hat so it is running quite fast. The database itself is
     located on a dual PII450 with 1GB ram and 14 high voltage
     differential raided scsi drives. The tables and indexes are
     partitioned in 4 chuncks across the raided drive which is nice
     because when ever you need to do a full table scan, it is actually
     starting in 4 different locations on 4 different drives
     simultaneously. And the indexes of course are on separate drives
     from the data so that speeds things up tremendously. When I can
     find the time I will document all that we have done to get this
     thing going to help others that may need it.

     As Matt has mentioned it is still using out-dated code and with a
     little help I would like to bring everything up to date for
     eventual incorporation with the main cvs tree. Due to other duties
     I have with the company any help with this wiould be appreciated.
     What we are using now is what I call a best first effort. It
     definitely can be improved on and may even need complete rewrites
     in a lot of areas. A lot of changes may have to be made in the way
     Bugzilla does things currently to make this transition to a more
     generic database interface. Fortunately when making the Oracle
     changes I made sure I didn't do anything that I would consider
     Oracle specific and could not be easily done with other databases.
     Alot of the sql statements need to be broken up into smaller
     utilities that themselves would need to make decisions on what
     database they are using but the majority of the code can be made
     database neutral.

3. Loki Bugzilla (AKA Fenris)

     Note: Loki's "Fenris" Bugzilla is no longer actively maintained. It
     works well enough for Loki. Additionally, the major differences in
     Fenris have now been integrated into the main source tree of
     Bugzilla, so there's not much reason to go grab the source. I left
     this section of the FAQ principally for historical interest.

   A.3.1. What about Loki Bugzilla?

   Loki Games has a customized version of Bugzilla available at
   http://fenris.lokigames.com. From that page,

     You may have noticed that Fenris is a fork from Bugzilla-- our
     patches weren't suitable for integration --and a few people have
     expressed interest in the code. Fenris has one major improvement
     over Bugzilla, and that is individual comments are not appended
     onto a string blob, they are stored as a record in a separate
     table. This allows you to, for instance, separate comments out
     according to privilege levels in case your bug database could
     contain sensitive information not for public eyes. We also provide
     things like email hiding to protect user's privacy, additional
     fields such as 'user_affected' in case someone enters someone
     else's bug, comment editing and deletion, and more conditional
     system variables than Bugzilla does (turn off attachments,
     qacontact, etc.).

   A.3.2. Who maintains Fenris (Loki Bugzilla) now?

   Raphael Barrerro <raistlin@lokigames.com>. Michael Vance created the
   initial fork, but no longer maintains the project.

   A.3.3.

4. Pointy-Haired-Boss Questions

     Note: The title of this section doesn't mean you're a PHB -- it
     just means you probably HAVE a PHB who wants to know this :)

   A.4.1. Is Bugzilla web-based or do you have to have specific software
   or specific operating system on your machine?

   It is web and e-mail based. You can edit bugs by sending specially
   formatted email to a properly configured Bugzilla, or control via the
   web.

   A.4.2. Has anyone you know of already done any Bugzilla integration
   with Perforce (SCM software)?

   Yes! You can find more information elsewhere in "The Bugzilla Guide"
   in the "Integration with Third-Party Products" section. The section on
   Perforce isn't very large, but as the maintainer of the Guide is
   charged with Perforce/Bugzilla integration by his company, you can
   expect this section to grow.

   A.4.3. Does Bugzilla allow the user to track multiple projects?

   Absolutely! You can track up to a "soft-limit" of around 64 individual
   "Products", that can each be composed of as many "Components" as you
   want. Check the Administration section of the Bugzilla Guide for more
   information regarding setting up Products and Components.

   A.4.4. If I am on many projects, and search for all bugs assigned to
   me, will Bugzilla list them for me and allow me to sort by project,
   severity etc?

   Yes.

   A.4.5. Does Bugzilla allow attachments (text, screenshots, urls etc)?
   If yes, are there any that are NOT allowed?

   Yes. There are many specific MIME-types that are pre-defined by
   Bugzilla, but you may specify any arbitrary MIME-type you need when
   you upload the file. Since all attachments are stored in the database,
   however, I recommend storing large binary attachments elsewhere in the
   web server's file system and providing a hyperlink as a comment, or in
   the provided "URL" field in the bug report.

   A.4.6. Does Bugzilla allow us to define our own priorities and levels?
   Do we have complete freedom to change the labels of fields and format
   of them, and the choice of acceptable values?

   Yes. However, modifying some fields, notably those related to bug
   progression states, also require adjusting the program logic to
   compensate for the change.

   A.4.7. Does Bugzilla provide any reporting features, metrics, graphs,
   etc? You know, the type of stuff that management likes to see. :)

   Yes. Look at http://bugzilla.mozilla.org/reports.cgi for basic
   reporting facilities.

   For more advanced reporting, I recommend hooking up a professional
   reporting package, such as Crystal Reports, and use ODBC to access the
   MySQL database. You can do a lot through the Query page of Bugzilla as
   well, but right now Advanced Reporting is much better accomplished
   through third-party utilities that can interface with the database
   directly.

   Advanced Reporting is a Bugzilla 3.X proposed feature.

   A.4.8. Is there email notification and if so, what do you see when you
   get an email? Do you see bug number and title or is it only the
   number?

   Email notification is user-configurable. The bug id and Topic of the
   bug report accompany each email notification, along with a list of the
   changes made.

   A.4.9. Can email notification be set up to send to multiple people,
   some on the To List, CC List, BCC List etc?

   Yes.

   A.4.10. If there is email notification, do users have to have any
   particular type of email application?

   Bugzilla email is sent in plain text, the most compatible mail format
   on the planet.

     Note: If you decide to use the bugzilla_email integration features
     to allow Bugzilla to record responses to mail with the associated
     bug, you may need to caution your users to set their mailer to
     "respond to messages in the format in which they were sent". For
     security reasons Bugzilla ignores HTML tags in comments, and if a
     user sends HTML-based email into Bugzilla the resulting comment
     looks downright awful.

   A.4.11. If I just wanted to track certain bugs, as they go through
   life, can I set it up to alert me via email whenever that bug changes,
   whether it be owner, status or description etc.?

   Yes. Place yourself in the "cc" field of the bug you wish to monitor.
   Then change your "Notify me of changes to" field in the Email Settings
   tab of the User Preferences screen in Bugzilla to the "Only those bugs
   which I am listed on the CC line" option.

   A.4.12. Does Bugzilla allow data to be imported and exported? If I had
   outsiders write up a bug report using a MS Word bug template, could
   that template be imported into "matching" fields? If I wanted to take
   the results of a query and export that data to MS Excel, could I do
   that?

   Mozilla allows data export through a custom DTD in XML format. It does
   not, however, export to specific formats other than the XML Mozilla
   DTD. Importing the data into Excel or any other application is left as
   an exercise for the reader.

   If you create import filters to other applications from Mozilla's XML,
   please submit your modifications for inclusion in future Bugzilla
   distributions.

   As for data import, any application can send data to Bugzilla through
   the HTTP protocol, or through Mozilla's XML API. However, it seems
   kind of silly to put another front-end in front of Bugzilla; it makes
   more sense to create a simplified bug submission form in HTML. You can
   find an excellent example at
   http://www.mozilla.org/quality/help/bugzilla-helper.html

   A.4.13. Does Bugzilla allow fields to be added, changed or deleted? If
   I want to customize the bug submission form to meet our needs, can I
   do that using our terminology?

   Yes.

   A.4.14. Has anyone converted Bugzilla to another language to be used
   in other countries? Is it localizable?

   Currently, no. Internationalization support for Perl did not exist in
   a robust fashion until the recent release of version 5.6.0; Bugzilla
   is, and likely will remain (until 3.X) completely non-localized.

   A.4.15. Can a user create and save reports? Can they do this in Word
   format? Excel format?

   Yes. No. No.

   A.4.16. Can a user re-run a report with a new project, same query?

   Yes.

   A.4.17. Can a user modify an existing report and then save it into
   another name?

   You can save an unlimited number of queries in Bugzilla. You are free
   to modify them and rename them to your heart's desire.

   A.4.18. Does Bugzilla have the ability to search by word, phrase,
   compound search?

   You have no idea. Bugzilla's query interface, particularly with the
   advanced Boolean operators, is incredibly versatile.

   A.4.19. Can the admin person establish separate group and individual
   user privileges?

   Yes.

   A.4.20. Does Bugzilla provide record locking when there is
   simultaneous access to the same bug? Does the second person get a
   notice that the bug is in use or how are they notified?

   Bugzilla does not lock records. It provides mid-air collision
   detection, and offers the offending user a choice of options to deal
   with the conflict.

   A.4.21. Are there any backup features provided?

   MySQL, the database back-end for Bugzilla, allows hot-backup of data.
   You can find strategies for dealing with backup considerations at
   http://www.mysql.com/doc/B/a/Backup.html

   A.4.22. Can users be on the system while a backup is in progress?

   Yes. However, commits to the database must wait until the tables are
   unlocked. Bugzilla databases are typically very small, and backups
   routinely take less than a minute.

   A.4.23. What type of human resources are needed to be on staff to
   install and maintain Bugzilla? Specifically, what type of skills does
   the person need to have? I need to find out if we were to go with
   Bugzilla, what types of individuals would we need to hire and how much
   would that cost vs buying an "Out-of-the-Box" solution.

   If Bugzilla is set up correctly from the start, continuing maintenance
   needs are minimal and can be completed by unskilled labor. Things like