tohndef

I currently use a bug writing program for work that's modeled after bugzilla that I can't stand. I'd like to create my own bug reporting software that can do more but I don't know where to start. Can anybody offer me their advice?

I'm only slightly familiar with C++ and Java, but am determined to start down the best path towards making a better bugging program. Any suggestions general or specific will be appreciated.

grumpy

General comment: you're putting the cart before the horse. Those who follow such a horse only see a horses behind that is going nowhere.

Bug tracking software like Bugzilla is a tool used to manage the process of identifying, tracking down, and fixing bugs. Solid experience with managing the process of identifying, tracking down, and fixing software bugs in a team environment is an essential prerequisite for designing and writing any useful bug tracking software.

If you're only slightly familiar with C++ and Java, you probably have only had a little bit of practice with programming. A little bit of practice with programming means you have very little experience with identifying, tracking down, or fixing software bugs in relatively small software configuration items. You will need quite a bit of practice with systematically identifying, tracking down, and fixing software bugs before you will even have a hope of managing a team going through such processes. Once you have some significant experience with managing a team though such processes, you will have enough useful knowledge to begin the process of designing tools to help manage the process.

Until you have those sorts of experience, I suggest you suck in your pride, and use tools like Bugzilla. They may seem painful but, until you have solid experience, you will not be in a position to identify what features of Bugzilla software cause you pain for a good reason (ie the authors of Bugzilla know something you don't) and what features are candidates for improvement.

tohndef

Just cause I'm weak on the programming end doesn't mean I don't have some solid experience. I've been using the program I speak of for nearly 4 years now on a professional level, and I have some very specific ideas and enhancements in mind. I admit that I don't have all the necessary experience you suggest, but I feel that it's enough so that I can justly continue down my path of knowledge.

Can you recommend appropriate languages or concepts that I can research for developing a good issue database that can be accessed across our network and that offers powerful searching tools or the ability to create them.

I understand that I'm being very general, but like I said I'm determined to get this one off the ground. I believe that if someone like you can steer me in the right direction, then I can find the right person at my company to support me as needed and eventually take over the project once I am able to convey all the things I want this program to do.

Thanks for your input, grumpy.

grumpy

The core concept I suggest you pursue, tohndef, is the writing of a business case. In it, identify the weaknesses of packages you're using, the impact of those weaknesses, your strategy for addressing them, the benefits of doing so (eg reduced development time, ability to sell the tool and make profits), the skills you or a team need to do it, and the costs (manpower, software licenses, etc) of implementing it.

The first person to lobby would be your immediate manager and/or his immediate manager. Convince them to take ownership, and then support them in building and refining the business case to take to their managers. Eventually, by working up the management tree, you will reach someone who can approve resources to do the work and, if you and the various levels of management can convince them the benefits outweigh the costs, you're golden.

tohndef

Intriguing. I appreciate the customized plan to actually see this thing through. I would not be the first person to suggest new bug reporting software for our company though. The idea has been shot down too many times for me to approach anyone without a slightly more developed plan.

I want to learn more about where a professional programmer would get started. People in other forums are suggesting I consider a web-based program so I don't have to install on every machine and anyone in the world can access it, but there aren't so many machines that this would be a problem for us. I'm weary of the web-based idea because I imagine it will be slower and I don't need anyone outside of our local network to gain access anyways. Also, our bugs are regarding some highly confidential products that I wouldn't want to risk making available to some hacker.

Another forum member is suggesting I not start from scratch and instead build off something like bugzilla or mantis, but I want this program to have it's own look and I don't want extra stuff in there that our company doesn't need.

I've got time on my hands and a desire to learn more about programming. This project is only my own idea for now, so please, turn me towards a good book or recommend a tutorial to get the cogs turning -the only urgency on my end is to gain a clearer understanding of what will be under the hood.