Logging bugs

I used to have some notes on the “best practices” for logging bugs, etc.
Wonder where it all went....


Programmers.StackExchange: Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?




I was satisfied with BugTracker.net from Corey Trager.
I used it for about 5-6 years at a former employer.
A co-worker originally installed it (not sure what version) and I did maintenance after he left.
I extended the code to add in some short-links to other info-systems we used, like a wiki and a project-management system.
This was an older version and was never really upgraded.
I hope to extend this concept into a more generic version, like PmWiki’s “intermap”.

But don’t get too carried away, lest it become a wiki itself.

Satisfied is faint praise, sorry about that.
There are certainly bug-tracking systems I’ve encountered that I do not like.
BugTracker did everything I needed.





I migrated an install from one machine to another with no problems.
Copied the database (detach, copy files, attach).
Copied the entire folder.
Set up virtual directory pointing to www, made application, set up app pool, made identity Network Service, granted permissions on www folder to app-pool identity (for writing log-files and attachments), updated web.config for new DB reference, and URL prefix (this had been wrong before, so does not seem to be a sticking point).



Visual editor

It uses the ckeditor


Ugh. The “visual” editor drives me bananas.
And it’s displaying everything in monospace.
How can I change that?
I’d like to display only selected items (code-fragments) in monospace.



TODO: is it possible to get a default organization? Or am I using the wrong schemas?
Default project can be set, but projects are usually below and organization.
IE, any given organization has multiple projects.
I’d like to set a default project for an organization, and possibly even a default organization.


Bug Relationships

Did I miss this somewhere in the documentation?
Relationship are mentioned here, but they are disabled by default.
Go into web.config and update the value of <add key="EnableRelationships" value="0"/> to 1


All change history

By default (?) some changes are not displayed -- addition of custom fields, relationships, status change, assignments, etc.
I can’t find a global setting to change this.
There is a link on each bug to enable the display: show change history|hide change history
This will store the setting to effect all other bugs the user views.
I haven’t dug into the code to see if this is stored in the back-end, or in the browser (cookie or local-storage).



Time to move BugTrackerDotNet to its own page....




Here’s a sample query I’ve set up, overwhelmingly based on the default open bugs query.
I found that referencing the st_name directly gave more clarity, and it was already present in the query.
Pay no heed to the exact list of ignored statuses, as my list of statuses is up in the air.


SELECT isnull(pr_background_color,'#ffffff'), bg_id [id], isnull(bu_flag,0) [$FLAG],
bg_short_desc [DESC], isnull(pj_name,'') [project], isnull(og_name,'') [organization], isnull(ct_name,'') [category], rpt.us_username [reported BY],
bg_reported_date [reported ON], isnull(pr_name,'') [priority], isnull(asg.us_username,'') [assigned TO],
isnull(st_name,'') [STATUS], isnull(lu.us_username,'') [last updated BY], bg_last_updated_date [last updated ON]
FROM bugs
LEFT OUTER JOIN bug_user ON bu_bug = bg_id AND bu_user = $ME
LEFT OUTER JOIN users rpt ON rpt.us_id = bg_reported_user
LEFT OUTER JOIN users asg ON asg.us_id = bg_assigned_to_user
LEFT OUTER JOIN users lu ON lu.us_id = bg_last_updated_user
LEFT OUTER JOIN projects ON pj_id = bg_project
LEFT OUTER JOIN orgs ON og_id = bg_org
LEFT OUTER JOIN categories ON ct_id = bg_category
LEFT OUTER JOIN priorities ON pr_id = bg_priority
LEFT OUTER JOIN statuses ON st_id = bg_status
WHERE (st_name <> 'closed' AND st_name <> 'UAT Testing' AND st_name <> 'Deploy to UAT')
AND orgs.og_name = 'ORG_NAME'
ORDER BY bg_priority


When twiddling queries in SSMS, you’ll have to comment out and bu_user = $ME


Steps to Recreate

I added a custom field, varchar 2048
Should be required, IMHO




Looking into this....



Best Practices

(ugh. buzz word. phrase.)
How to report bugs effectively
Bug Reporting Best Practices



No comments yet.



Add Comment

 Your Message
 Enter value ← Have you entered the code number?