create new tag
, view all tags

XpTrackerPluginDev Discussion: Page for developer collaboration, enhancement requests, patches and improved versions on XpTrackerPlugin contributed by the TWikiCommunity.
• Please let us know what you think of this extension.
• For support, check the existing questions, or ask a new support question in the Support web!
• Please report bugs below

XP Tracker Plugin Dev Discussions

This page is for general discussion of XpTrackerPlugin. There are other pages for specific issues related to the plugin:

ZenAndXpTracking User manual for the plugin, written by AndreaBacchetta
XpTrackerPluginHistory Revision history of the plugin
XpTrackerPluginRequests Bugs and feature requests
XpTrackerPluginProblems User-reported problems
XpTrackerPluginOriginalCode The original code for this plugin, contributed by RichardBennett.
XpTrackerPluginAlternativeIdeas Alternative ideas for tracking (description of a framework for SCRUM in TWiki by DarrylGreen and the XP Project Management plugin by JohnCavanaugh.)

Ok, I started writing something on the topic of ZenAndXpTracking.

I must say that most of my problems were solved when I printed and duly read this Dev topic. Once I copied in my web all the templates, the pages started coming up filled with nice, pre-formatted, information, and once I started releasing locks on each page right after change, EditPagePlugin started finally working as espected.

But, I still feel a user oriented manual is nice to have. I get this feeling by the resistence I had myself in trying the plugin, and the resistence I am finding with my fellow PMs. I am writing the manual for them, but I will leave it here for your review. Please comment as you like, or get rid of the topic if you deem it unnecessary.

All this said, I am more and more impressed with MartinWatt and all the contributors to this plugin for the work that has been done, and for the good packaging of the plugin as a whole. Thanks to you all.

-- AndreaBacchetta - 05 Nov 2002

I notice that the teams don't seem to have much purpose. The table on a team topic just shows the backlink to the project. Is this really a useful level of hierarchy?

Let's suppose a Team is a place where one references all the members of the team in addition to the project. Now we could use the list of names that are on the team page to generate a "select" for the edittable on the tasks in a Story. Then, instead of tediously typing everybody's name every time, these names can be picked of the generated drop down list. Neat?

-- ThomasWeigert - 08 Nov 2002

The purpose of the team page is to give an overview of the team's current status. The page shows a summary of the team's work, including the percentage completion, start and end dates for each of the team's iterations. I think it's a pretty useful page when you have several teams working on a project as it allows each team manager to see how their team is getting along.

Adding team members to the page and using that to set up the edit table is a great suggestion though.

-- MartinWatt - 08 Nov 2002

I hope this question isn't too dumb but... What does the acronym 'FEA' stand for?

-- JasonKrueger - 08 Nov 2002

Not a dumb question. This is actually explained in XpTrackerPlugin at the end of the "sample output" section. In summary it's something we use at our company that I thought may be useful to others (and I didn't want to have to maintain two versions by taking it out smile ). It should probably become an optional field controllable by a plugin variable.

-- MartinWatt - 08 Nov 2002

Just a couple of questions on the use of some information that is entered manually: I perfectly see what they mean, but I fail to see if they are used for something more than mere display.

- Task , what's the use for:

- Story , what's the use for:
Story Lead
Acceptance Criteria

- Iteration , what's the use for:

-- AndreaBacchetta - 11 Nov 2002

Andrea - the fields you list are not used by the plugin when generating its tables, but that does not mean they are just there for "mere" display. I see the tracking having two aims. One is to give developers and managers an overview of the current project status. That is what the Project, Team and Iteration pages present. The Story pages have information aimed more at the individual developers. The content here, which is mostly the fields you asked about above, are aimed at the developers who are assigned the tasks. They will go to these pages to see what exactly they need to do, such as who will review their code, who the customers are and what the customers have defined for acceptance criteria. All information required by the developer to complete their tasks are either on this Story page or linked to from it.

-- MartinWatt - 17 Nov 2002

I'm very happy to say that I've had a number of interesting-looking enhancements sent to me while I was away, so I can see a 3.1 coming out shortly afterwards. (The way I am doing the version numbers is that a major version number change means a break in backwards compatability, and a minor version number change means added functionality/bugfixes.) We may also want to look at setting up a CVS for the plugin if there is enough activity to require it. This is great - thanks for all the comments and contributions. Open source is certainly proving its value here.

-- MartinWatt - 17 Nov 2002

Version 3.0 posted at XpTrackerPlugin. See details of changes at XpTrackerPluginHistory.

