Extension talk:IssueTracker

25 June 2009 Task End Date and Outcome fields ??
HI great extension Would it be useful to others to add the ability to record the actual end date of the task and its outcome ie successful, incomplete, partial etc

Cheers

Mark W

April 21, 2009 Where do I configure the Issue list to show all issues instead of 30 items by default in View Issue?
Solution:
 * Models/IssueTrackerModelDefault.php
 * // public function getIssues($conds, $offset, $limit = 30)

--BertvanderHooft 20:34, 24 October 2009 (UTC)

February 22, 2009: small patch to have text parsed by mediawiki
Hi, we made some minor changes to the code to have the issues parsed by mediawiki. It is available at http://hackerspace.lu/issuetracker_mediawiki.patch

Other things that we'd love to see: (besides email notification)
 * 1) Present title in italic if task is in progress, make it bold if it is marked as ASAP, etc..
 * 2) Extend title varchar size
 * 3) When someone is set as assignee, change status to assigned automatically
 * 4) Natural sort order!

thanks, hackerspace.lu Dead Link for the patch. Where can I find it?

''Do you have a robust solution for this because it doesn't work with Mediawiki 1.14 and FCKeditor? The internalParse function fails. I've tried using  but it doesn't help. I've solved it temporarily by making the title an implicit anchor but it's not what I wanted.'' - John Colman

29 August 2008: IssueTracker vs Issue_Tracker
Produkt Version MediaWiki 1.13.0 PHP 5.1.2 (isapi) MySQL 5.0.51a-community-nt-log Windows 2003

On my System the IssueTracker Appears on the specialPage wiki/index.php?title=Spezial:Issue_Tracker  (note .. with underline)

but if i klick on add the wiki/index.php?title=Spezial:Issue_Tracker the underline is removed

wiki/index.php?title=Spezial:IssueTracker&bt_action=add

...

I searched in the files .. i only found a IssueTracker but no Issue_Tracker!


 * I had the same issue when installing on Windows (though it worked fine on Ubuntu when I tried.
 * I fixed it by editing the 'IssueTracker.i18n.php' file replacing line
 * with
 * 204.99.250.45 21:55, 20 March 2009 (UTC)
 * 204.99.250.45 21:55, 20 March 2009 (UTC)
 * 204.99.250.45 21:55, 20 March 2009 (UTC)

???
I've followed the installation instructions and when I add to a page I get a very long string that starts with: "@ENCODED@PHN0eWxlIHR5cGU9InRleHQvY3NzIj4NCmRpdiNpc3N1ZUZpb"

When will version 1.1 be available. I would like to have the email feature.

This is with MediaWiki 1.11.0 and PHP 5.2.5
 * This issue should be fixed with r63, another problem occurs if you use a version containing only one '.' like 1.13alpha. The author didn't fix that yet, but I sent him a proposal. --Osai 13:14, 11 March 2008 (UTC)


 * 11 March 2008: Encoding Issue

Hi, yes, I'm aware of this (thanks Osai) and I'm trying to implement a solution for the latest versions of MediaWiki. To fix this manually, you can update the IssueTrackerAction.php file.

File: IssueTracker/Actions/IssueTrackerAction.php Line: 269

Change: return $this->_processOutputEncoding($output); To: return $output;

I've added the ParserAfterTidy hook to fix the encoding issue in MediaWiki > 1.11.2. The ParserAfterTidy hook is available from version 1.5.0.
 * 11 March 2008: Encoding Issue Resolved
 * Nice job. And it is working very well, here is a live demo, I'll probably have a closer look at the styling, maybe you could add a super class 'IssueTracker' to apply custom styles using CSS. Best Regards, Osai 23:37, 11 March 2008 (UTC)

I've followed the installation instructions perfectly. However, when I click on the "add" link to insert a new issue all I get is a blank white page. I do not receive any error messages either. Is there a known fix for this? Thanks, Dave Dchou 04:12, 20 November 2008 (UTC)
 * 19 November 2008: Unable to add new issue

Comments
Great extension, I love it! Keep up the good work on it!

I would like to make a request/suggestion for a "Comments" capability on each issue. I would try to modify it myself to manage that but I'm not quite proficient enough with the code. Could this be done?


 * --Kethra 05:34, 28 March 2008 (UTC)

View Archived issues
Would be Nice if it is possible so see old/done issues.

Granular permissions by project
I'd like to see the IssueTracker have the capability to set permissions by project. In our case, different developer teams are responsible for different projects, and I'd like to have the ability to assign, resolve and close projects reside within the team responsible for the project. --Lhridley 13:36, 18 June 2009 (UTC)

Support for Wikitext markup
Wow! wouldnt' it be great if the text box would handle content in wikitext markup? --Lhridley 13:37, 18 June 2009 (UTC)

Wiki markup support -- future enhancement?
I think that the Summary filed should allow wiki formatting. --DCLXVI 19:26, 8 April 2008 (UTC)

I agree...Wiki markup would be super! --Lhridley 13:10, 18 June 2009 (UTC)

Some thing about "archived

 * It's seem to having some situations.
 * Once a issues be archived, it's can't be search.
 * How to change a archived issues to other status.


 * Yeah..  I agree! This IssueTracker would be far more useful if you could "unarchive" issues!
 * One more agree :D

Add Mail function
It will be better if this extension can send email to a user when a issues assigned to him or something changed in the issues like Todo Tasks.:-) --Roc michael 17:10, 15 April 2008 (UTC)

