Bug 712233 - partner-bugzilla does not talk to DEV (or QA) SFDC
Summary: partner-bugzilla does not talk to DEV (or QA) SFDC
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: Noura El hawary
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-09 21:08 UTC by Daniel Fisher
Modified: 2012-04-13 21:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-22 00:28:49 UTC


Attachments (Terms of Use)
result of Bug.get (17.82 KB, text/plain)
2011-06-21 13:43 UTC, Noura El hawary
no flags Details

Description Daniel Fisher 2011-06-09 21:08:47 UTC
Description of problem:

Attaching a "Red Hat Customer Portal (QA)" or "Red Hat Customer Portal (DEV)" case to partner-bugzilla doesn't actually attach it.

An attachment can be made in SFDC (DEV/QA) to a bug in partner-bugzilla, though.

I believe this has been seen before.

[Although I don't remember the fix.]

Comment 3 Daniel Fisher 2011-06-10 01:57:35 UTC
I have tried to connect 
bz-web2-test bz#730698
and
partner-bugzilla bz#710672

to 
SFDC DEV Case# 00458942

with no luck.

What's particularly strange is that when I look at the Debug logs in Dev for the bzautomation user, I see activity when it tries to disconnect a Case from a Bug, but I don't see any activity when it tries to connect a Case to a Bug.

Any idea why that'd be?

Comment 4 Daniel Fisher 2011-06-16 19:46:35 UTC
We need to talk about this and get it working correctly.

I'll try to be in touch tonight [EDT]

Comment 5 Simon Green 2011-06-21 10:54:34 UTC
Hi,

I think I have this working on bz-web2-test.devel.redhat.com. Can you please let me know if you agree with this. If so, I'll get a new package up on partner-bugzilla, so we can see if it works.

  -- simon

Comment 7 Scott Dodson 2011-06-21 13:09:41 UTC
Have we checked the database entries that correspond to the external tracker types? Perhaps the external trackers are configured differently?

Comment 8 Noura El hawary 2011-06-21 13:41:45 UTC
Hi Scott, 

I just tested the function:
    my $bug_data = Bugzilla::WebService::Bug->get({
        ids            => [$bug->id],
        extra_fields   => ['external_bugs','description'],
        exclude_fields => ['internals']
    });


in extensions/ExternalBugs/lib/Type/SFDC_DEV.pm

and seems to be returning the external_bugs fine as the following:

                       'external_bugs' => [
                                             bless( {
                                                      'ext_description' => 'None',
                                                      'ext_bz_id' => '1',
                                                      'ext_last_updated' => '2011-06-20 21:50:01',
                                                      'bug_id' => '1',
                                                      'ext_bz_bug_id' => 'ORG-123',
                                                      'id' => '1',
                                                      'ext_status' => 'RESOLVED',
                                                      'type' => bless( {
                                                                         'must_send' => '0',
                                                                         'can_send' => '0',
                                                                         'description' => 'test',
                                                                         'can_get' => '1',
                                                                         'url' => 'http://www.test.com',
                                                                         'id' => '1',
                                                                         'type' => 'JIRA',
                                                                         'full_url' => 'http://www.test.com/%id%=id'
                                                                       }, 'Bugzilla::Extension::ExternalBugs::Type::JIRA' )
                                                    }, 'Bugzilla::Extension::ExternalBugs::Bug' )
                                           ],

the above is a test data from my local installation. attached is a full result of Bug.get

Do you see anything wrong with the returned result?

Comment 9 Noura El hawary 2011-06-21 13:43:03 UTC
Created attachment 505832 [details]
result of Bug.get

Please check the output of the Bug.get

Comment 10 Daniel Fisher 2011-06-21 17:11:36 UTC
The fix is to run (in the database)

UPDATE external_bugzilla set must_send=1 WHERE description LIKE 'Red Hat Customer Portal (%';

It would be VERY useful to have this as part of the deployment to Dev so that we can avoid this in the future.

After running the above, Bugs can be linked to Cases and Bug Comments relay to the Case(s) it is linked to.

Comment 11 Scott Dodson 2011-06-21 20:58:10 UTC
Setting ON_DEV.

Comment 12 Scott Dodson 2011-06-21 21:12:28 UTC
Simon,

There was a misunderstanding between Dan and I. We still need this value changed in partner-bugzilla.redhat.com. This should be do-able via the bugzilla UI by anyone that's a bugzilla admin AFAIK.

Comment 14 dfisher test 2011-08-22 17:30:40 UTC
This is a test of a public comment.

Comment 15 Daniel Fisher 2011-08-22 17:31:46 UTC
This is an RH-internal public comment test.


Note You need to log in before you can comment on or make changes to this bug.