Bug Tracking Tool
-
ontime by axosoft has 3 options you mentioned check seapine also.
_________________________ "When the superior man refrains from acting, his force is felt for a thousand li." Sun Tzu
It is a little expensive for me.
Abhishek theBOKA It is impossible to change your past. But it is very possible to ruin your present by worrying about the future. -Chankya
-
Really cool. As light weight as it can me. Thanks a lot for the link.
Abhishek theBOKA It is impossible to change your past. But it is very possible to ruin your present by worrying about the future. -Chankya
AbhishekBK wrote:
Thanks a lot for the link.
You're welcome. :)
With respect, I must disagree. A quick look at middle management in just about any corporation shows that the dodo not only survived, it's reproducing in record numbers. Christopher Duncan
-
Well I think you are crazy to go and develop Yet Another Bug Tracking Tool but if you must then you should do all three options. It should be accessible via a URL, should have a standalone, native OS app and it should have an IDE plugin. It should also accept and send out emails, use RSS, have a mobile view and work across platforms (our small team is a mix of Linux, Mac OS X and Windows.) Frankly, I wouldn't bother. I'd use trac or Fogbuz.
regards, Paul Watson Ireland & South Africa
Shog9 wrote:
And with that, Paul closed his browser, sipped his herbal tea, fixed the flower in his hair, and smiled brightly at the multitude of cute, furry animals flocking around the grassy hillside where he sat coding Ruby on his Mac...
Paul Watson wrote:
go and develop Yet Another Bug Tracking Tool
Pronounced "YabTitty"
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Paul Watson wrote:
go and develop Yet Another Bug Tracking Tool
Pronounced "YabTitty"
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Well, a few days ago I was asking people about a bug tracking tool. A lot of people here came up with some links. I went through all of them but none of them were able to satisfy my needs. I am a development lead of a product development team and the productivity of my entire team depends heavily on clarity on which are the important tasks and which are the not so important tasks. However, my team size is very small around 5. And I don't plan to work with a team that is bigger than 10 or 15 in size in the long run as well. Hence I need something that is very compact and does its job well. Most tracking systems that I came across were either for extremely large projects or had a steep learning curve or were pretty expensive for my needs. So, I am thinking if I should write a bug tracking tool myself. I believe it is quite a simple thing to develop provided the objectives of the tool are identified appropriately. But I am unable to decide on if should it be a 1. Web application 2. Windows Application 3. VS Add-in Any Ideas?
Abhishek theBOKA It is impossible to change your past. But it is very possible to ruin your present by worring about the future. -Chankya
Well we at FeedGhost use a web based bug tracking tool called BugTracker.Net. It's fine for our needs (2 developers). Regards Lee
-
Well, a few days ago I was asking people about a bug tracking tool. A lot of people here came up with some links. I went through all of them but none of them were able to satisfy my needs. I am a development lead of a product development team and the productivity of my entire team depends heavily on clarity on which are the important tasks and which are the not so important tasks. However, my team size is very small around 5. And I don't plan to work with a team that is bigger than 10 or 15 in size in the long run as well. Hence I need something that is very compact and does its job well. Most tracking systems that I came across were either for extremely large projects or had a steep learning curve or were pretty expensive for my needs. So, I am thinking if I should write a bug tracking tool myself. I believe it is quite a simple thing to develop provided the objectives of the tool are identified appropriately. But I am unable to decide on if should it be a 1. Web application 2. Windows Application 3. VS Add-in Any Ideas?
Abhishek theBOKA It is impossible to change your past. But it is very possible to ruin your present by worring about the future. -Chankya
Would Visual Studio Team System suffice in that regard?
"A good athlete is the result of a good and worthy opponent." - David Crow
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
-
Well, a few days ago I was asking people about a bug tracking tool. A lot of people here came up with some links. I went through all of them but none of them were able to satisfy my needs. I am a development lead of a product development team and the productivity of my entire team depends heavily on clarity on which are the important tasks and which are the not so important tasks. However, my team size is very small around 5. And I don't plan to work with a team that is bigger than 10 or 15 in size in the long run as well. Hence I need something that is very compact and does its job well. Most tracking systems that I came across were either for extremely large projects or had a steep learning curve or were pretty expensive for my needs. So, I am thinking if I should write a bug tracking tool myself. I believe it is quite a simple thing to develop provided the objectives of the tool are identified appropriately. But I am unable to decide on if should it be a 1. Web application 2. Windows Application 3. VS Add-in Any Ideas?
Abhishek theBOKA It is impossible to change your past. But it is very possible to ruin your present by worring about the future. -Chankya
AbhishekBK wrote:
I believe it is quite a simple thing to develop provided the objectives of the tool are identified appropriately.
The world is littered with shops using half assed software that they thought was "quite easy to develop". If you truly think this even though there are excellent inexpensive products out there such as FogBugz and you feel that your time is less valuable than a couple hundred dollars for a pre-made fully working solution and you delight in re-inventing the wheel then I wish you the best of luck and my personal preference would be a web application.
"I don't want more choice. I just want better things!" - Edina Monsoon
-
Would Visual Studio Team System suffice in that regard?
"A good athlete is the result of a good and worthy opponent." - David Crow
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
I think he mentioned something about "cheap".
Todd Smith
-
I think he mentioned something about "cheap".
Todd Smith
I get your point, but "cheap" is one of those words whose meaning depends on to whom you are speaking. Also, if the person happens to be an MSDN subscriber, they may already own the tool for which they seek. :)
"A good athlete is the result of a good and worthy opponent." - David Crow
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
-
AbhishekBK wrote:
I believe it is quite a simple thing to develop provided the objectives of the tool are identified appropriately.
The world is littered with shops using half assed software that they thought was "quite easy to develop". If you truly think this even though there are excellent inexpensive products out there such as FogBugz and you feel that your time is less valuable than a couple hundred dollars for a pre-made fully working solution and you delight in re-inventing the wheel then I wish you the best of luck and my personal preference would be a web application.
"I don't want more choice. I just want better things!" - Edina Monsoon
Well, the world is also littered with software shops that think that a good tool can work for every body. Here is a set of my requirements: 1. I need a bugs list where through a Developer login (Tester + Programmer) the bugs get reported by people seriously perusing the development and fixing of bus. The bug report needs to be effective. But not unnecessarily detailed. The bugs list can also be populated by users who can say what problems they are facing through a web interface, preferably through a page in my website. 2. I need a features list, where developers can write the features they can think of and maintain a database of ideas to enhance their product. The same list will also accept features request from users, preferably through a web interface again. 3. I need a marketeer login where marketers go ahead and write their evaluation of how much the market values which feature feature. They can suggest what features the market reacted to very very well and which were not so well accepted. 4. A project sponsor log in for the people at the top to get an over view of the whole development process and give high level directives as to what to do next with the project. Plus, I want the application to only this. Nothing more. Please share your thoughts on this.
Abhishek theBOKA It is impossible to change your past. But it is very possible to ruin your present by worrying about the future. -Chankya
-
Well, the world is also littered with software shops that think that a good tool can work for every body. Here is a set of my requirements: 1. I need a bugs list where through a Developer login (Tester + Programmer) the bugs get reported by people seriously perusing the development and fixing of bus. The bug report needs to be effective. But not unnecessarily detailed. The bugs list can also be populated by users who can say what problems they are facing through a web interface, preferably through a page in my website. 2. I need a features list, where developers can write the features they can think of and maintain a database of ideas to enhance their product. The same list will also accept features request from users, preferably through a web interface again. 3. I need a marketeer login where marketers go ahead and write their evaluation of how much the market values which feature feature. They can suggest what features the market reacted to very very well and which were not so well accepted. 4. A project sponsor log in for the people at the top to get an over view of the whole development process and give high level directives as to what to do next with the project. Plus, I want the application to only this. Nothing more. Please share your thoughts on this.
Abhishek theBOKA It is impossible to change your past. But it is very possible to ruin your present by worrying about the future. -Chankya
Well that's your problem right there. You started a thread asking about a bug tracking tool, then went on to add all sorts of things that are quite clearly not bug tracking related. Fogbugz will take care of 1 and 2 nicely. 3 and 4 are obviously completely unconnected to bug tracking and will require a different product that will obviously (well it should be obvious) be designed for other purposes but allow enough leeway for you to use them as you wish. Perhaps some general purpose contact management style app that is highly customizable with extra database fields. Your comment at the bottom:
AbhishekBK wrote:
Plus, I want the application to only this. Nothing more.
Is highly amusing because you are clearly after something that doesn't exist and so you are going to have to make do with what is already out there which means it will obviously do a lot more than what is on your list depending on what the software was originally designed for. By the way I *highly* recommend that you do not use that terminology with software companies if you are enquiring about their products because they will automatically put you in the "dick" category for being arrogant and annoying and will likely not help you as well as they could if you would just accept that the world will not necessarily cater to your wishes and some effort will be required on your part to adapt and work with what is already out there. I know you may very well have not intended to be offensive with that statement but be aware it will come across that way. Bottom line is you want something that I can almost gurantee you does not exist in one software package and so you are left with writing something yourself or hiring someone to do it. As a developer of a product that is easily as complex as what you are after I can tell you that to do it right is going to require several developers working a year or more. If you just want to get going then I suggest you take your attitude down a notch, adopt a more humble frame of mind and take a *realistic* look at more than one product that will do the different tasks separately and accept that they may well have features that you will not use.
"I don't want more choice. I just want better things!" - Edina Monsoon
-
Well that's your problem right there. You started a thread asking about a bug tracking tool, then went on to add all sorts of things that are quite clearly not bug tracking related. Fogbugz will take care of 1 and 2 nicely. 3 and 4 are obviously completely unconnected to bug tracking and will require a different product that will obviously (well it should be obvious) be designed for other purposes but allow enough leeway for you to use them as you wish. Perhaps some general purpose contact management style app that is highly customizable with extra database fields. Your comment at the bottom:
AbhishekBK wrote:
Plus, I want the application to only this. Nothing more.
Is highly amusing because you are clearly after something that doesn't exist and so you are going to have to make do with what is already out there which means it will obviously do a lot more than what is on your list depending on what the software was originally designed for. By the way I *highly* recommend that you do not use that terminology with software companies if you are enquiring about their products because they will automatically put you in the "dick" category for being arrogant and annoying and will likely not help you as well as they could if you would just accept that the world will not necessarily cater to your wishes and some effort will be required on your part to adapt and work with what is already out there. I know you may very well have not intended to be offensive with that statement but be aware it will come across that way. Bottom line is you want something that I can almost gurantee you does not exist in one software package and so you are left with writing something yourself or hiring someone to do it. As a developer of a product that is easily as complex as what you are after I can tell you that to do it right is going to require several developers working a year or more. If you just want to get going then I suggest you take your attitude down a notch, adopt a more humble frame of mind and take a *realistic* look at more than one product that will do the different tasks separately and accept that they may well have features that you will not use.
"I don't want more choice. I just want better things!" - Edina Monsoon
I am not trying to be rude. At the same time, I will show you respect only if you ensure the same. Whatever "dick" category you are talking about, I haven't fallen into. Neither am I afraid of falling in that category in somebody's books who not understand my requirements totally. You have actually done me great service by letting me know that nothing of this kind exists. That has furthered my motivation in developing something like this. It may not be called a bug tool. Possible. But that does not make my requirements go away. The idea behind the tool is that, in most small teams there is always a trade off between fixing bugs and writing new features. Unlike, large software companies, the development team size does not fluctuate with new requirements. This is where a true reflection of the bug vs feature debate needs to be considered in greater light. As to points 3 and 4 not being a part of the features list of a "bug tracking system" I accept. But I still maintain that it does not call for unparliamentary language. Finally, your estimates of this thing taking several developers more than a year to develop is way off my estimates. This perhaps because, you don't seem to really see the "threadbareness" of the application in my mind.
Abhishek theBOKA It is impossible to change your past. But it is very possible to ruin your present by worrying about the future. -Chankya
-
I am not trying to be rude. At the same time, I will show you respect only if you ensure the same. Whatever "dick" category you are talking about, I haven't fallen into. Neither am I afraid of falling in that category in somebody's books who not understand my requirements totally. You have actually done me great service by letting me know that nothing of this kind exists. That has furthered my motivation in developing something like this. It may not be called a bug tool. Possible. But that does not make my requirements go away. The idea behind the tool is that, in most small teams there is always a trade off between fixing bugs and writing new features. Unlike, large software companies, the development team size does not fluctuate with new requirements. This is where a true reflection of the bug vs feature debate needs to be considered in greater light. As to points 3 and 4 not being a part of the features list of a "bug tracking system" I accept. But I still maintain that it does not call for unparliamentary language. Finally, your estimates of this thing taking several developers more than a year to develop is way off my estimates. This perhaps because, you don't seem to really see the "threadbareness" of the application in my mind.
Abhishek theBOKA It is impossible to change your past. But it is very possible to ruin your present by worrying about the future. -Chankya
AbhishekBK wrote:
I am not trying to be rude. At the same time, I will show you respect only if you ensure the same. Whatever "dick" category you are talking about, I haven't fallen into. Neither am I afraid of falling in that category in somebody's books who not understand my requirements totally.
I understand and that's why I stated that I didn't think you were trying to be a "dick" your tone of phrase just came across that way. It personally angered me in a small way because we sometimes get people emailing us enquiring about our software and they are harsh with us in their tone because they feel that our software's features are not perfectly written for exactly their requirements which is of course unrealistic and I find very annoying personally.
AbhishekBK wrote:
Finally, your estimates of this thing taking several developers more than a year to develop is way off my estimates. This perhaps because, you don't seem to really see the "threadbareness" of the application in my mind.
:) We'll see. What you described is right up my alley so to speak. It's directly within my area of expertise and I'll grant that you could make a very threadbare application in no real time at all, it's usefullness would perhaps be equally threadbare. I say this from personal experience having used a system we wrote and added on to over the years but never really had the time to perfect because it was nothing more than an in-house tool and you can never spend more effort on in-house tools than you can on the software you are actually producing for your customers or you will quickly go out of business. I've learned over the years that if you want to have happy customers, happy staff and make money you are best served by buying every thing you need wherever possible instead of creating it yourself. Even as little as one month of solid programming time, even one week, spent on an in-house tool could translate into a *lot* of profit for the company if that time was invested in the product you produce for your customers instead. The only possible justification for investing any amount of time writing something that you can simply go out and buy is if you do it as a product that you intend to resell, that's where my time estimate came into the picture. Bug versus feature is really a practical matter that no software can do more than help keep a list for you and you can as easily do that on paper o
-
AbhishekBK wrote:
I am not trying to be rude. At the same time, I will show you respect only if you ensure the same. Whatever "dick" category you are talking about, I haven't fallen into. Neither am I afraid of falling in that category in somebody's books who not understand my requirements totally.
I understand and that's why I stated that I didn't think you were trying to be a "dick" your tone of phrase just came across that way. It personally angered me in a small way because we sometimes get people emailing us enquiring about our software and they are harsh with us in their tone because they feel that our software's features are not perfectly written for exactly their requirements which is of course unrealistic and I find very annoying personally.
AbhishekBK wrote:
Finally, your estimates of this thing taking several developers more than a year to develop is way off my estimates. This perhaps because, you don't seem to really see the "threadbareness" of the application in my mind.
:) We'll see. What you described is right up my alley so to speak. It's directly within my area of expertise and I'll grant that you could make a very threadbare application in no real time at all, it's usefullness would perhaps be equally threadbare. I say this from personal experience having used a system we wrote and added on to over the years but never really had the time to perfect because it was nothing more than an in-house tool and you can never spend more effort on in-house tools than you can on the software you are actually producing for your customers or you will quickly go out of business. I've learned over the years that if you want to have happy customers, happy staff and make money you are best served by buying every thing you need wherever possible instead of creating it yourself. Even as little as one month of solid programming time, even one week, spent on an in-house tool could translate into a *lot* of profit for the company if that time was invested in the product you produce for your customers instead. The only possible justification for investing any amount of time writing something that you can simply go out and buy is if you do it as a product that you intend to resell, that's where my time estimate came into the picture. Bug versus feature is really a practical matter that no software can do more than help keep a list for you and you can as easily do that on paper o
John Cardinal wrote:
Bug versus feature is really a practical matter that no software can do more than help keep a list for you and you can as easily do that on paper or a spreadsheet if you want "threadbare".
Exactly. Spreadsheets are good enough. But imagine a spreadsheet which sends you an email when something has changed + does not show fixed bugs + keeps track of the status throughout the life of the bug and records it for viewing later. That's a good enough bug tracking system for me.:)
Abhishek theBOKA It is impossible to change your past. But it is very possible to ruin your present by worrying about the future. -Chankya
-
John Cardinal wrote:
Bug versus feature is really a practical matter that no software can do more than help keep a list for you and you can as easily do that on paper or a spreadsheet if you want "threadbare".
Exactly. Spreadsheets are good enough. But imagine a spreadsheet which sends you an email when something has changed + does not show fixed bugs + keeps track of the status throughout the life of the bug and records it for viewing later. That's a good enough bug tracking system for me.:)
Abhishek theBOKA It is impossible to change your past. But it is very possible to ruin your present by worrying about the future. -Chankya