—

This can be achieved pretty easy, do the following modifications: open Actions/IssueTrackerActionAdd.php and edit funcion addAction, paste the following code:

if ($_POST['bt_assignee'] != wfMsg('unassigned')) { $assignee = User::newFromName($_POST['bt_assignee']); $assignee->sendMail(wfMsg('issue_added').": ".$_POST['bt_title'],wfMsg('filehist-user')." ".$userName." ".wfMsg('has_assigned_issue').": ". $_POST['bt_title']. "\n".wfMsg('status').": " .$this->statusArray[$_POST['bt_status']]['name']. "\n".wfMsg('type').": " .$this->typeArray[$_POST['bt_type']]['name']."\n".wfMsg('summary').": ".$_POST['bt_summary']."\n\n".wfMsg('see')." http://".$_SERVER['HTTP_HOST'].$this->listUrl); }

after the line $this->getModel('default')->addIssue($_POST, $userId, $userName);

Similarly, open Actions/IssueTrackerActionEdit.php and edit function editAction, paste the following code:

if ($_POST['bt_assignee'] != wfMsg('unassigned')) { $assignee = User::newFromName($_POST['bt_assignee']); $assignee->sendMail(wfMsg('issue_changed').": ".$_POST['bt_title'],wfMsg('filehist-user')." ".$userName." ".wfMsg('has_changed_issue').": ". $_POST['bt_title']. "\n".wfMsg('status').": " .$this->statusArray[$_POST['bt_status']]['name']. "\n".wfMsg('type').": " .$this->typeArray[$_POST['bt_type']]['name']."\n".wfMsg('summary').": ".$_POST['bt_summary']."\n\n".wfMsg('see')." http://".$_SERVER['HTTP_HOST'].$this->listUrl); }

after the line

$result = $this->getModel('default')->updateIssue($this->issueId, $_POST)

Finally, add the following messages into IssueTracker.i18n.php:

$messages['en']['issue_added']     = 'New issue added'; $messages['en']['has_assigned_issue']  = 'has assigned new issue to you'; $messages['en']['issue_changed']       = 'Issue changed'; $messages['en']['has_changed_issue']   = 'has changed an issue assigned to you'; $messages['en']['see'] = 'See';

And that is, now you'll get an email once a new issue is assigned to you or changed. Milos Jakubicek 15:01, 4 August 2009 (UTC)

Add Priority
The one item missing from making this a very useful tool is the ability to set a priority. The default would be blank, but then the list should be at the very least 1 through 10. If I can I'll try to make the modifications myself to see if I can make it work and submit it for review. --cvtrig 02:24, 19 April 2008 (PST)

