Hi there,
I know it’s a bit off topic, but even though it is an important question to me and maybe others, too…
I’ve got a question to all you IT gurus out there:
What kind of Bug Tracking System do you use to manage your applicatios in use? Any recommendations?
Thanks in advance for any hints!
Michael
Subject: Bug Tracking System?
I have a system that gets added to all the LotusScript in a database. It tracks where you are and what documents you’re working on. When there’s a LotusScript error the error is captured and logged in a database. The module, line number, and error message are recorded. Also the notes document that was being processed is stored in the log database and linked to the log document. Then the system sends me an email.
The system can also automatically generate a help desk ticket for the person that generated the error so support can follow up on it. It’s amazing how users will get used to messages such as “Object variable not set” or “Subscript out of range” and not do anything about them when they pop up.
With this system I can follow up on LotusScript problems in both the Notes client and web processes. Because of this I have very little formula in my forms. I do everything with LotusScript.
I’ve been meaning to develop a similar system for formula but I’ve found that rewriting the formula as LotusScript is just better. But I will create something at some point for those times when you have no choice but to use formula. Usually in those instances the code is short and fairly solid, so not having a system hasn’t been a problem.
Subject: RE: Bug Tracking System?
Open Log from OpenNtfhttp://www.openntf.org/Projects/pmt.nsf/0/631EE33A6D328831C1256E3A003B4268
JYR
Subject: RE: Bug Tracking System?
Yeah I’ve seen that. It’s nice but I like mine better because I needed more than just recording the details of the error ad-nauseam. I needed to record the actual documents that cause the error, as well as features to ensure data integrity. My process first stores a pre-processing version of the document. Then when an error occurs it stores a version a current version of the document. That way I can examine actual values of fields at the time of the error and I can test code on the document that cause the error. I’ve found that users will go in and still try to change the document after they’ve received errors because they have to get their work done…so they try again and again. By the time I review the document the data may have been updated several times.
Data integrity was also an important feature I needed. When an error occurs I use the pre-processing document versions to back out any updates that were made by the code. This enhances data integrity by not leaving half-processed documents in an unknown state. This is important because, as I said, users will try over and over when receiving an error…they can end up increasing damage to data without knowing it.
When OpenLog does all that I’ll consider it.
Subject: RE: Bug Tracking System?
OpenLog is freely available to anybody and can be implemented by inheriting one LotusScript library and calling one parameterless LotusScript function. Capturing additional arbitrary information (including doc links to failing documents) however requires you to take the hassle and pass no less then three (!) arguments to a different (!) function. It can also capture Java and JavaScript errors. When your solution does that, I’ll consider it. 
I still wonder, if this really is, what Michael was asking for …
Subject: RE: Bug Tracking System?
Yes, you are right. What I asked for were any hints, experiences etc. regarding Bug-Tracking Systems like BugZilla, Jira or Mantis - or Help from openntf…
But asit is a bit off-topic I didn’t expect too much information in this forum. If there is anybody who uses one of the systems I mentioned - or any other system - I would greatly appreciate any kind of information about your experiences.
Regards, Michael