Bug Tracking Tool
-
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, 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 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...
-
We find BugZilla more than adequate. We are a small team (7 developers) but we have a large in-house user base (a few hundred) who all have access to the database via their browser.
Any Bugzilla complaints? We find it to be a bit of a pig.
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...
-
We find BugZilla more than adequate. We are a small team (7 developers) but we have a large in-house user base (a few hundred) who all have access to the database via their browser.
Well is is not the presence of features but the absence of features I am looking at. I want some thing that is very clean. But to be frank I haven't looked at BugZilla carefully. But will definitely take a loot at it again. But I think the important point is the large user base that needs access from a web browser. Not all users will be interested in a software install.
Abhishek theBOKA It is impossible to change your past. But it is very possible to ruin your present by worrying about the future. -Chankya
-
Any Bugzilla complaints? We find it to be a bit of a pig.
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...
We messed with some of the fonts in the CSS to make it a little easier on the eye, but other than that, it just works for us. My only complaint is that when creating an initial bug report you can't add an attachment - you have to create the report first.
-
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...
Well a bug tracker is pretty much a function of your development methodology. No two companies follow the exact development methodology. It is important that your bug tracking tool truly reflects your development procedure. That is precisely why there are so many bug tracking tools out there, each one springs from a different perspective on software development. Thats precisely why i want to develop one of my own. Besides it is going to be great fun as well. :) But yes, I do see that it is going to be a lot of work.
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, 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 a bug tracker is pretty much a function of your development methodology. No two companies follow the exact development methodology. It is important that your bug tracking tool truly reflects your development procedure. That is precisely why there are so many bug tracking tools out there, each one springs from a different perspective on software development. Thats precisely why i want to develop one of my own. Besides it is going to be great fun as well. :) But yes, I do see that it is going to be a lot of work.
Abhishek theBOKA It is impossible to change your past. But it is very possible to ruin your present by worrying about the future. -Chankya
How about taking an existing solution and modifying it to your needs instead of writing a new one from the ground up? Trac is open source and easily modifiable. There is a lot of drudge work you will need to do that is the same between any two bug systems.
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...
-
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 went through all of them but none of them were able to satisfy my needs.
I never got a chance to toss this link in with the mix (from CP) -> Bugreporter[^]
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
-
AbhishekBK wrote:
I went through all of them but none of them were able to satisfy my needs.
I never got a chance to toss this link in with the mix (from CP) -> Bugreporter[^]
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
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
-
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