Has this been added?

Special Page fix
Thanks for the great extension. I particularly like how your MVC framework lets you run everything on a Special Page instead of at the issue tag.

However I needed to make a few tweaks to get it to work with multiple projects ...

Index: IssueTracker.body.php

=
====================================================== --- IssueTracker.body.php	(revision 17) +++ IssueTracker.body.php	(working copy) @@ -56,10 +56,16 @@ 		// Set the page namespace $title = Title::makeTitle(NS_SPECIAL, $this->getName); $namespace['dbKey'] = $title->getPrefixedDbKey; +		if ($par) $namespace['dbKey'] .= '/'. $par; $namespace['text'] = $title->getPrefixedDbKey; +		$args = array; +		$args['project'] = $par; + +		$isParserHook = false; +		 		// Process request -		$output = $this->_processActionRequest($namespace); +		$output = $this->_processActionRequest($namespace, $isParserHook, $args); // Output $this->setHeaders; Index: IssueTracker.i18n.php

=
====================================================== --- IssueTracker.i18n.php	(revision 17) +++ IssueTracker.i18n.php	(working copy) @@ -10,7 +10,7 @@ * @copyright   Copyright (c) 2008 Federico Cargnelutti * @license    GNU General Public Licence 2.0 or later */ -$messages['en']['issuetracker']   = 'Issue Tracker'; +$messages['en']['issuetracker']   = 'IssueTracker'; $messages['en']['view_issues']    = 'View Issues'; $messages['en']['project']        = 'Project'; $messages['en']['add']            = 'add'; @@ -40,4 +40,4 @@ $messages['en']['error_bt_title'] = 'Please enter a title'; $messages['en']['not_authorized'] = 'You are not authorized to view this page'; $messages['en']['invalid_id']     = 'Invalid issue ID'; -?> \ No newline at end of file +?>

With these changes you can use Special:IssueTracker/. There is still an issue with the i18n bits; it doesn't seem to work when the name of the special page is different from 'IssueTracker' - hence the change in the i18n file.

Eclecticdave 19:29, 30 May 2008 (UTC)

Just installed it
On Ubuntu 8.04, and it looks great!

I recommend it to be built into Wikipedia by default. 76.28.255.165 08:26, 15 July 2008 (UTC)

Bug with multiple issue trackers on a page
I have created several pages with multiple issue trackers. It is sort of a meta tracking page. It works great, but when you add a new issue, it creates an issue every issue tracker on the page, with the exact same content, into the one issue tracker.

Supporting more than one issue tracker on a page should be a supported scenario.

Installation problem
I try to install the IssueTracker extensions, after I add the "require_once $IP . '/extensions/IssueTracker/IssueTracker.php';" line to my LocalSettings.php file, I get a blank white page as my main wiki page.

I get log entries like so:

Warning: require_once(/www/Interactive/extensions/IssueTracker/Models/IssueTrackerModelDefault.php) [function.require-once]: failed to open stream: No such file or directory in /www/Interactive/extensions/IssueTracker/IssueTracker.body.php on line 3

Fatal error: require_once [function.require]: Failed opening required '/www/Interactive/extensions/IssueTracker/Models/IssueTrackerModelDefault.php' (include_path='/www/Interactive:/www/Interactive/includes:/www/Interactive/languages:.:/usr/local/lib/php') in /www/Interactive/extensions/IssueTracker/IssueTracker.body.php on line 3

Any suggestions?

Major Bug/Glitch
I was unable to add a new issue or search for issues, it seems theres a glitch or something going on here. . the bug is already mentioned here on this talk page. Issue_Tracker vs IssueTracker

I tried to find the line in the code myself with no luck.


 * To fix this, edit IssueTracker.i18n.php, and change

$messages['en']['issuetracker']   = 'Issue Tracker'; to $messages['en']['issuetracker']   = 'IssueTracker';

--Lhridley 12:48, 18 June 2009 (UTC)

In the current trunk version of the Special page for Issue Tracker has a glitch that causes the php includes to point to an "invalid special page".

