Extension:IssueTracker: Difference between revisions
| Line 188: | Line 188: | ||
''' 1.13.3 bug found ''' |
''' 1.13.3 bug found ''' |
||
''' the same applies for 1.14.0 also ''' |
''' the same applies for 1.14.0 also ''' |
||
Revision as of 10:45, 17 April 2009
Release status: beta |
|
|---|---|
| Implementation | Tag, Special page |
| Description | A simple and powerful bug tracking and issue tracking extension developed to make this process easier for your team. |
| Author(s) | Federico Cargnelutti |
| Latest version | 1.0 (March 08, 2008) |
| MediaWiki | 1.9.0 or greater |
| Licence | No licence specified |
| Download | SVN Change Log |
The IssueTracker extension is a simple and powerful bug tracking and issue tracking system developed to make this process easier for your team. It introduces the <issues /> tag to the MediaWiki markup, which can be used to produce an issue and bug tracking system.
Features
Version 1.0
- View, add, edit and archive issues.
- Search issues.
- Filter issues.
- List issues (new, resolved, closed, archived and/or any other custom tag).
- Access Control List (group of users can have a different access levels).
- Anonymous issue management.
- MVC architecture, easy to extended.
Version 1.1(not yet released)
- Attachments.
- Issue change history.
- Changelog support.
- Email notifications.
- Users can monitor specific issues.
Screencast
Screenshot

Usage
The IssueTracker extension provides a custom tag, <issues />, that allows the inclusion of an issue tracker in any wiki page. It's possible to customize almost every aspect of the extension, such as permissions, user groups, colours, titles, and templates. It supports searching and several types of filtering.
To embed an issue tracker into a page, use the <issues /> tag:
<issues />
If a project name is not provided, the extension will use the page namespace as the default project name. You can create multiple issue trackers by providing different project names, for example:
<issues project="My Project" />
To hide the filter and search forms you can set the search and filter options to false:
<issues project="My Project" search="false" filter="false" />
By default, users must be logged in to add, edit or achieve issues. If you want to allow anonymous issue management, set the authenticate option to false:
<issues project="My Project" authenticate="false" />
Options
- project = String : The project name (default: page namespace).
- authenticate = Boolean : User authentication (default: true).
- search = Boolean : Display search form (default: true).
- filter = Boolean : Display filter form (default: true).
Requirements
The IssueTracker extension requires MediaWiki 1.9.0 or greater.
Download
Archive File
Available formats: zip | tar.gz
Subversion Repository
Use SVN to checkout a copy of the source code. I highly recommend you to get the trunk version of the extension until a stable version is released. I do what I can to ensure that SVN versions are build-able and run-able, but clearly beta versions in SVN should not be considered stable.
Check out the current development trunk with:
$ cd extensions/ $ svn checkout http://svn.phpimpact.com/repo/MediaWiki/IssueTracker/trunk/ IssueTracker
Installation
1. Copy the IssueTracker/ directory into the extensions folder of your MediaWiki installation. Note: Make sure that the extensions/ directory and the IssueTracker/ directory are both readable and executable by everyone.
2. Add the following line to the LocalSettings.php file:
require_once $IP . '/extensions/IssueTracker/IssueTracker.php';
3. Create the database table, executing the following script on your MySQL administration tool. In case you are using Wiki SQL table prefixes, do not forget to add that prefix as prefix to the table name issue_tracker.
CREATE TABLE `issue_tracker` (
`issue_id` int(10) NOT NULL auto_increment,
`type` varchar(5) NOT NULL default 't_bug',
`title` varchar(100) NOT NULL,
`summary` text NOT NULL,
`status` varchar(5) NOT NULL default 's_new',
`assignee` varchar(40) NOT NULL,
`user_name` varchar(40) NOT NULL,
`user_id` int(10) NOT NULL,
`project_name` varchar(100) NOT NULL,
`deleted` int(1) NOT NULL default '0',
`history` text NOT NULL,
`priority_date` datetime NOT NULL default '0000-00-00 00:00:00',
`date_created` timestamp NOT NULL default CURRENT_TIMESTAMP,
PRIMARY KEY (`issue_id`),
KEY `user_id` (`user_id`)
);
Customization
Customization options are available and can be set in the IssueTracker.config.php file.
Issue Types
$type['t_bug'] = array('name' => 'Bug', 'colour' => 'FFDFDF');
$type['t_fea'] = array('name' => 'New Feature', 'colour' => 'E1FFDF');
$type['t_imp'] = array('name' => 'Improvement', 'colour' => 'FFFFCF');
$type['t_doc'] = array('name' => 'Doc', 'colour' => 'F9F9F9');
$type['t_fee'] = array('name' => 'Feedback', 'colour' => 'E5D4E7');
$type['t_tes'] = array('name' => 'Test', 'colour' => 'DFE2FF');
You can add as many issue types as you want, for example:
...
$type['t_pat'] = array('name' => 'Patch', 'colour' => 'EEEEEE');
Issue Status
$status['s_new'] = array('name' => 'New', 'colour' => 'F9F9F9');
$status['s_asi'] = array('name' => 'Assigned', 'colour' => 'F9F9F9');
$status['s_res'] = array('name' => 'Resolved', 'colour' => 'B8EFB3');
$status['s_clo'] = array('name' => 'Closed', 'colour' => 'F9F9F9');
Permissions
$perms['list'] = array('group' => '*');
$perms['view'] = array('group' => '*');
$perms['add'] = array('group' => '*');
$perms['edit'] = array('group' => '*');
$perms['archive'] = array('group' => '*');
$perms['delete'] = array('group' => '*');
$perms['assign'] = array('group' => 'sysop');
$perms['assignee'] = array('group' => 'devel');
By default:
- list: Any group can access the listing page.
- view: Any group can view issues.
- add: Any group can add issues.
- edit: Any group can edit issues.
- archive: Any group can archive issues.
- delete: Any group can delete issues.
- assign: Only the "Sysop" group can assign issues.
- assignee: Issues can only be assigned to users in the "Devel" group.
Change Log
| Version | Release Date | Description |
|---|---|---|
| 1.0b | 08 Mar, 2008 | Version 1.0 beta released |
| 1.0b | 11 Mar, 2008 | Added new hook: ParserAfterTidy |
Known Bugs
More than one issue tracker on a page is not properly supported. It looks fine, but when you create a new issue, it creates a new issue for every issue tracker on that page, with the exact same content, into the one tracker.
1.13.3 bug found
the same applies for 1.14.0 also
Open: IssueTracker/Actions/IssueTrackerActionAdd.php
Change: require_once 'SpecialListusers.php';
To: require_once 'includes/specials/SpecialListusers.php';
License
GNU General Public Licence 2.0 or later. Copyright © 2008, Federico Cargnelutti.
