Bug 406321
| Summary: | 3.22: security-response-team@redhat.com Cc for new security bugs. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | David Lawrence <dkl> | ||||||||
| Component: | Bugzilla General | Assignee: | Noura El hawary <nelhawar> | ||||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | high | ||||||||||
| Version: | 3.2 | CC: | nelhawar | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | 2 hours | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2008-02-12 04:16:34 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 406071, 427051 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
David Lawrence
2007-11-30 16:58:39 UTC
LOC Estimation: Adding 50% to compensate for porting to Bugzilla/Bug.pm in 3.0 that uses create() instead of Add(). Bugzilla/Bug.pm: 20 + (20*.50) = 30 XMLRPC tests for Bug.create() to verify security added to cc list: 60 selenium tests to verify security add to cc list: 2 hours LOC Total: 90 Hi Dave, I think I can help you with this bug. Just letting you know so we don't work on it both at the same time. Thanks, Noura Created attachment 294536 [details]
patch to Bugzilla/Bug.pm
this is a patch to enable the following:
When group security is selected when a new bug is created then 3 things
should happen:
1- security-response-team is added to the cclist of the bug.
2- The cclist should only contain accounts that are members of the groups
selected when the bug is created.
3- Keyword Security is added to the bug's Keywords
also attaching selenium test for it.
Please review and let me know what you think.
Thanks,
Noura
Created attachment 294537 [details]
selenium test
This is a selenium test for the attached patch, fully documented . please note
that to run this test, you will need to run it on a freshly installed
rh_bugzilla_3 that has just had checksetup.pl run. also to run it you will need
to change line 366 in Bugzilla/Bug.pm after applying the previous patch to have
the groupid == 14 not 71 as 71 will be the group id for the security group
using our live bugzilla database.
I couldn't create any xmlrpc tests for this feature yet as the function
Bug.get() will not return any cclist or keywords information for the bug to
enable the testing of this feature for newly created bugs with the security
group assigned.
3 hours converting the rh_bugzilla_2_18 code to work with rh_bugzilla_3 2 hours testing Comment on attachment 294536 [details]
patch to Bugzilla/Bug.pm
Noura, patch looks nice and also installed on bugdev where it worked as
expected. If the Selenium case works then this is good to go.
Dave
Created attachment 294615 [details]
patch for bugs 406321 and 406141
cool , Thanks Dave. So what would be the next step shall we commit to cvs? also
I think this patch will conflict with your patch caze both of them update
Bugzilla/Bug.pm, so I am attaching a new patch that has both changes so we
apply it at once.
Noura
(In reply to comment #7) > Created an attachment (id=294615) [edit] > patch for bugs 406321 and 406141 > > cool , Thanks Dave. So what would be the next step shall we commit to cvs? also > I think this patch will conflict with your patch caze both of them update > Bugzilla/Bug.pm, so I am attaching a new patch that has both changes so we > apply it at once. One way to make sure this is normally not a problem is to always make sure you do a full cvs update before committing. So for example you would commit your security-response patch first, and then before I commit the rhel changes patch, I would cvs update and pull in your changes first, then commit mine. As long as we do not both edit the same exact lines, it will normally work out. If not then it will throw a conflict error and the last person will just work out the conflict and commit. Dave Oh, so anyway, go ahead and check this in ;) Dave |