While trying to use this from a tag in an article causes

PHP Error Message

Warning: IssueTrackerActionAdd::require_once(SpecialListusers.php) [issuetrackeractionadd.require-once]: failed to open stream: No such file or directory in /home/$user/public_html/wiki/extensions/IssueTracker/Actions/IssueTrackerActionAdd.php on line 119

PHP Error Message

Fatal error: IssueTrackerActionAdd::require_once [function.require]: Failed opening required 'SpecialListusers.php' (include_path='/home/$user/public_html/wiki:/home/$user/public_html/wiki/includes:/home/$user/public_html/wiki/languages:.:/usr/lib/php:/usr/local/lib/php') in /home/$user/public_html/wiki/extensions/IssueTracker/Actions/IssueTrackerActionAdd.php on line 119


 * This can be fixed by changing the line 119 to require_once $IP.'includes/specials/SpecialListusers.php'; where $IP is path to the wiki folder. --Tejasparikh 22:44, 21 March 2009 (UTC)

Attachements how to?
1. How can I add attachments in the edit window?,

2. If somebody post issues and then if the solver want to guide then how to do? May the solver need to edit the window and reply? Its mean issue submitter always need to check issues. is it possible to make the highlights if there is new messages in the issue then issue submitter easily know there is new message in the issue.

Version 1.1
Is version 1.1 available for download. I would like to have email and attachment capabilities. Thanks

Ver 1.1
How can I download version 1.1??? Please help me...


 * Yep, me too. I contacted the author, let's see if he answers. --Michaelaye 17:32, 4 November 2008 (UTC)

some stuff
currently working on some improvements, wiki markup is fine for summ and header

own page for issue etc., just to note here.

nice tool! 84.57.29.233 08:23, 14 November 2008 (UTC)

Install error
Hi. I've just checked out the repository (at phpimpact.com) and followed the instructions in the section Installation. I restarted Apache, and create a new, empty page, with " ". When saving, I get this error:

"Fatal error: Call to undefined function wfLoadExtensionMessages in /var/lib/mediawiki1.10/extensions/IssueTracker/IssueTracker.body.php on line 39".

Any idea? Thanks, --Florent (2008-11-22T01:45:00+02:00)


 * -> UPDATE WIKI VERSION? i had the same error until upgrade wiki upto current version (1.13.3). It could be because of some functions or objects (for example $wgExtensionMessagesFiles) is introduced in later versions then you have ...
 * I think extension-info-label for IssueTracker needs to be updated too; it says that minimal version needed is "1.9.0 or greater" but here we see that it needs at least "1.11.0" (for $wgExtensionMessagesFiles). <_<

Semantic Mediawiki integration?
Hi first of all very excellent extension, I was wondering if this can be integrated to SMW?

Assignee List
The drop down Assignee box does not show more than 51 users

Use different Config files for seperate Issue Tracker pages
Great extension! I'd like to be able to customize the issue types and status specific to each issue tracker that I run. Right now it gets a little confusing since I have added issue types that only pertain to one of my issue tracker pages, but those issue types are also showing up on every issue status page in my wiki.

Problem when trying to use groups to restrict permissions
Hello, first of all thanks for an excellent extension, it seems to fulfill our needs perfectly. Just having a small issue while attempting to restrict the ability of certain users to add, assign, archive etc. Ive attempted to create a separate group that will have permissions to do these things but will allow only normal logged in users to view. I dont want to use the Sysop user as per the example I have done the following as per examples create a new group in my localsettings.php file (not sure what permissions they will need to be able to create and assign tasks) $wgGroupPermissions['WAB' ]['edit'] = true; $wgGroupPermissions['WAB' ]['read'] = true; $wgGroupPermissions['WAB' ]['createpage'] = true;
 * 1) Create the WAB group

