\documentclass{article}
\usepackage{ulem}
\pagestyle{headings}
\begin{document}
\tableofcontents

\part{ Workflow application }
Chuck Hagenbuch outlined an ambitious workflow module for horde back in 2008, but it has not been done.\newline
I needed a simple thing to document, delegate and, possibly, semi-automate a set of repetitive, multi-step workflows.\newline
I created a module "sueporter" which does exactly that in a minimum-effort way. The code needs some cosmetics before release, i.e. get license statements right and decide what is actually boilerplate, what is mine and what should be attributed to the authors of other horde modules which are copy-pasted.

I also consider either releasing it somewhere on github as "mine" or transfering copyright ownership to horde, if interested.

\begin{tabular}{|l|l|l|l|}
\hline
\textbf{Item} & \textbf{Status} & \textbf{Priority} & Comment\\
\hline
Create Jobs out of defined workflows & Works & -- & The original interest to create the thing\\
\hline
Create Workflows out of given Tasklets & Works & -- & Minimal UI does exist / No ACLs\\
\hline
Create Tasklets through UI & not implemented/DB commands needed & high & I want to get\\
\hline
Assign Jobs to users & Works & -- & Simple list-all-users dropdown / no fallback for backends without user listing / no ACLs\\
\hline
Branching workflows & Works/Subset & medium & \\
\hline
Automation hooks for certain tasklets & high & A simple hooking solution exists but the actual hooks implemented so far will stay unreleased - they are not useful to the general public - the whole automation probably should be redesigned and some example hooks given & \\
\hline
tasklet type "freeform text + code copy/paste" & Done & -- & The Code area is optional\\
\hline
parsing http links & tbd & medium & Not sure if I want to switch to wicked's markup engine\\
\hline
various markup & tbd & low & Not sure if I want to switch to wicked's markup engine\\
\hline
tasklet type "4 eyes approval" & not implemented & high & This is something I want to use myself\\
\hline
switch to a different workflow & possible, but not really implemented & medium & Currently, Step IDs only need to exist, but not necessarily in the same workflow\\
\hline
multiple choices (more than yes/no) & not implemented & medium & Beyond scope of my initial project, but probably needed for a workflow thingy\\
\hline
interface to kronolith and/or nag & not implemented & low & sadly, in my current use case this does not really make sense\\
\hline
interface to hermes & not implemented & very low & only if anybody really uses hermes + this\\
\hline
real ajax instead of HordeCore.doAction + reload & tbd & medium & this will be needed for large job lists and makes sense in most other areas\\
\hline
better CSS and proper icons instead of the same head everywhere & tbd & low & I could not care less for my own current use case, but it really needs to be done\\
\hline
get copyright right and release alpha version & tbd & very high & This should not rot in the dark\\
\hline
Import/Export workflows to some industry standard format & tbd & low & This probably won`t be used very much and can consume a lot of time\\
\hline
Import/Export jobs to some libreoffice/closed source office readable spreadsheet format & tbd & medium & Probably makes more sense than reporting features\\
\hline
Job list filters/searches & not implemented & high & \\
\hline
\end{tabular}
\section{ Bugs}
Currently not on the horde tracker

\section{ People}
Ralf Lang

\section{ Description}
Detailed project description. Include implementation steps, current status, plan, etc.

\section{ Resources}

\noindent\rule{\textwidth}{1pt}
Back to the Project List\footnote{http://example.com/index.php?page=Project}

\end{document}
