Talk:Bug tracking system

message: Do people think that this should be a sub-section of Issue tracking system? I forget everything but you (talk) 14:08, 8 February 2008 (UTC)
replies: text: Just a point of note. There is nothing that says that a bug tracking system has to be a software application. It can be and has been done with pieces of paper (citation needed!). I do think there is some merit to merging this with Issue tracking system as strictly bugs are just one issue type. However there may also be merit to creating a page that deals with issue tracking/incident management for the software development environment. Any thoughts anyone? or should I just follow the wikipedia suggestion of being bold with my edits?! Hornsofthebull (talk) 15:57, 26 January 2009 (UTC)
thread_title: Merge

message: Hello fellow Wikipedians,
I have just modified  on Bug tracking system. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20141113131614/http://www.sitepoint.com:80/implement-client-side-bug-reporting-usersnap/ to http://www.sitepoint.com/implement-client-side-bug-reporting-usersnap/
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—InternetArchiveBot (Report bug) 11:17, 10 November 2016 (UTC)
thread_title:  External links modified 

message: Would probably be interesting to find out what the first bug trackers were and what prior solutions they replaced. 81.217.129.211 (talk) 16:44, 8 March 2023 (UTC)
replies: text: repri.190.162.11.1 177.228.52.92 (talk) 09:37, 28 April 2023 (UTC)
thread_title:  History section? 

message: I see the difference between the articles bug tracking system and issue tracking system. The former is generally used very internally by developers and the latter used for tracking externally reported issues; from users. But, a bug is an issue, right? So, it's confusing, right?
I get it. Tooling is usually different for the two use cases. But, I struggle with whether these two things merit separate pages. And, is the distinction all that clear? Maybe it is for some tools and organizations, but IMO that is more marketing and positioning than a aspect of software development.
I think this is a case of codifying terms that are not that firmly engrained in the world. For example, Bugzilla calls it tool "defect-tracking system, or bug-tracking system". Jira calls its tool "project management tool". Azure Devops says "It allows organizations to create and improve products at a faster pace than they can with traditional software development approaches" so it's a "software development approach". At the end of the day tracking issues is something that is done in the world. But, it's not always done with a thing called a "bug tracking system" or "issue tracking system". Those terms are used sometimes, but many different terms are used for basically the same thing.
Further, is there really that much to say about these tools? Of course there is much that could be said. But, without getting into all the particular tools (and their sales pitches), what is there to say at a high level?
Maybe both pages should redirect to software bug where there's a section on tracking tools; i.e. the existing Management section. Stevebroshar (talk) 11:09, 30 April 2024 (UTC)
thread_title:  Issue, bug, change tracking