Message-ID: <1642846928.1231.1429604559389.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1230_866527605.1429604559389" ------=_Part_1230_866527605.1429604559389 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
As with the seven deadly spiritual sins, you can find someone wh= o will argue that each of the coding sins is the worst of the seven. We won= 't argue that any of the sins is the worst, but we do believe Bugs and Pote= ntial Bugs is the most urgent. That's because this sin represents things th= at are going wrong in your code today or that may go wrong tomorrow. An unc= onditional null pointer dereference is a prime example of a bug (hopefully = the urgency is self-evident). Potential bugs are a bit more subtle, but no = less important.
Instances of this sin are tracked with the issues mechanism. Typically bugs and potential bugs will sho= w up as Blocker or Critical issues, although that's fully configurable. Coding Standards Breaches are also tracked as i= ssues, although typically at lower severities. Instances of the other = sins can optionally also be tracked using the issues mechanism (which offers some distinct advantages).
To monitor potential bugs, add the Issues and Technical Debt widget to your project dash= board if it's not there already:
Use the differential views&n= bsp;to monitor new issues.