Task Plugin

~~TASK:[user]?[due date][priority]~~

Place ~~TASK~~ on any page to mark it as a task. The title (first heading) is considered to be the summary of the task, the contents its description.

If a task is unassigned, any registered user of the wiki can accept it. Once a task is taken, the user to whom it is assigned to can change the status of the task to one of these values:

• rejected – task is not worthwhile or not accepted by user
• new – deassign task so somebody else can take it
• accepted – user took over task but did not yet start the work
• started – work on task started
• done – work on task completed

If the task is done, other users can verify whether it's really done. If yes, the status can be set to verified.

The priority is reflected by the intensity of the orange shade of the task box.

Next to the title of the task box is an icon. It links to download an .ics file for the task. That can be imported by almost any calendar application that understands the VTODO component of the iCalendar standard.

{{tasks>[namespace]?[view]&[flags]}}

Try this plugin at here

Please report bugs at the Bug tracker.

• Darcs Repository
• Bug tracker
• Source code

• 28 Jun 18:46 - fixed vim modeline
• 07 Jun 21:16 - fixed code style
• 07 Jun 17:20 - fixed code style
• 06 Jun 14:16 - TAG release 2008-06-06
• 06 Jun 14:16 - updated VERSION file
• 06 Jun 14:16 - updated french translation FS#37
• 06 Jun 14:11 - fix for FS#40
• 26 May 17:19 - TAG 2008-05-26 release

“done” flag don't work. You can fix it by changing these lines in task/helper.php :

Line 118 :
      if ($filter != 'all'){
to
      if ($filter != 'all' and $filter != 'done'){

and line 130 :
      if (($filter == 'done') && ($responsible || ($task['status'] != 3))) continue;
to
      if (($filter == 'done') && ($task['status'] < 3 and $task['status'] != -1)) continue;

— Jean-Michel 08/04/2008 16:05

could you please open a bug report at the Bug Tracker? — Michael Klier 2008/04/20 21:26
I couldn't reproduce this. Do you still have the problem? — Michael Klier 2008/05/05 18:04

I could reproduce this, and I opened a bug report (#31). — Andreas Schamanek 2008/05/24 01:28

Ok, I've just updated the plugin and really hope that I could finally fix all problems, please give it a go and tell me if everything is working as expected now! — Michael Klier 2008/05/25 00:43

Spent the last half hour trying to figure how to change the status of a task from accepted to done. Could someone clarify this? — abr 2008/05/25

I've added some screenshots which show the form to change tasks' statuses. Can you specify what exactly is not working? — Andreas Schamanek 2008/05/25 10:57

The form drop-down on the individual tasks appears to me as plain text. By my reading, that means it doesn't recognize my account as owning the ticket. A configurable ACL group or maybe namespace admin privilege is more than enough security on task status for me, I'll look into that. — abr 2008/05/25 20:27

It would be handy, if one could make tasks on the fly in ANY document. Making different tasks in the same document doesnt work for me. My purpose is to define certain list entries in a protocol as tasks related to users (and doing so without spoiling the formating of the list. another syntax that is including the task-description into the task-declaration would solve the problem. — EUR 2008/06/22

It's not as easy as that. The plugin treats one page as one task and making the plugin behave like you want one would need to rewrite quite a lot of it. If you like different todo items on one page have a look at the gtd plugin. Sorry, won't implement! — Michael Klier 2008/06/22 21:15

I would also really love to see the feature that EUR described (defining multiple tasks on one page). The rationale is very similar in that we want to be able to turn meetings from a minute into tasks and assign them to users but I can imagine other uses as well. Michael, if you aren't willing to implement this I would really like to try my hand on it. Do you think the current code could be used as a starting point or would there be more things changed than could be reused? Could you probably give me some pointers on where to start? Thanks!. — Georg Sorst 2008/07/08

Well, let me quote myself ”It's not easy.”. You'd have to a) change the data structure and how the plugin handles it completely (at the moment it's one page ⇒ one task - every page, if used as task, gets it's .task meta file which contains a serialized php array) b) change the whole process of adding/removing/modifying tasks, and most important c) preferably stay compatible with the current used model (read “lots of extra code”). In other words, that's almost a complete rewrite of the plugin. I'd suggest you go an easier route, have a look at the plugin code, see how it handles all that stuff and then, start writing a new one, reusing parts of its code if you like/need. — Michael Klier 2008/07/08 10:33

How difficult would it be to introduce additional task-attributes, like severity, project name, customer name… and finally make filters available on those attributes as well ?. — Hakan Coker 2008/06/30

Hmmmm, not all that difficult I think. Submit a detailed feature request at the bug tracker. — Michael Klier 2008/06/30 14:24

It is possible to link this Plugin to a BugTrackingSoftware , for example Mantis ? I think would be a nice idea. — white 2008/08/10

While creating an entry for users to reference on our syntax reference page, I found that tasks will not let you create a due date past 2038. We will probably not be using the wiki in 30 years, but I thought you should know. I haven't looked at your code yet, so I don't know if the bug is in your code or something in dokuwiki. — bfifield 2008/08/20

Well, this is not a really a bug with the plugin. In fact, 2038 is by many computer scientists considered as being the official end of the world, or maybe even the whole universe itself. Kidding aside, for further reference see year 2038 problem. — Michael Klier 2008/08/20 18:22