and in my issuetracker.config.php public function setPermissions {               $perms['list']     = array('group' => '*'); $perms['view']    = array('group' => '*'); $perms['add']     = array('group' => 'WAB'); $perms['edit']    = array('group' => '*'); $perms['archive'] = array('group' => '*'); $perms['delete']  = array('group' => '*'); $perms['assign']  = array('group' => 'WAB'); $perms['assignee'] = array('group' => '*');

$this->_permissions = $perms;

I am a member of the WAB group from the user list page Wiltonm ‎(WAB, Bureaucrat, Sysop) But when attempting to add or assign i get the following error You are not authorized to view this page

are there specific permissions that i need to assign the WAB group to allow, assigning and adding ???

cheers regards Mark Wilton

203.9.185.216Resolved, Case is significant, make your group all lower case Mark Wilton

Another solution
Or, if you'd prefer not to have the extension dictate your group names, go to the hasPermission function in IssueTrackerAction.php and change if ($group == strtolower($perms[$action]['group'])) { to if ($group == $perms[$action]['group']) {

Thanks, Clif Johnston

Message error (MW 15)
Is any body else receiving this error:

Does anybody have any ideas?--05:13, 11 July 2009 (UTC)

Special List Users Error
After seeing mention of this error in widely varying spots i collected them all together. **29 sept 2009** I figured out that within IssueTrackerActionAdd.php it references the SpecialListusers.php file, which can't be found. Is the SpecialListusers.php file supposed to be included in the Issue Tracker download? Thanks, Dave Dchou 23:51, 20 November 2008 (UTC)
 * 20 November 2008: Unable to add new issue - UPDATE

I had the same problem mentioned in 20 November 2008: Unable to add new issue - UPDATE I figured out that within IssueTrackerActionAdd.php it references the SpecialListusers.php file, which can't be  found. Is the SpecialListusers.php file supposed to be included in the Issue Tracker download? Thanks, Dave Dchou 23:51, 20 November 2008 (UTC)
 * November 21, 2008 - ME TOO

I found that SpecialListusers.php is in wiki/include/specials. The path used in IssueTrackerActionAdd.php doesn't get there. you can copy SpecialListusers.php to the extensions/IssueTracker/Actions folder, or fix the pathing in IssueTrackerActionAdd.php, line 119 from

/** @see SpecialListusers **/ require_once 'SpecialListusers.php';

to something like

/** @see SpecialListusers **/ require_once '/includes/specials/SpecialListusers.php'; /*Fix Line, this doesn't work*/ /* remove the leading / (before includes) so the path wil be right*/

I'm a PHP newbie, so still figuring out how to make the path correct, but copying the special page into the actions folder is functional workaround. Someone tell me if you can recomend the correct PHP for the line above? --Janunson 13:31, 21 November 2008 (UTC)

Just found one possible Solution.. But be aware, I am also a PHP noob :-) (at least it works for me) /** @see SpecialListusers **/ require_once dirname(__FILE__) . '/../../../includes/specials/' . 'SpecialListusers' . '.php';
 * January 06 2009

There is also this error in MW 15 

Which points to this line: The file is simply not there. I am missing something? --iWiki 22:51, 24 July 2009 (UTC)

I'm not running 15 so can't check but I assume it's likely the same issue as shown further up the page. Try the solution offered there

Alternative SQL code for Postgres
I modified the table creation code to work on Postgres:

CREATE TABLE mediawiki.issue_tracker ( issue_id serial NOT NULL,  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 NOT NULL,  project_name varchar(100) NOT NULL,  deleted int NOT NULL default '0',  history text,  priority_date timestamp NOT NULL default '1970-01-01 00:00:00',  date_created timestamp NOT NULL default CURRENT_TIMESTAMP,  PRIMARY KEY (issue_id) );

Note that I removed the NOT NULL constraint from the history column, since it is currently not used by the code, and as such it would lead to fatal exceptions. Also, there is no index on the user_id column, but that could be created separately. For the time being, I just went for the absolute minimum to make it work. - Patai Gergely

Edit task does not work
I have made all of the recomended changes above, but I am still receiving an error (HTTP 500 Internal Sever Error) the same error received before changing the path to the SpecialListuser.php file.

Thank you in advance.

--Dgennaro 16:49, 4 November 2009 (UTC)