| Summary: | Odd entries related to external trackers in history | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Bernd Groh <bgroh> |
| Component: | Bugzilla General | Assignee: | Tony Fu <tfu> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2 | CC: | ahecox, dfisher, ebaak, jfearn, sfloess |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-11-16 02:11:16 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 723050 | ||
| Bug Blocks: | 834142 | ||
The requests we investigated last week were all created through the BZ UI, none through SFDC. I very much doubt these were created through the BZ UI. There's just no way, at least not as far as I can see. The only way I can explain this is that someone made an according xmlrpc call, and I guess the only way to be sure is to ask the people who made the change, and hope they remember. As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time. If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically. Thanks, the Bugzilla team. This requires testing to see if it's still a problem. Very low priority, though. It is still a problem, and it comes from Hardware Cert. Assigning this bug to tfu, since I mentioned it to him last week, and he is going to change it. -- simon |
Description of problem: Odd entries related to external trackers are making it into the history. I haven't tried to reproduce the problem, and I don't exactly know what's causing it, but I've found three bugs where this is the case: $VAR1 = { 'added' => '', 'attach_id' => undef, 'bug_id' => '630990', 'bug_when' => '2010-10-20 11:30:27', 'fieldid' => '76', 'removed' => 'https://access.redhat.com/show_bug.cgi?id=00320418', 'who' => '174484' }; $VAR1 = { 'added' => '', 'attach_id' => undef, 'bug_id' => '499874', 'bug_when' => '2011-02-02 03:39:10', 'fieldid' => '76', 'removed' => 'https://access.redhat.com/show_bug.cgi?id=00358403', 'who' => '266078' }; $VAR1 = { 'added' => '', 'attach_id' => undef, 'bug_id' => '672138', 'bug_when' => '2011-02-03 07:19:24', 'fieldid' => '76', 'removed' => 'https://access.redhat.com/show_bug.cgi?id=00408969', 'who' => '200676' }; "https://access.redhat.com/show_bug.cgi?id=" is not a valid url for any tracker, and while it seems to have deleted the BZ<->SFDC association in Bugzilla, it does not seem to propagate the deletion through to SFDC. I can only speculate that these requests were sent via xmlrpc, as I don't see the UI allowing this, though I'm not entirely certain. If so, such requests should simply be rejected, i.e. nothing should happen. Unless the url has the right format, it should not trigger a deletion of an external tracker. Equally, irrespective of how the request is issued, all history entries relating to the deletion of external trackers should have the same format, and the "removed" entry should read "Red Hat Customer Portal <id>".