Programming.BugTracking History

Hide minor edits - Show changes to output - Cancel

October 15, 2013, at 08:44 AM by OtherMichael -
Changed line 1 from:
(:toc-float knowing what went wrong, and how it was fixed (or why not):)
Added lines 5-7:

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

July 31, 2013, at 09:59 AM by OtherMichael - bugtracker migration
Added lines 17-26:

!! installation

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).

April 18, 2013, at 11:43 AM by OtherMichael -
Added lines 36-45:

!!! 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....
April 11, 2013, at 10:30 AM by OtherMichael -
Added lines 19-20:
It uses the [[|ckeditor]]
April 03, 2013, at 04:46 PM by OtherMichael -
Added line 13:
->But don't get too carried away, lest it become a wiki itself.
Changed lines 16-18 from:
BugTracker did everything I needed.

[=BugTracker=] did everything I needed.

!!! Visual editor
Changed lines 20-23 from:

TODO: notes on setting up queries

And it's displaying everything in monospace.
How can I change that?
I'd like to display only selected items (code-fragments) in monospace.

Changed line 25 from:
TODO: is it possible to get a default organization? Or am I using the wrong schemas?
'''TODO:''' is it possible to get a default organization? Or am I using the wrong schemas?
Deleted line 29:
Added lines 36-70:
!!! Queries
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.

(:toggle id="tog1365021491266" show="Show query" init=hide button=1:)
(:div1365021491266 id="tog1365021491266" style="border:1px solid #999; padding;5px;":)
(:source lang=sql:)
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

Changed lines 73-80 from:
Looking into this....
Looking into this....

!! Best Practices
(ugh. buzz word. phrase.)
[[|How to report bugs effectively]]
[[|Bug Reporting Best Practices ]]
April 03, 2013, at 02:19 PM by OtherMichael -
Added lines 22-23:

!!! Organizations
Added lines 25-33:
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@]'''
April 02, 2013, at 11:07 PM by OtherMichael -
Added lines 16-23:

Ugh. The "visual" editor drives me bananas.

TODO: notes on setting up queries

TODO: is it possible to get a default organization? Or am I using the wrong schemas?

March 11, 2013, at 10:41 AM by OtherMichael -
Added lines 1-2:
!! Logging bugs
Added line 6:
!! []
Changed lines 15-19 from:
BugTracker did everything I needed.
BugTracker did everything I needed.

!! [=BugNet=]
Looking into this...
March 11, 2013, at 10:36 AM by OtherMichael -
Changed lines 7-9 from:
I extended the code to add in some short-links
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/CustomInterMap|PmWiki's "intermap"]].
March 11, 2013, at 10:34 AM by OtherMichael -
Added lines 1-10:
I used to have some notes on the "best practices" for logging bugs, etc.
Wonder where it all went....

I was satisfied with [[|]] 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
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.