Last modified: 2014-10-16 12:00:22 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T58079, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56079 - [IssueTracker] Add new fields, remove Type field, and make Status a double field (e.g. RESOLVED FIXED rather than just RESOLVED)
[IssueTracker] Add new fields, remove Type field, and make Status a double fi...
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Other (Other open bugs)
master
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-24 07:08 UTC by Nathan Larson
Modified: 2014-10-16 12:00 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Nathan Larson 2013-10-24 07:08:42 UTC
IssueTracker needs Product, Component, Version, Platform, and Importance fields. Also, Type should be replaced with Severity. Status should be made a double field (e.g. RESOLVED FIXED rather than just RESOLVED).
Comment 1 Andre Klapper 2013-10-24 09:55:41 UTC
Well, in case you have Bugzilla in mind, "Importance" is actually two fields ("Severity" and "priority") plus "Target Milestone" also comes into play. One of them might be replaceable. And only the closed statuses such as RESOLVED and VERIFIED need a "double field" as they have a resolution like "FIXED" or "WONTFIX" - open status do not have that (or could use "---").
Comment 2 Nathan Larson 2013-10-24 11:19:24 UTC
Yeah, the idea is to overthrow Bugzilla (https://www.mediawiki.org/wiki/Requests_for_comment/Overthrow_Bugzilla) or at least equip IssueTracker to be a reasonable substitute for Bugzilla on non-WMF sites. Since wikis are often used for collaboration on software documentation, it makes sense to have an issue tracker extension that can do some of the same stuff as Bugzilla. Also, the closer its capabilities are to Bugzilla's, the more potential there could be to import and convert data from Bugzilla databases -- unless, of course, the extension will instead be modified to use Bugzilla databases without data conversion.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links