|
We are using a home made system - made 15 years ago and extended with web portal 10 years ago...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
That's quite a mature system.
Is it non-intrusive ie - not annoying to use?
Just curious.
Thanks for the feedback.
|
|
|
|
|
As it was originally tailored for our support team and matured with that team (with additions and fixes per request) it is very easy to use - for the team at least. I can't promise that everyone will find it easy-to-use, after all it has a rather old UI...
But for us it is the best...Now that there is a plan to move to JIRA we all scared a bit...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
BugZilla and notepad
|
|
|
|
|
I've used
- TFS
- BugZilla
- OnTime
- Axosoft
- Excel
- One Note
- A homegrown app I wrote
and some other one too
If it's not broken, fix it until it is
|
|
|
|
|
|
Bugzilla[^]. It sucks, but to be fair the same can be said of every single bug tracking system I've ever worked with.
|
|
|
|
|
Nemanja Trifunovic wrote: It sucks,
Thanks for feedback on Bugzilla.
Also, that is the same thing I've found. They all mostly suck.
|
|
|
|
|
Ever heard of Fogbugz [^]? I can recommend it for small to not-so-small teams.
|
|
|
|
|
I've heard of Fogbugz because I've heard of Joel On Software.
Thanks for the feedback.
|
|
|
|
|
That's what my office uses, and it's..."adequate".
But then, I haven't used that many alternatives, so it's not really fair of me to put it down as I honestly wouldn't know what to suggest to make it better.
Maybe I'm just biased because every time I open it there's more work coming my way. But then, nobody opens cases to say everything's fine...
|
|
|
|
|
We use JIRA by Atlassian.
It is Web-based, with great pricing that scales with the team size and budget needs.
Features many useful plugins accessible via a Plugin Store[^]. Some are free, some are paid.
Hope it helps!
Max
|
|
|
|
|
The other Max approves.
I'd rather be phishing!
|
|
|
|
|
... as does the one with three Xs
PooperPig - Coming Soon
|
|
|
|
|
We are going to switch to JIRA in a few months... I'm glad to hear it is good...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Thanks for the feedback. I see your comment us upvoted by someone else too, so maybe they are chiming in that JIRA is not too bad?
|
|
|
|
|
Used Jira in my last job and it was one of the better systems I have used.
(Team I currently work with are using TFS, it appears adequate.)
|
|
|
|
|
|
We use Jira, as well. It works great for what we need it for, and it integrates well with some of our other tools.
|
|
|
|
|
|
Great link. Didn't know that existed. Thanks very much. Sorry for the rerun.
|
|
|
|
|
Have found several circular references here.
Answers to many questions are found here itself, so CP is kind of a self-sufficient universe. No need of Google, Bing, etc.
|
|
|
|
|
FogBugz baby yeah!
|
|
|
|
|
|
Just to chime in here, I'm quite happy nowadays using GitHub's issue tracker. And it was painless[^] to integrate into the client's website, so they can keep tabs on issues.
That said, I've worked with several others, and as others have posted, they all pretty much suck. One day I will write a decent bug tracker, one that is configurable to the project needs, isn't dog slow, doesn't clutter your screen with a ton of "I don't give a sh*t about that field", is interactive rather than just statically showing issues, easily quantizable (think "sprints" but don't think "sprints")
And by interactive, I mean being able to say "here's some issues I'll be working on" and it could ask how progress is going, what issues / dependencies have been encountered, etc.
Marc
|
|
|
|