Loading Profile...
Twitter,
Facebook, or email.
I’m
puzzled
Why can't I refresh downloaded bugzilla data?
Scrumworks V4.3 is unable to refresh Bugzilla d ata and is unable to clearly describe why or what to do in order to rectify the problem. Database has been installed for several years, recently upgraded to V4.3 and was still able to update Bugzilla data. Then one day, it stopped working. I get the error message to Duplicate the exact filter syntax in Bugzilla with the same login for the specific error information. I have no idea where the filter syntax is located, nor how to use it with the Bugzilla interface once I find it. No problem downloading new items or updating a single PBI (via the Editor's Downloaded Data tab) from the same Bugzilla server.
-
Hi Mikey,
I will see if I can duplicate this issue.
Can you tell me which version of Bugzilla you are currently running?-
mikey April 09, 2010 17:033.0.2EditDeleteRemove
-
-
-
-
-
Hi Mikey,
I haven't been able to duplicate the issue on my system here, I will need to pass this along to the development group. I will need to gather some information to do so. Could you send the following to support@danube.com?
A copy of your log file, located at installdirectory\server\scrumworks\log\server.log
The output from your desktop client's Help - About ScrumWorks Pro menu.
The third thing is a bit more complex, basically we need the output from the Java Console while you are attempting the refresh. You can enable the console following the steps in this topic: http://community.danube.com/danube/to...
After the console is enabled close ScrumWorks and start it back up again, you should get an additional console window when you do. When you try the refresh again it will hopefully give us some output as to exactly what is going wrong. If you can send that output that should be what I need to pass this up to the team. -
-
Just an update on this issue.
The development group has made a change, which will roll out with release 4.4 that resolves the problem.
Mike reported that he was able to temporarily resolve the issue by increasing Apache's LimitRequestLine setting to 10k (up from 8k > default). -
-
-
EMPLOYEE
EMPLOYEE