This is basically the same as 3.0beta except for a few fixes for uninitialised variables that were generating warnings in the apache error log. So if you have 3.0beta you may as well grab the latest version.

-- MartinWatt - 19 Nov 2002

Martin et al,

FYI. The code for XP-PM is on sourceforge at this point in case anyone is interested in checking it out. I didnt write it, MichaelWong did.

I have a few questions/commments on XpTrackerPlugin.

One of the things we are presently struggling with is how to use xp-pm during the transition period from one release to the next, I thought I would try to leverage some ideas from this plugin.

Funny thing is, it appears to suffer the same problems, namely that it is focused on using a project metaphor vs an ongoing product development with a continuous stream of releases, like 1.0, 1.0-sp1, 1.1, 1.2, 2.0 etc.

Yes we could make every new release a new project, but that doesnt feel right in my gut (or perhaps I just have indigestion). Is there a way to have an additional layer for releases within the hierarchy?? Im thinking that might make things like postponing various stories until later releases etc.

Any thoughts comments, or should I have put this in the ZenAndXpTracking topic for this type of discussion...

-- JohnCavanaugh - 20 Nov 2002


Firstly, this is the right place for this type of discussion.

I think this may be just a question of nomenclature. The project level is in fact intended to be a single release of a product. There is in theory a product level above the project level in the hierarchy, but it is not instantiated because there is not much useful to put in there. (Also I have not been using the plugin long enough to go over multiple releases and so need it.) Maybe the Project should be renamed to Release?

One thing I do wonder about is the interaction between projects and teams. Currently a project has one or more teams, and the teams belong only to that one project. However in reality a team is likely to continue on to work on the following project/release, which will break the hierarchy pattern. Alternatively, a team just changes its name based on the project it is working on.

-- MartinWatt - 20 Nov 2002

Moved bugs/suggestions from here into new page XpTrackerPluginRequests
Moved user problem reports to XpTrackerPluginProblems

-- MartinWatt - 20 Nov 2002

