View Full Version : Sending to FogBugz
I have signed up with FogBugz (trial) and am trying to send a error report to it.
The problem is that it pops up a disconnecting form and hangs.
Is there a way to test sending a bug to FogBugz (maybe via a web page ) to see if I have all the fields set up correctly?
admin
02-Oct-2007, 06:56 AM
Hi,
can you send to me a little source demo that uses the same FogBugz trial account and data, able to reproduce this issue, please?
I sent you a link to the project did you get it?
I will send another private message.
admin
08-Oct-2007, 08:51 AM
Yes, I'm working on, please to be patient. :)
admin
08-Oct-2007, 04:02 PM
Hi Rob,
I'm happy to communicate you to have solved your issue.
Isn't an EurekaLog bug but only a your wrong EurekaLog configuration.
You have insert the FogBugz login data in the URL login.
The URL login must used only if the URL is protected by an UserName and Password (in this case the Web Page appears only after that the Browser asked you to insert this data).
After you have set as URL Port number 80, but the https ports is 443.
So reassuming you must:
1)...remove any data in the URL/User, URL/Password;
2)...change the URL port from 80 to 443;
3)...set the correct user/Password in the "Web Bug Tracker" user/Password fields (using FogBugz user/password);
4)...remove the "Trial ID" field (because in my try it works as a full account).
I hope to have finally solved your problem! :)
Unregistered
13-Aug-2008, 05:18 AM
Hi I have just downloaded the latest Trial version on Eureka logs.
From my brief experience it seems like an excellent program. I will be purchasing the product asap.
I have been attempting to integrate Eureka Logs and FogBugz however the web submit refuses to authenticate to the FogBugz submit page. Even following your instruction abive this fails.
Has anyone else experienced any issue with FogBugz 6.0 ?
Also there is a bug in the Web Tracking settings. If you do not set a password it complains that there is no project name set?
admin
22-Aug-2008, 10:27 AM
Hi,
I have just fixed this issues in the last 6.0.16 RC 5 version.
Try it and tell back to me your results, OK? :)
vBulletin® v3.8.2, Copyright ©2000-2012, Jelsoft Enterprises Ltd.