I wanted to do test BZ5<=>SFDC Ticketing interactions. I tried to link https://beta-bugzilla.redhat.com/show_bug.cgi?id=1148545 *in* Ticketing's SFDC QA on Case 01846644 And it shows up as an External Tracker for BZ 1148545 (that's good) HOWEVER, 'Send Changes' is marked as 'No' and Priority, Status, and Summary are all not present I also tried to link: https://beta-bugzilla.redhat.com/show_bug.cgi?id=1148545 to Ticket's SFDC QA case 01844101 *in* BZ5 That shows up in the External Trackers of BZ, but did not propagate to SFDC QA. And it's also got the same problem as the BZ1148545<=>QA 01846644 External Tracker: Priority, Status, and Summary are all not present I think 'Send Changes' needs to be activated for Beta-Bugzilla in order to test this.
Hi Daniel, can you test this on https://bugzilla5.redhat.com or https://partner-bugzilla5.redhat.com ?
Jeff, I have changed our SFDC QA to point at bugzilla5.redhat.com, but I have seen similar results: Attempting to link from SFDC QA Case# 01905773 to BZ1168295 (on the SFDC Case page) results in SFDC Case showing they're linked. The Bugzilla shows they're linked, but also doesn't show useful information (like Priority, Status, Summary... and 'Send Changes' is set to 'No'): https://bugzilla5.redhat.com/show_bug.cgi?id=1168295#et0 And attempting to link from bz 1240363 to SFDC QA Case 01905773 (on the Bugzilla page) results in SFDC Case *NOT* showing they're linked... and the Bugzilla shows they're linked, but doesn't show useful information (ike Priority, Status, Summary... and 'Send Changes' is set to 'No'): https://bugzilla5.redhat.com/show_bug.cgi?id=1240363#et0 Help?
I've updated the RHCP QA ET on BZ5 to the same settings as the RHCP Prod ET on BZ5.
While I do see that "Send Updates" is checked in https://bugzilla5.redhat.com/show_bug.cgi?id=1192170#et0 for a link to 01905766, I do *not* see the accompanying info beside it (Priority, Status, Summary) I also notice that SFDC QA does not have any record of the Bugzilla Automation user logging into SFDC QA (unsuccessfully or not). That makes me think that something else on the Bugzilla side is not configured as it ought to be. Is it possible that the QA credentials are not present on bugzilla5.redhat.com? And is there any logging that'd be available to show what happens when a link is attempted on Bugzilla to an SFDC case?
Daniel can you confirm what the QA access server is? We had it configured as access.webqa.redhat.com which doesn't exist. I tried access.qa.redhat.com and I was unable to login.
Created attachment 1474536 [details] Bugzilla Automation Login Failed
I've reset the password. Can you test again?
Good news: I can see comments being transmitted from https://bugzilla5.redhat.com/show_bug.cgi?id=1204948 to SFDC QA case 01905773 Bad news (but probably manageable): The message that was sent didn't include an 'author'. So SFDC shows comments originating from Bugzilla as having been composed by 'null'. That's undesired, but it can be fixed by having the SFDC client to the message that Bugzilla is sending use 'creator' instead of 'author'. And I hope to create an SFDC Ticketing Bug to track ^^^. (I also hope to do a bit more thorough testing in the near-future, but I'm glad this particular hurdle seems to have been worked around!)