Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
wishlists:bug-tracker [2012/09/18 03:03] – Add a technical item codebrainzwishlists:bug-tracker [2012/11/08 05:11] (current) – Add todo note for later codebrainz
Line 1: Line 1:
-====== Whishlist Features of a new Issue Tracking System ======+====== Wish List Features of a New Issue Tracking System ======
  
 Lists are in no particular order (yet). Once ideas are all listed we should group them by "must have", "nice to have" and so on. Seems unlikely all of the items listed will be found in any one software and some items are completely subjective. Lists are in no particular order (yet). Once ideas are all listed we should group them by "must have", "nice to have" and so on. Seems unlikely all of the items listed will be found in any one software and some items are completely subjective.
Line 10: Line 10:
   * File/diff/image attachments   * File/diff/image attachments
   * Email notifications   * Email notifications
 +    * For individual bugs
 +    * For whole tracker category
   * Status field(s) (ex. fixed, rejected, deleted, etc.)   * Status field(s) (ex. fixed, rejected, deleted, etc.)
   * Ability to add own custom fields   * Ability to add own custom fields
   * Tags/keywords/labels (ie to make filtering/search easier)   * Tags/keywords/labels (ie to make filtering/search easier)
   * Groups/categories   * Groups/categories
 +    * Not having two different trackers for bugs & features, just different categories
   * Integration with VCS/Git   * Integration with VCS/Git
     * Ability to auto-close bug through commit message (ex. "Fixes #12345")     * Ability to auto-close bug through commit message (ex. "Fixes #12345")
Line 25: Line 28:
   * Have a template for guiding submitter what info to include (I think Google Projects does it). Like to prefill some titles in description like "steps to reproduce", "expected result", "actual result", etc.   * Have a template for guiding submitter what info to include (I think Google Projects does it). Like to prefill some titles in description like "steps to reproduce", "expected result", "actual result", etc.
     * Or least a place to put instructions that is prominent when filling out reports.     * Or least a place to put instructions that is prominent when filling out reports.
-  * Migration path/import from from existing tracker would be nice+  * Migration path/import from existing tracker would be nice
  
 ===== Non-Technical and/or Subjective ===== ===== Non-Technical and/or Subjective =====
Line 34: Line 37:
   * Open source (at least if self hosted on geany.org)   * Open source (at least if self hosted on geany.org)
   * Easy searching with good algorithm   * Easy searching with good algorithm
 +
 +===== Summary of Evaluations of Various Systems =====
 +
 +If you disagree, please add to the evaluation and mark previous content deleted (%%<del> ... </del>%%), don't actually delete it.
 +
 +==== Flyspray ====
 +
 +=== Pros ===
 +
 +  * Fast (even on an upload limited server)
 +  * Looks good
 +  * Seems to have most standard issue tracker features
 +  * Search good
 +  * Has fields protected against user modification
 +
 +=== Cons ===
 +
 +  * Has related tasks, but couldn't get them to mark as duplicates
 +  * Doesn't seem to be able to create new fields
 +  * Automation/integration interface has been removed, so links to github poor
 +  * Geany has to host it
 +
 +==== Github Issues ====
 +
 +Rather than repeating a bunch of stuff, here's a fairly good summary of features:
 +
 +[[https://github.com/blog/831-issues-2-0-the-next-generation]]
 +
 +TODO: flesh this out according to above wish list

Trace:

Print/export