- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Wait, what? I think Paula is broken...she unlisted this one!
I appreciate the time you spent.
Admin
Don't worry; there's still a chance for her to screw up. She'll probably create a duplicate comment topic when the article is published.
Admin
I really hope
BUGREP-92726was just flavor, or this was a really old JIRA instance. 92k bugs is quite a feat!Admin
Given the code in TFA, I believe it!
Admin
I've seen bug numbers much higher than that, but the tracking system was shared across countless projects through many years. It was also used for things that weren't bugs, like documenting questions about how something is supposed to work, or tracking things like "These are the issues that remain before project X can say they've reached milestone Y," and assigning ARs for each of those issues.
Admin
I think they started at some really high number, like 1,000.
Btw, I wonder whether Ancient Coder's native language is Hebrew or some Slavonic or some other language that doesn't have present forms of to be as auxiliary verb.
Admin
We're near 10k now, but only because most of our team members use our bug tracker as their personal TODO list. Also, whenever our NFS share goes down (which is way too often, because some people think that writing 32GB core dumps to NFS is a good idea), hundreds of tickets are automatically created by Jenkins (one for each build job that failed).
Admin
We have more than that, but we've split it across different Jira projects (over the course of about 8 years) which all have independent numbering. One is internal to us, one we share with the customer, one is basically theirs and another is focused on ops.
Admin
Go, Go, Gadget Error Handler!
http://img09.deviantart.net/a089/i/2010/329/2/b/inspector_gadget_study_by_vdvector-d33k9db.jpg
Admin
"Go, go, errorGadget337", said Inspector Gadget, but only a pop and a quickly dying twirling whistle resulted.
While I was composing @dkf ?! Great minds think alike.
Admin
I think that about sums it up.
Admin
So the previous commenter(s) for this code were aware that they'd released patches which not only didn't fix the bug in question at the time but also created new bugs? Time to fire the [s]entire QA team[/s] PHBs who overruled the QA team to get to this state of affairs
Admin
Sometimes defeat is the only option.
Admin
I its justs mes ors i thes grammars ons thi articles brokens beyonds repairs? Wa its parts ofs thes originals submissions, ors whats?
Admin
Yup, this is nasty. I'm not even going to look at it when I have my own oodles of legacy code to maintain.
Admin
At my last gig, the Jira codes were up to 95000, and nobody thought that was bad. Many, many tickets similar to that one. Actually, any time I picked up a ticket, I usually found 3 to 5 new bugs while navigating to the ticket bug. A real gumption-trap!
Admin
Our jira project is up to 4k or so, originally only used for projects and tasks but nowadays bugs are mirrored to it as well. The bug tracker uses global numbers, has been active for 20 years or so, and is up to bug number 22 million or thereabouts.