PageRenderTime 75ms CodeModel.GetById 22ms RepoModel.GetById 0ms app.codeStats 1ms

/tags/Doduo_1.1/BugsSite/docs/html/groups.html

https://github.com/weissms/owb-mirror
HTML | 632 lines | 632 code | 0 blank | 0 comment | 0 complexity | 5a2d724159f36d24821d5b87095dccaa MD5 | raw file
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
  2. <HTML
  3. ><HEAD
  4. ><TITLE
  5. >Groups and Group Security</TITLE
  6. ><META
  7. NAME="GENERATOR"
  8. CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
  9. REL="HOME"
  10. TITLE="The Bugzilla Guide - 2.20.1
  11. Release"
  12. HREF="index.html"><LINK
  13. REL="UP"
  14. TITLE="Administering Bugzilla"
  15. HREF="administration.html"><LINK
  16. REL="PREVIOUS"
  17. TITLE="Quips"
  18. HREF="quips.html"><LINK
  19. REL="NEXT"
  20. TITLE="Upgrading to New Releases"
  21. HREF="upgrading.html"></HEAD
  22. ><BODY
  23. CLASS="section"
  24. BGCOLOR="#FFFFFF"
  25. TEXT="#000000"
  26. LINK="#0000FF"
  27. VLINK="#840084"
  28. ALINK="#0000FF"
  29. ><DIV
  30. CLASS="NAVHEADER"
  31. ><TABLE
  32. SUMMARY="Header navigation table"
  33. WIDTH="100%"
  34. BORDER="0"
  35. CELLPADDING="0"
  36. CELLSPACING="0"
  37. ><TR
  38. ><TH
  39. COLSPAN="3"
  40. ALIGN="center"
  41. >The Bugzilla Guide - 2.20.1
  42. Release</TH
  43. ></TR
  44. ><TR
  45. ><TD
  46. WIDTH="10%"
  47. ALIGN="left"
  48. VALIGN="bottom"
  49. ><A
  50. HREF="quips.html"
  51. ACCESSKEY="P"
  52. >Prev</A
  53. ></TD
  54. ><TD
  55. WIDTH="80%"
  56. ALIGN="center"
  57. VALIGN="bottom"
  58. >Chapter 3. Administering Bugzilla</TD
  59. ><TD
  60. WIDTH="10%"
  61. ALIGN="right"
  62. VALIGN="bottom"
  63. ><A
  64. HREF="upgrading.html"
  65. ACCESSKEY="N"
  66. >Next</A
  67. ></TD
  68. ></TR
  69. ></TABLE
  70. ><HR
  71. ALIGN="LEFT"
  72. WIDTH="100%"></DIV
  73. ><DIV
  74. CLASS="section"
  75. ><H1
  76. CLASS="section"
  77. ><A
  78. NAME="groups"
  79. >3.10. Groups and Group Security</A
  80. ></H1
  81. ><P
  82. >Groups allow the administrator
  83. to isolate bugs or products that should only be seen by certain people.
  84. The association between products and groups is controlled from
  85. the product edit page under <SPAN
  86. CLASS="QUOTE"
  87. >"Edit Group Controls."</SPAN
  88. >
  89. </P
  90. ><P
  91. >&#13; If the makeproductgroups param is on, a new group will be automatically
  92. created for every new product. It is primarily available for backward
  93. compatibility with older sites.
  94. </P
  95. ><P
  96. >&#13; Note that group permissions are such that you need to be a member
  97. of <EM
  98. >all</EM
  99. > the groups a bug is in, for whatever
  100. reason, to see that bug. Similarly, you must be a member
  101. of <EM
  102. >all</EM
  103. > of the entry groups for a product
  104. to add bugs to a product and you must be a member
  105. of <EM
  106. >all</EM
  107. > of the canedit groups for a product
  108. in order to make <EM
  109. >any</EM
  110. > change to bugs in that
  111. product.
  112. </P
  113. ><DIV
  114. CLASS="note"
  115. ><P
  116. ></P
  117. ><TABLE
  118. CLASS="note"
  119. WIDTH="100%"
  120. BORDER="0"
  121. ><TR
  122. ><TD
  123. WIDTH="25"
  124. ALIGN="CENTER"
  125. VALIGN="TOP"
  126. ><IMG
  127. SRC="../images/note.gif"
  128. HSPACE="5"
  129. ALT="Note"></TD
  130. ><TD
  131. ALIGN="LEFT"
  132. VALIGN="TOP"
  133. ><P
  134. >&#13; By default, bugs can also be seen by the Assignee, the Reporter, and
  135. by everyone on the CC List, regardless of whether or not the bug would
  136. typically be viewable by them. Visibility to the Reporter and CC List can
  137. be overridden (on a per-bug basis) by bringing up the bug, finding the
  138. section that starts with <SPAN
  139. CLASS="QUOTE"
  140. >"Users in the roles selected below..."</SPAN
  141. >
  142. and un-checking the box next to either 'Reporter' or 'CC List' (or both).
  143. </P
  144. ></TD
  145. ></TR
  146. ></TABLE
  147. ></DIV
  148. ><DIV
  149. CLASS="section"
  150. ><H2
  151. CLASS="section"
  152. ><A
  153. NAME="AEN1438"
  154. >3.10.1. Creating Groups</A
  155. ></H2
  156. ><P
  157. >To create Groups:</P
  158. ><P
  159. ></P
  160. ><OL
  161. TYPE="1"
  162. ><LI
  163. ><P
  164. >Select the <SPAN
  165. CLASS="QUOTE"
  166. >"groups"</SPAN
  167. >
  168. link in the footer.</P
  169. ></LI
  170. ><LI
  171. ><P
  172. >Take a moment to understand the instructions on the <SPAN
  173. CLASS="QUOTE"
  174. >"Edit
  175. Groups"</SPAN
  176. > screen, then select the <SPAN
  177. CLASS="QUOTE"
  178. >"Add Group"</SPAN
  179. > link.</P
  180. ></LI
  181. ><LI
  182. ><P
  183. >Fill out the <SPAN
  184. CLASS="QUOTE"
  185. >"Group"</SPAN
  186. >, <SPAN
  187. CLASS="QUOTE"
  188. >"Description"</SPAN
  189. >,
  190. and <SPAN
  191. CLASS="QUOTE"
  192. >"User RegExp"</SPAN
  193. > fields.
  194. <SPAN
  195. CLASS="QUOTE"
  196. >"User RegExp"</SPAN
  197. > allows you to automatically
  198. place all users who fulfill the Regular Expression into the new group.
  199. When you have finished, click <SPAN
  200. CLASS="QUOTE"
  201. >"Add"</SPAN
  202. >.</P
  203. ><P
  204. >Users whose email addresses match the regular expression
  205. will automatically be members of the group as long as their
  206. email addresses continue to match the regular expression.</P
  207. ><DIV
  208. CLASS="note"
  209. ><P
  210. ></P
  211. ><TABLE
  212. CLASS="note"
  213. WIDTH="100%"
  214. BORDER="0"
  215. ><TR
  216. ><TD
  217. WIDTH="25"
  218. ALIGN="CENTER"
  219. VALIGN="TOP"
  220. ><IMG
  221. SRC="../images/note.gif"
  222. HSPACE="5"
  223. ALT="Note"></TD
  224. ><TD
  225. ALIGN="LEFT"
  226. VALIGN="TOP"
  227. ><P
  228. >This is a change from 2.16 where the regular expression
  229. resulted in a user acquiring permanent membership in a group.
  230. To remove a user from a group the user was in due to a regular
  231. expression in version 2.16 or earlier, the user must be explicitly
  232. removed from the group. This can easily be done by pressing
  233. buttons named 'Remove Memberships' or 'Remove Memberships
  234. included in regular expression' under the table.</P
  235. ></TD
  236. ></TR
  237. ></TABLE
  238. ></DIV
  239. ><DIV
  240. CLASS="warning"
  241. ><P
  242. ></P
  243. ><TABLE
  244. CLASS="warning"
  245. WIDTH="100%"
  246. BORDER="0"
  247. ><TR
  248. ><TD
  249. WIDTH="25"
  250. ALIGN="CENTER"
  251. VALIGN="TOP"
  252. ><IMG
  253. SRC="../images/warning.gif"
  254. HSPACE="5"
  255. ALT="Warning"></TD
  256. ><TD
  257. ALIGN="LEFT"
  258. VALIGN="TOP"
  259. ><P
  260. >If specifying a domain in the regexp, make sure you end
  261. the regexp with a $. Otherwise, when granting access to
  262. "@mycompany\.com", you will allow access to
  263. 'badperson@mycompany.com.cracker.net'. You need to use
  264. '@mycompany\.com$' as the regexp.</P
  265. ></TD
  266. ></TR
  267. ></TABLE
  268. ></DIV
  269. ></LI
  270. ><LI
  271. ><P
  272. >If you plan to use this group to directly control
  273. access to bugs, check the "use for bugs" box. Groups
  274. not used for bugs are still useful because other groups
  275. can include the group as a whole.</P
  276. ></LI
  277. ><LI
  278. ><P
  279. >After you add your new group, edit the new group. On the
  280. edit page, you can specify other groups that should be included
  281. in this group and which groups should be permitted to add and delete
  282. users from this group.</P
  283. ></LI
  284. ></OL
  285. ></DIV
  286. ><DIV
  287. CLASS="section"
  288. ><H2
  289. CLASS="section"
  290. ><A
  291. NAME="AEN1465"
  292. >3.10.2. Assigning Users to Groups</A
  293. ></H2
  294. ><P
  295. >Users can become a member of a group in several ways.</P
  296. ><P
  297. ></P
  298. ><OL
  299. TYPE="1"
  300. ><LI
  301. ><P
  302. >The user can be explicitly placed in the group by editing
  303. the user's own profile</P
  304. ></LI
  305. ><LI
  306. ><P
  307. >The group can include another group of which the user is
  308. a member.</P
  309. ></LI
  310. ><LI
  311. ><P
  312. >The user's email address can match a regular expression
  313. that the group specifies to automatically grant membership to
  314. the group.</P
  315. ></LI
  316. ></OL
  317. ></DIV
  318. ><DIV
  319. CLASS="section"
  320. ><H2
  321. CLASS="section"
  322. ><A
  323. NAME="AEN1475"
  324. >3.10.3. Assigning Group Controls to Products</A
  325. ></H2
  326. ><P
  327. >&#13; On the product edit page, there is a page to edit the
  328. <SPAN
  329. CLASS="QUOTE"
  330. >"Group Controls"</SPAN
  331. >
  332. for a product. This allows you to
  333. configure how a group relates to the product.
  334. Groups may be applicable, default,
  335. and mandatory as well as used to control entry
  336. or used to make bugs in the product
  337. totally read-only unless the group restrictions are met.
  338. </P
  339. ><P
  340. >&#13; For each group, it is possible to specify if membership in that
  341. group is...
  342. </P
  343. ><P
  344. ></P
  345. ><OL
  346. TYPE="1"
  347. ><LI
  348. ><P
  349. >&#13; required for bug entry,
  350. </P
  351. ></LI
  352. ><LI
  353. ><P
  354. >&#13; Not applicable to this product(NA),
  355. a possible restriction for a member of the
  356. group to place on a bug in this product(Shown),
  357. a default restriction for a member of the
  358. group to place on a bug in this product(Default),
  359. or a mandatory restriction to be placed on bugs
  360. in this product(Mandatory).
  361. </P
  362. ></LI
  363. ><LI
  364. ><P
  365. >&#13; Not applicable by non-members to this product(NA),
  366. a possible restriction for a non-member of the
  367. group to place on a bug in this product(Shown),
  368. a default restriction for a non-member of the
  369. group to place on a bug in this product(Default),
  370. or a mandatory restriction to be placed on bugs
  371. in this product when entered by a non-member(Mandatory).
  372. </P
  373. ></LI
  374. ><LI
  375. ><P
  376. >&#13; required in order to make <EM
  377. >any</EM
  378. > change
  379. to bugs in this product <EM
  380. >including comments.</EM
  381. >
  382. </P
  383. ></LI
  384. ></OL
  385. ><P
  386. >These controls are often described in this order, so a
  387. product that requires a user to be a member of group "foo"
  388. to enter a bug and then requires that the bug stay restricted
  389. to group "foo" at all times and that only members of group "foo"
  390. can edit the bug even if they otherwise could see the bug would
  391. have its controls summarized by...</P
  392. ><TABLE
  393. BORDER="0"
  394. BGCOLOR="#E0E0E0"
  395. WIDTH="100%"
  396. ><TR
  397. ><TD
  398. ><FONT
  399. COLOR="#000000"
  400. ><PRE
  401. CLASS="programlisting"
  402. >
  403. foo: ENTRY, MANDATORY/MANDATORY, CANEDIT
  404. </PRE
  405. ></FONT
  406. ></TD
  407. ></TR
  408. ></TABLE
  409. ></DIV
  410. ><DIV
  411. CLASS="section"
  412. ><H2
  413. CLASS="section"
  414. ><A
  415. NAME="AEN1493"
  416. >3.10.4. Common Applications of Group Controls</A
  417. ></H2
  418. ><DIV
  419. CLASS="section"
  420. ><H3
  421. CLASS="section"
  422. ><A
  423. NAME="AEN1495"
  424. >3.10.4.1. General User Access With Security Group</A
  425. ></H3
  426. ><P
  427. >To permit any user to file bugs in each product (A, B, C...)
  428. and to permit any user to submit those bugs into a security
  429. group....</P
  430. ><TABLE
  431. BORDER="0"
  432. BGCOLOR="#E0E0E0"
  433. WIDTH="100%"
  434. ><TR
  435. ><TD
  436. ><FONT
  437. COLOR="#000000"
  438. ><PRE
  439. CLASS="programlisting"
  440. >
  441. Product A...
  442. security: SHOWN/SHOWN
  443. Product B...
  444. security: SHOWN/SHOWN
  445. Product C...
  446. security: SHOWN/SHOWN
  447. </PRE
  448. ></FONT
  449. ></TD
  450. ></TR
  451. ></TABLE
  452. ></DIV
  453. ><DIV
  454. CLASS="section"
  455. ><H3
  456. CLASS="section"
  457. ><A
  458. NAME="AEN1499"
  459. >3.10.4.2. General User Access With A Security Product</A
  460. ></H3
  461. ><P
  462. >To permit any user to file bugs in a Security product
  463. while keeping those bugs from becoming visible to anyone
  464. outside the securityworkers group unless a member of the
  465. securityworkers group removes that restriction....</P
  466. ><TABLE
  467. BORDER="0"
  468. BGCOLOR="#E0E0E0"
  469. WIDTH="100%"
  470. ><TR
  471. ><TD
  472. ><FONT
  473. COLOR="#000000"
  474. ><PRE
  475. CLASS="programlisting"
  476. >
  477. Product Security...
  478. securityworkers: DEFAULT/MANDATORY
  479. </PRE
  480. ></FONT
  481. ></TD
  482. ></TR
  483. ></TABLE
  484. ></DIV
  485. ><DIV
  486. CLASS="section"
  487. ><H3
  488. CLASS="section"
  489. ><A
  490. NAME="AEN1503"
  491. >3.10.4.3. Product Isolation With Common Group</A
  492. ></H3
  493. ><P
  494. >To permit users of product A to access the bugs for
  495. product A, users of product B to access product B, and support
  496. staff to access both, 3 groups are needed</P
  497. ><P
  498. ></P
  499. ><OL
  500. TYPE="1"
  501. ><LI
  502. ><P
  503. >Support: Contains members of the support staff.</P
  504. ></LI
  505. ><LI
  506. ><P
  507. >AccessA: Contains users of product A and the Support group.</P
  508. ></LI
  509. ><LI
  510. ><P
  511. >AccessB: Contains users of product B and the Support group.</P
  512. ></LI
  513. ></OL
  514. ><P
  515. >Once these 3 groups are defined, the products group controls
  516. can be set to..</P
  517. ><TABLE
  518. BORDER="0"
  519. BGCOLOR="#E0E0E0"
  520. WIDTH="100%"
  521. ><TR
  522. ><TD
  523. ><FONT
  524. COLOR="#000000"
  525. ><PRE
  526. CLASS="programlisting"
  527. >&#13;Product A...
  528. AccessA: ENTRY, MANDATORY/MANDATORY
  529. Product B...
  530. AccessB: ENTRY, MANDATORY/MANDATORY
  531. </PRE
  532. ></FONT
  533. ></TD
  534. ></TR
  535. ></TABLE
  536. ><P
  537. >Optionally, the support group could be permitted to make
  538. bugs inaccessible to the users and could be permitted to publish
  539. bugs relevant to all users in a common product that is read-only
  540. to anyone outside the support group. That configuration could
  541. be...</P
  542. ><TABLE
  543. BORDER="0"
  544. BGCOLOR="#E0E0E0"
  545. WIDTH="100%"
  546. ><TR
  547. ><TD
  548. ><FONT
  549. COLOR="#000000"
  550. ><PRE
  551. CLASS="programlisting"
  552. >&#13;Product A...
  553. AccessA: ENTRY, MANDATORY/MANDATORY
  554. Support: SHOWN/NA
  555. Product B...
  556. AccessB: ENTRY, MANDATORY/MANDATORY
  557. Support: SHOWN/NA
  558. Product Common...
  559. Support: ENTRY, DEFAULT/MANDATORY, CANEDIT
  560. </PRE
  561. ></FONT
  562. ></TD
  563. ></TR
  564. ></TABLE
  565. ></DIV
  566. ></DIV
  567. ></DIV
  568. ><DIV
  569. CLASS="NAVFOOTER"
  570. ><HR
  571. ALIGN="LEFT"
  572. WIDTH="100%"><TABLE
  573. SUMMARY="Footer navigation table"
  574. WIDTH="100%"
  575. BORDER="0"
  576. CELLPADDING="0"
  577. CELLSPACING="0"
  578. ><TR
  579. ><TD
  580. WIDTH="33%"
  581. ALIGN="left"
  582. VALIGN="top"
  583. ><A
  584. HREF="quips.html"
  585. ACCESSKEY="P"
  586. >Prev</A
  587. ></TD
  588. ><TD
  589. WIDTH="34%"
  590. ALIGN="center"
  591. VALIGN="top"
  592. ><A
  593. HREF="index.html"
  594. ACCESSKEY="H"
  595. >Home</A
  596. ></TD
  597. ><TD
  598. WIDTH="33%"
  599. ALIGN="right"
  600. VALIGN="top"
  601. ><A
  602. HREF="upgrading.html"
  603. ACCESSKEY="N"
  604. >Next</A
  605. ></TD
  606. ></TR
  607. ><TR
  608. ><TD
  609. WIDTH="33%"
  610. ALIGN="left"
  611. VALIGN="top"
  612. >Quips</TD
  613. ><TD
  614. WIDTH="34%"
  615. ALIGN="center"
  616. VALIGN="top"
  617. ><A
  618. HREF="administration.html"
  619. ACCESSKEY="U"
  620. >Up</A
  621. ></TD
  622. ><TD
  623. WIDTH="33%"
  624. ALIGN="right"
  625. VALIGN="top"
  626. >Upgrading to New Releases</TD
  627. ></TR
  628. ></TABLE
  629. ></DIV
  630. ></BODY
  631. ></HTML
  632. >