I finally imported XpTrackerPlugin to SourceForge ( http://sourceforge.net/projects/twikiplugins/ ).

I imported everything exactly as appeared in the release 3.0 zip. I don't think there was much to decide on the import structure.

Check ReadmeFirst and RestructurePluginsDevelopment topics, for some information on the SF repository. To contribute,

  • create a username in SF,
  • e-mail the username to PeterThoeny in order to have write access to the repository.
  • install ssh and configure cvs over ssh, instructions on SF are pretty good.

-- AndreaBacchetta - 02 Dec 2002

There are some more CVS tips over in Codev.CvsReadme, including ssh setup.

-- RichardDonkin - 02 Dec 2002

I'm just getting started implementing the XP tracker. One development use case that I don't see how to handle well is: Collect Stories for future assignment to Iterations. The problem is that I want to create the Story topics when the customer thinks of them and then later link them into an Iteration. Hopefully I'm just missing something but at this point I don't see how to do that.

BTW, the method I started with for collecting the unassigned stories is to create a WishList Project with a CustomerTeam and a NotAssigned Iteration. That allows me to collect and review the pile of future stories easily, and to start right off documenting them in XpTrackerPlugin format. I like that.

-- RichHolladay - 15 Dec 2002

Duh!! All I have to do - it appears - is to manually change the value of Iteration in the Story table. Are there any unsuspected side effects of doing this?

-- RichHolladay - 15 Dec 2002

Rich. I do what you do, create an iteration called something like UnassignedStories and load it up with any stories and tasks that we want to consider in future but do not add to an existing iteration. We normally do this for each team, so we keep the current project and team names and each team creates its own unassigned stories iteration. That ties in quite well with the XP way I think - you plan in detail for only the first few iterations, and keep all the stories beyond that in a pool to be allocated to specific iterations later.

Moving a story to another iteration is simply a case of changing the iteration name in the story table, as you found out. That is the right way to do it, there are no bad side effects.

(Andrea, this might be worth adding to the ZenAndXpTracking page)

-- MartinWatt - 16 Dec 2002

Yeah, it sounds interesting. I haven't been working on ZenAndXpTracking in a long time, I'll try to give it a shot this Xmas holiday!

-- AndreaBacchetta - 16 Dec 2002

There is now a beta of XpTrackerPlugin 3.1 at Sourceforge. Here is the full path:


It is a drop-in replacement for the current 3.0 version - no compatability issues this time. (But back up your current version!!)

The changes are as described in XpTrackerPluginRequests:

Not much in the way of docs yet. At this point I'd particularly like to get testing of the caching code on a Windows system. So far all testing has happened on Unix/Linux. Since it creates a disk file with the cached data, there may be OS-specific diffs that cause problems on untested platforms. If it works, you should see a file called .xpcache appear in the tracking web when you first modify a story page, and the file should get rebuilt on each subsequent edit. Page views should not modify the file.

Thanks to Andrea for looking after the CVS end of things, and to Andrea and Thomas for their contributions to this plugin.

-- MartinWatt - 31 Dec 2002

I've attached some mods to the 3.1 beta to order iterations by date and clean up Apache error_log messages.

-- AnthonPang - 01 Jan 2003

Anthon - thanks for the patch. It looks useful, I've had users complain about the lack of date-ordering of iterations. I'll try it out, and roll it into the next 3.1 beta version when I get a chance. I'd still like to hear from anyone who has tried the current beta on a Windows server...

-- MartinWatt - 06 Jan 2003

You're welcome. For date ordering, I updated the attachment to include a change in xpShowDeveloperTasks, i.e., after the comment "# Show them", I had to uncomment the first foreach, and then comment out the second. (nb: the code was already there)

-- AnthonPang - 09 Jan 2003

I've attached the latest version of the plugin to this page. It is basically the previous 3.1 beta from sourceforge plus Anthon's patch plus an author list in the comments. I'd like to make this the final 3.1 version, but still haven't heard from any testers on Windows. If I don't hear from anyone in the next few days, I'll just release it as 3.1 with a warning saying it is untested on a windows server. I think it should be ok on Windows, just wanted to be sure...

-- MartinWatt - 13 Jan 2003

Just came back and had a look at what you guys have done with my plugin. I haven't curently got a TWiki system to install it on, but from the discussions it sounds like it has definitely moved forward from where I originally wrote it. Congratulations, and thank you!

I'm actually posting in reply to a comment above re stories not in an iteration. We used to have a StoryPool for dropping in so far unaccounted for stories from the customer. Not sure if that functionality has made it all the way through to 3.1, but it have some special case logic in there (I can no longer remember what).

-- RichardBennett - 15 Jan 2003


It shows all iteration's stories and iteration detailes by user. How am I using it? When I assigne story to developer I use TwikiName without Main. So it looks like this LeanidNazdrynau. Then in Velocity table I click to user LeanidNazdrynau and create personal page within project Web page. Than in this page I type:



And I have all stories and task detailes for this developer within IterationOne. I also created the same page for UnassignedStory, so when I assigne task to "pseudo user" UnassignedStory it get into table of UnassignedStory. Plus I have created Personal tracking page with all users:



This help to have two different view of the project: one feature based, another developer based. My changes based on XpPlugin 3.0. Another trick it to add XPITERATION varibale on local WepPrefernce page. In this case just use:


And you can switch iteration for all users at once. Without modifying all personal pages.

I will attache my XpTrackerPlugin.pm file to this page.

-- LeanidNazdrynau - 29 Jan 2003

Sorry, did not see you already developing it in 3.1. May be my way of using it will give you some ideas.

-- LeanidNazdrynau - 29 Jan 2003

Hi Leanid. Thanks for the contribution. I have not had a chance to look at it yet, but it sounds useful. I've been really busy recently, but I should get around to making 3.1 a final release soon, then we can start on a 3.2, and include your additions.

There is an performance issue arising with XpTrackerPlugin as it is a rather big file. This slows down all TWiki page reads since every page view, even those that do not use the plugin, have to load the file and parse it for the plugin tags. So it would be good to break it down into a small file that maybe just does the init and plugin tags, and another that does all the tracking work. I don't see any other TWiki plugins coded this way, but I think none are as big. Any suggestions from anyone on the best way to do this?

-- MartinWatt - 31 Jan 2003

A short term solution is to only enable the plugin in a web that has stories in it; we've had to do this, as googlebot's crawling of server with xp tracker on everywhere took out our webserver. Since turning it off in non-tracking webs, the problem has gone away.

You might want to look at how ActionTrackerPlugin does it's packaging, it uses a sub-directory inside the lib/TWiki/Plugins directory, possibly for the same reasons you've mentioned.

-- MikeMaurer - 31 Jan '03

Today some of our users were having trouble with garbled iterations being entered in the generated tables. My fix for this was deleting the .xpcache file. It might be useful to have the plugin delete the cache file every so often to prevent this from happening.

-- MikeMaurer - 28 Apr '03

Mike - this is worrying. I have not encountered this behaviour myself. If it happens again could you save a copy of the broken .xpcache file before you delete it, and also the new clean one generated, and send it to me or post it here? Clearly there is a problem somewhere that we really need to track down. I'm not sure a periodic delete of the cache file would help, since once it is corrupt then it sounds like the tracking pages become unusable immediately.

Thinking out loud - one possible cause may be that the user is hitting a browser button like Back or Reload while the plugin is actually writing a new .xpcache file, and the interrupt results in an incomplete file? I have run into this situation with CacheAddOn at times, where the cached pages are only half written, and I'm guessing it may happen with XpTrackerPlugin as it can get quite slow, so impatient users may be tempted to start requesting page reloads.

-- MartinWatt - 28 Apr 2003

There is no harm in deleting the .xpcache file, as it is immediately rebuilt. Actually, I changed the xpsavepage routine to always delete the cache file, as for some reason I don't understand neither on my Windows nor on my Unix system the cache works as is (the change in date is not noticed).

-- ThomasWeigert - 28 Apr 2003

I modified my BYDEVELOPER view to support newly uncovered Pair Programmer feature by Doug (see XpTrackerPluginRequests) Thanks, Doug.

-- LeanidNazdrynau - 08 May 2003

There is a discussion and some patches for the .xpcache file corruption problem on the XpTrackerPluginProblems page.

-- RobertWoodcock - 09 May 2003

In order to get XpTrackerPlugin to work with the Twiki 1 Feb 03 version, it appears that you need to add the HTTP::Date module by copying the file Date.pm to ~twiki/lib/HTTP/Date.pm. (See note by JensKaemmerer on XpTrackerPluginProblems )

Could this be added to the distribution, or at least to the installation instructions on the XpTrackerPlugin page?

-- AdamShelly - 03 Dec 2003

Thanks for the information Adam. Unfortunately I'm on a heavily customised older version of TWiki, so have not got round to upgrading myself yet, but I'll try to get this updated.

-- MartinWatt - 03 Dec 2003

I have done several modifications to the XpTrackingPlugin we use at work. These are:

  • Extract the cache management to a new module Xp::Cache
  • Extract status management (not started, in progress, aceptance, completed) to a new module Xp::Status
  • Start extracting some of the xpShow* methods to the new module Xp:Show
  • Added %XPSHOWDEVELOPERTASKS{developer,web} to check the task in any web. We use this in our homepages at the Main web to list the task in our Tracking web.
  • Added %XPSHOWDEVELOPERTASKSBYITERATION{developer,iteration}%
  • Added %XPSHOWDEVELOPERTASKSBYITERATION{developer,iteration,web}%
  • Added a new Plugin callback to Store.pm and Plugin.pm to be called after a topic is saved (afterSaveHandler). This handler is used in XpTrackerPlugin to update the cache.
  • Removed the ordering in the %XPSHOWDEVELOPERTASKS% tag family. On a project with 200+ stories is was causing memory contention plus the eventual Twiki hang up, and the tag was never displayed.

I uploaded a zip with all these modifications.

-- RafaelAlvarez - 14 Jan 2004

Rafael - this looks great. Modularisation was badly needed, and having a smaller toplevel XpTrackerPlugin.pm file will make all twiki page accesses faster as it doesn't need to load such a large file. What OSs and versions of TWiki are your changes tested on? Sounds like it's time for another release...

-- MartinWatt - 15 Jan 2004

I have tested it on Windos 2k and Windows XP, using both Feb2003 release and the latest beta release, using Apache with both ActiveState Perl and Cygwin Perl.

-- RafaelAlvarez - 15 Jan 2004

Sorry, I thought that I had the latest beta on my box at work, but that was not the case. So my changes where tested only on Win2k with the Feb2003 release.

Indeed, in the latest beta the change of ordering hangs the project page. (I'll check it at home)

-- RafaelAlvarez - 15 Jan 2004

I discovered why the ordering by FEA hung the project page. I used the following:

sort { $targetOrder{$a} <=> $targetOrder{$b} || $targetOrder{$a} cmp $targetOrder{$b} || $a cmp $b }

But if the FEA has some non-numeric field, or the number of activities in an iteration is to high (around 200 in a PIV machine) xpShowIterationTerse hangs. Removing the

$targetOrder{$a} <=> $targetOrder{$b}
part solved the problem.

I'm working to further modularize the main module, something along the lines of 1 module per main function (xpShowIteration, xpDumpIteration, etc), and one support module subs. This is my first step to start removing duplicated code.

A note of interest: xpShowIterationTerse and xpShowIteration do exactly the same thing (I managed to put the same "terse" info in xpShowIteration with a very minor change), but xpShowIterationTerse does it with a lot more code.

-- RafaelAlvarez - 15 Jan 2004

The version of this plugin in CVS is not consistent with the released version. Please either update CVS or remove the "Developer Version in CVS" flag from the plugin topic. Given that this topic relates to management of a software development process, you should be setting an example.

-- CrawfordCurrie - 18 Mar 2004

I have uploaded the latest modifications. There are several changes:

  • More modularization of the code. I think I took this into the extreme, as one module per "function" was created (more or less).
  • Implementation of objects representing Stories, Iterations and Tasks. I found out that in some cases the use of these objects improved performance, but in others they impaired it.
  • SHOWTEAMITERATIONS shows also the number of stories in an iteration
  • SHOWITERATIONTERSE shows the Developer(s) and the Reviewer(s) for each story.
  • SHOWITERATION show the completition percentage with the status.
  • A new status (Error) was introduce. Use it or ignore it to your heart content.
  • If two developers are assigned to a Task, then the estimate/spent/todo will add to both totals in SHOWVELOCITY.
  • Not new, but I discovered that if you set the iteration to TornUp the Story is ignored.
  • Change the way to determine the completition status. Now it's considered complete if the TODO is 0, even if the spent is also 0.
  • Remove the use of "forbidden" methods, that ismethods that are not published via TWiki::Func module, as much as I could. This cleaning will continue (check PluginsConformanceReport for more info)

My main goal was to increase maintenability, but keeping the performance at least the same. One side effect is that the scalability improved.

Now that we're at it, how can I have access to the plugin CVS? My sourceforge id is soronthar

A final note: this update needs the AfterSavePluginHandler modification to manage the cache.

-- RafaelAlvarez - 06 Apr 2004

I have not had much time recently to work on this plugin, and Rafael is making some impressive contributions and is now the one driving development forward. As a result I've asked Rafael if he would be willing to take over as lead for this plugin, and he has agreed. Thanks very much Rafael, and keep up the good work!

-- MartinWatt - 13 Apr 2004

Welcome Rafael! And a request; it would be great if you could follow the standard for releasing the package i.e. release a single zip, named the same as the plugin. This is purely selfish on my part; i have automatic tools for analysing the plugins, and they stumble when plugin zips are release with encoded version numbers or dates. You really shouldn't need these, as attachments are fully version-controlled anyway. So if you could return to releasing just XpTrackerPlugin.zip each time, that would be great. A good tip is to write a build script that generates it, and of course runs the tests.

-- CrawfordCurrie - 13 Apr 2004

I uploaded the files with date because I was uploading and "unofficial" version of the plugin. From now on I'll upload the plugin properly packaged.

And is not selfish from your part... the PluginsConformanceReport was (and is) very useful. I'm dreaming on seeing XpTrackerPlugin in the white zone with 0 points smile

-- RafaelAlvarez - 14 Apr 2004

Great tool you have here! I am seeing an issue with XPDUMPITERATION not handling the EDITTABLE variable. So for every EDITTABLE in each story you see the line: EDITTABLE{ format="| text, 20 | text, 40 |" changerows="off" }. Has anyone else noticed this?

-- JoelOnofrio - 14 Apr 2004

I second Crawford's request, name the package XpTrackerPlugin.zip, and hide the other packages.

I did some editing on the Plugins page. Remember that WikiWord links will be broken in an installed version unless you use Interwiki names.

-- PeterThoeny - 15 Apr 2004

What Joel is reporting is happening because the raw text from the story is used. AFAIK, there is no standard(oficial?) way to invoke another plugin to render some text, so... The only hack I can think of is to manually remove the lines with the %EDITTABLE% tags in the XPDUMPITERATION function.


-- RafaelAlvarez - 15 Apr 2004

Rafael, one thing I noticed was that if you edit the page and look at it in Preview mode the EDITTABLE lines don't show up, and the tables display as standard tables as opposed to EDITTABLEs. If it behaved like this when viewing normally, I think that would be acceptable. Thanks!

-- JoelOnofrio - 15 Apr 2004

To be true, I don't know why is working that way. It seems that the preview mode is ignoring the EDITTABLE tag for some reason...

-- RafaelAlvarez - 15 Apr 2004

I ended up just removing the EDITTABLE lines...it cleaned up the page nicely. Thanks.

-- JoelOnofrio - 30 Apr 2004

Could you point out on the plugin page what XP stands for? It could be Extreme Programming or maybe Windows XP or perhaps extra large something. Thanks.

-- ArthurClemens - 04 May 2004

Had an error message when using XpTrackerPluginModified20040405. The error occured when trying to access a project status page that holds completed iterations.

Can't locate object method "complete" via package "MyIterationName" (perhaps you forgot to load "MyIterationName"?) at /var/www/twiki/lib/TWiki/Plugins/Xp/ShowProjectCompletitionByTasks.pm line 115.

Fix : There seems to be a typo at above mentioned line.

  • replace:
    $pctComplete = sprintf("%u",(complete{$iteration}*100/$master{$iteration}));
  • by:
    $pctComplete = sprintf("%u",($complete{$iteration}*100/$master{$iteration}));

Keep up the good work! XpTrackerPlugin is a real hit within our team !

-- HansPype - 13 May 2004

Finally, I uploaded the current version of the plugin into the XpTrackerPlugin topic. Check XpTrackerPluginHistory for a complete list of changes. Also uploaded to CVS the current version of the plugin.


-- RafaelAlvarez - 28 Jul 2004

FYI: With version 3.2 of the plugin, I am observing the following differences compared to version 3.1 :

  1. %XPVELOCITIES{}% and %XPSHOWITERATIONTERSE{}% are not expanded correctly on MSIE6.0. From the HTML code it appears that closing </script> tags are missing (in Xp/ShowIterationTerse.pm and Xp/ShowVelocities.pm).
  2. %XPSHOWITERATIONTERSE{}% has two HTML-forms for adding new stories. Is this intentional?
  3. when creating new iterations or stories, they are locked by TWikiGuest.
I've attempted a small patch xp32patch.txt to fix these problems on my installation. It should be applied in the lib/TWiki/Plugins directory with the command patch -p1 < xp32patch.txt. Thanks for the good work!

-- ThorkildPedersen - 09 Sep 2004

whoops... you're right. I used <script ..... /> but IE don't understood that. It'll be patchet asap. Thanks for the patch

-- RafaelAlvarez - 09 Sep 2004

For anyone who was wondering where Rafael has got to - he's been deluged at work, and says he will return to TWiki (and XpTrackerPlugin) as soon as he has time to draw breath. In the interim, if anyone has fixes or questions, why don't you post them here and perhaps some other XpTrackerPlugin user can help.

-- CrawfordCurrie - 20 Feb 2005

Some minor issue which fills up the apache log:

oops: Scalar value @_[0] better written as $_[0] at ../lib/TWiki/Plugins/XpTrackerPlugin.pm line 176.

Also the following Errors showed up:

viewauth: Use of uninitialized value in subtraction (-) at ../lib/TWiki/Plugins/Xp/ShowProjectCompletitionByStories.pm line 98.

viewauth: Use of uninitialized value in concatenation (.) or string at ../lib/TWiki/Plugins/Xp/ShowIterationTerse.pm line 51.

This refers to XpTrackerPlugin v3.2.2

-- WolfgangAlper - 24 Feb 2005

Translating XpTrackerPlugin to german:

I am working on translating the XPTrackerplugin into german. The topics are done quite easy, however i have so far no idea about the fieldname. To be more precise, what fields can be renamed and what fields are hardcoded and whould break funcionality when being translated. Also a question was raised wether fields can be added or removed (which would be customizing rather than simple translation)

-- WolfgangAlper - 24 Feb 2005

New Problem

To check performance issues i deleted the Xp modules in /lib/Plugins and also /lib/Plugins/Xp. After that i restored the modules with the same accessrights as before., However i now get always the following errormessages when trying to access existings projects:

Undefined subroutine &TWiki::Plugins::Xp::ShowProjectTeams::xpShowProjectTeams called at ../lib/TWiki/Plugins/XpTrackerPlugin.pm line 359.

For help, please send mail to the webmaster (you@yourPLEASENOSPAM.address), giving this error message and the time and date of the error.

-- WolfgangAlper - 25 Feb 2005

I added a signature to the Plugin topic; the report on the PluginPackage topic depends on it. I also added some standard rows to the Plugin Info table. How about measuring and documenting the PluginBenchmarks?

-- PeterThoeny - 23 Aug 2005

Raffael, this Plugin is kind of popular and helps the TWikiAdvocacy. How about keeping it compatible with Cairo and Dakar codebase? See updated HandlingCairoDakarPluginDifferences

-- PeterThoeny - 08 Feb 2006

with this plugin installed,when I refresh the InstalledPlugins topics in local setup, i got an error , Can't call method "maketext" on an undefined value at /local/home/twiki/twiki401/lib/TWiki/Access.pm line 174. ???

-- JingYuan - 08 Mar 2006

Jing, I ran into the same problem, and I find running the install script XpTrackerPlugin_installer.pl fixes the problem. You might want to give it a try?

-- VictorTsang - 09 Apr 2006

ManuelSoto posted a bug report with fix at TrackingIncorrectStartEndIterationDate.

-- PeterThoeny - 07 May 2006

Not sure where this goes, since appraisal pages seem to be purely poll or something based, so here's a link where XpTrackerPlugin wins. big grin

-- MeredithLesly - 19 May 2006

thanks smile

-- RafaelAlvarez - 19 May 2006

I have tried installing XpTrackerPlugin with the TWiki 4.0 family and the plugin continually fails, citing an error with "getPreferencesValue" on the plugin diagnostics page. I've tried this with 4.0.2, 4.0.1, and 4.0.0 (the topic said the build had been tested with 4.0.0). Does anyone know if there is an up-to-date built version of the plugin that I can install?

-- JoshAllen - 06 Jun 2006

Unfortunately, the authors of the plugin have either vanished or (in the one case I know of for sure) are overloaded with work. Hopefully one of them will come in and fix things up.

-- MeredithLesly - 16 Jun 2006

Thanksfuly, I manage to squeeze a little time to help a fellow plugin user smile The problem was that for some reason the attachments were "screwed", so it was pointing at the wrong version. I uploaded the right version to the plugin topic, so everything should be fine now.

-- RafaelAlvarez - 16 Jun 2006

Speaking of the darling devil! big grin

-- MeredithLesly - 16 Jun 2006

The latest download seems to be broken - WinZip and Linuz unzip both fail to unzip it. The 322 version seems ok but I'm in Twiki4

-- PaulJeffrey - 13 Jul 2006

again? frown i'll upload the good one later today.

-- RafaelAlvarez - 14 Jul 2006

I do not think that there is an issue with the .zip / .tgz files. There have been several similar reports in the Support web, it looks like an Apache config / firewall / browser combination issue.

-- PeterThoeny - 14 Jul 2006

>I have tried installing XpTrackerPlugin with the TWiki 4.0 family and the plugin continually fails, citing an error with "getPreferencesValue" on the plugin diagnostics page. I've tried this with 4.0.2, 4.0.1, and 4.0.0 (the topic said the build had been tested with 4.0.0).

It doesn't work any better with 4.0.4. I've also tried ProjectPlannerPlugin and OoProjectPlannerPlugin. Is there a project-management plugin that does work with TWiki 4.0.x?

-- ScottAlfter - 05 Sep 2006

Never mind the last post...I had grabbed an older version and installed that.

-- ScottAlfter - 05 Sep 2006

anyone else having issue wiht the maketext? I tried running the installing but get this error every time I enable the plugin.

Can't call method "maketext" on an undefined value at /usr/local/twiki/lib//TWiki/Access.pm line 174.
[Fri Sep 29 16:00:21 2006] [error] [client X] Premature end of script headers: /usr/local/twiki/bin/view

Any pointers appreciatted.

Also, I don't know if this makes a difference, but the current attachment does not seem to have the XP directory per the install instructions:

lib/TWiki/Plugins/Xp/*.pm plugin Perl submodules

-- EricHanson - 29 Sep 2006

hi, Can someone confirm that this plugin works with Apache HTTP 2.2.4, TWiki 4.1.1 before i go setting it up, my section does alot of programming and i would like to see it this plugin can help us. thanks

-- JasonOKeeffe - 28 Feb 2007

well.. I know it works in TWiki 4.1 (haven't updated my install yet), but as I run on Apache 1.3.8 I cannot certify on 2.2.4.

I suggest you to ask in the Support web or in Codev.TWikiIRC if TWiki has been tested on 2.2.4. If so, this plugin should work without problems. I suggest you to take a look also to YetAnotherXpTrackerPlugin that has some features that xpTrackerPlugin is lacking.


-- RafaelAlvarez - 01 Mar 2007

Thanks Refael much appricated. smile just new to this Twiki and getting the feel of it....like it so far.

-- JasonOKeeffe - 01 Mar 2007

Anyone else get .xpchache errors randomly?

-- EricHanson - 17 May 2007

Whenever I got .xpcache errors, is because I used a wrong Web name.

-- RafaelAlvarez - 17 May 2007

I have the plugin running on latest Apache 2 to date, TWiki 4.1.2. So far I havent noticed any abnormalities.

-- MikkoLaakso - 07 Jun 2007

Thanks for the report, Mikko! smile

-- RafaelAlvarez - 07 Jun 2007

Glad I could help. Some comments about the plugin so far: it seems to have lots of potential, but there is an unfinished taste to it. The navigation in the project is almost frustrating, there should be a clearer hierarchy (parent/child) so you could browse backwards from a story to iteration, from iteration to project. Tables vary in looks, some unnecessary javascript is used in sorting XPSHOWITERATIONTERSE and XPVELOCITIES (these should be twiki tables).

-- MikkoLaakso - 11 Jun 2007

Mikko, you're absolutely right about the navigation. We actually use an "updated" version of this plugin (that I never got around to release) that creates the proper topic hierarchy, so in the breadcrumb you'll see Project->Team->Iteration->Story

There is an (historic) reason for the javascript, though: We usually have about 100-150 stories per iteration, spanning some 18 developers. Sorting the iteration table was nightmarish (because it forced a reload of the page). The javascript makes the sorting faster. Of course, that was with the 'old' server (back in the days where our wiki was not important and served from and old PC). With the current server that is not an issue anymore, so I'll make a not of making the javascript optional.

It would be nicer if this js was incorporated into TablePlugin as an option for sorting, but it was rejected at the time (and is now lost in the history of the dev topic).

Besides that, most of the tables created by XpTrackerPlugin must be "handcrafted" instead of TWiki Tables, because of the colors. I tried using "=<div>=s on each cell to set the background, but it looks ugly.

Thanks again for the feedback.

-- RafaelAlvarez - 11 Jun 2007

Hello RafelAlvarez, it would be nice if you could release your update version of the plugin with the updated hierarchy. I was also wondering how difficult it would be to combine the progress fields in the Task table. I think it would make more sense (for myself) to replace the est/spent/to do fields with a simply percentage complete field. I find I tend to forget to balance all three fields and I get incorrect figures for overall story completion. What are your thoughts on this?

-- ColinNickerson - 08 Sep 2007

Can we have a XpTrackerConsolidationDiscussion ?

-- MartinCleaver - 06 Aug 2008

I changed the ModificationPolicy of this extension from ContactAuthorFirst to PleaseFeelFreeToModify due to inactivity. Anyone please feel free to work on this extension.

-- PeterThoeny - 2012-12-03

Topic attachments
I Attachment History Action Size Date Who Comment
Compressed Zip archivezip XpTrackerModified20040114.zip r1 manage 32.5 K 2004-01-14 - 19:25 RafaelAlvarez Several modificatrion to XpTrackerPlugin v3.1
Compressed Zip archivezip XpTrackerPlugin.zip r1 manage 11.2 K 2003-01-29 - 20:37 LeanidNazdrynau New tags: *BYDEVELOPER patch for v.3.0
Compressed Zip archivezip XpTrackerPluginModified20040405.zip r1 manage 38.7 K 2004-04-06 - 00:14 RafaelAlvarez Performance improvement and modularization of the code
Texttxt XpTracking_patch.txt r1 manage 14.5 K 2003-05-08 - 18:05 LeanidNazdrynau BYDEVELOPER veiw Support pair Programmers, for 3.0
Texttxt diffsToBeta.txt r3 r2 r1 manage 6.9 K 2003-01-09 - 01:41 AnthonPang Diffs to 3.1 beta
Texttxt xp32patch.txt r1 manage 2.7 K 2004-09-09 - 12:03 ThorkildPedersen Attempt to fix missing </script> and TWikiGuest lockup in Version 3.2 (28 Jul)
Compressed Zip archivezip xptracker30beta.zip r1 manage 16.0 K 2002-11-07 - 20:54 MartinWatt  
Compressed Zip archivezip xptracker31beta.zip r1 manage 14.0 K 2003-01-13 - 22:03 MartinWatt 3.1 beta2 release
Edit | Attach | Watch | Print version | History: r139 < r138 < r137 < r136 < r135 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r139 - 2012-12-03 - PeterThoeny
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.