|
Wow! Didn't know that one. Thanks! 
And it appears to be one of the most popular articles here.
Your time will come, if you let it be right.
|
|
|
|
|
I know it's TFS, but just had to mention it... 
|
|
|
|
|
Just kidding
It is Bugzilla, but I would hardly call it a "fave".
|
|
|
|
|
We started using JIRA a couple months ago after years of using a custom template inside Microsoft Groove.
All is going well; but we still have to streamline our workflow.
We are still evaluating and formalizing the usage of the plugins "Crucible" for code review and "FishEye" for code management.
I'd rather be phishing!
|
|
|
|
|
yellow is my preferred color.
|
|
|
|
|
an the jump bar recognizes it.
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
To be honest, My present work doesn need too much formal tracking system.
Excel sheet works well for my need
cheers,
Super
------------------------------------------
Too much of good is bad,mix some evil in it
|
|
|
|
|
Only because we tied into them just before TFS came out.
|
|
|
|
|
Does my Inbox count?
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
Your time will come, if you let it be right.
|
|
|
|
|
We have a 15 year old in-house bug tracker and patch creator duo (made in VB) still running well...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I inherited it from the people that came before me. They were just allergic to the word "bug", so they renamed it Task tracker.
|
|
|
|
|
The senior developers aren't developers, so they tend to not use tools different from text editors and e-mail.
There is to say that our team is small (4 people dividend in 2 subteams), the work is frantic and the differences between each instance of the same software are such that this system works - at least it has a flat learning curve and gives absolutely no problem of integration as there is none!
Geek code v 3.12
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++*
Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Instead each project has a text based TODO list which records outstanding mods, internal changes and bugs. Those are transferred to the mods history when they are fixed. The file itself (and the revision history text file) are part of the VS project, and are built into the EXE / DLL when it is compiled.
Since there is only me, I don't need anything more sophisticated.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
You pretty much described my situation, with the only difference that we are in two 
Geek code v 3.12
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++*
Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Well, that is my way too.
"I have not failed. I've just found 10,000 ways that won't work." Thomas A. Edison
"Politicians and diapers should be changed often and for the same reason." Eça de Queiroz (1845 - 1900)
|
|
|
|
|
Bacon flavoured CListCtrl! 
|
|
|
|
|
So you generate a lot of bugs just so you can eat 'em? 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Of course! YUMMY!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
