StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13183038
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-11-01T18:10:15.280
FavoriteCount
0
LastActivityDate
2012-11-01T18:10:15.280
LastEditDate
LastEditorUserId
0
OwnerUserId
182811
ParentId
13170088
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You didn't really say which version of Bugzilla you are using, so the URLs are for the latest release, 4.2. However, the same concepts apply to most recent versions. For instance, we use 3.6 and control whether certain users can change certain things in the same ways that I describe below. 1) Restricting users who are not in a group from seeing bugs is what Bugzilla's group security does: <a href="http://www.bugzilla.org/docs/4.2/en/html/groups.html" rel="nofollow">http://www.bugzilla.org/docs/4.2/en/html/groups.html</a> One wrinkle in your case is that group security controls positive access rather than negative access. That is, it allows specifying which groups can view bugs in a product rather than groups that cannot. To keep members of <code>students</code> from viewing bugs in <code>projectA</code>, you'll need to have a group that can access <code>projectA</code> and devise a way to keep users in <code>students</code> out of that group. Alternatively, you could put some custom code into <code>Bugzilla::User::can_see_bug</code>, <code>Bugzilla::User::visible_bugs</code>, or <code>Bugzilla::Bug::check_is_visible</code> to exert firmer control that users who are in group <code>students</code> can never see bugs in <code>projectA</code> 2) You can exercise a lot of granularity in allowing changes: <a href="http://www.bugzilla.org/docs/4.2/en/html/cust-change-permissions.html" rel="nofollow">http://www.bugzilla.org/docs/4.2/en/html/cust-change-permissions.html</a> We do something like this. We have a set of users to whom we want to grant read-only access unless we have explicitly allowed read-write access. To do this, we have a group called <code>allspecialusers</code> to which these users belong based on email address. We have another group called <code>approved_specialusers</code> to which some of those users are added manually. So, in our <code>Bugzilla::Bug::check_can_change_field</code>, we have code like: <blockquote> <pre><code>if ($user->in_group('specialusers') && !$user->in_group('approved_specialusers')) { $$PrivilegesRequired = 3; return 0; } </code></pre> </blockquote> You can do what you want by checking if the bug is in product <code>projectB</code> and the user trying to make the change is in group <code>students</code>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBugzilla restrict bug status
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDavid M
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POBugzilla restrict bug status
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COhi thanks so much for your respond. you've really pinpoint my problem precisely.anyway I've already update another question above.I really appreciate if you can help me with it.
 singulars
 PostPostId
 PO
 UserUserId
 USnewbie.my

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.