With respect to "
What other possibilities do I have?":-
It depends on how you structure your project pages. If, as I do, they have separate namespaces (e.g.
:projects:$ProjectName:start) then, if you can do without tables:-
1. I would like to see one table section with all "to do topics" of all projects.
=====All Project todos=====
~~TODOLIST ns:projects:~~
[/color]
2. I would like to see individual tables sections showing of all to do topics for individual projects. Perhaps that's better suited to the
task plugin.
I note that you probably want (data)tables so that you can filter, rather than for aesthetics.
I'd be
very interested in how you solve this as I require similar functionality. Currently, for similar purposes, I use
:client:$ClientName:start,
:jobs:$JobNumber:start, and
:projects:$ProjectName:start.
Clients have
Jobs, and
Jobs have
Tasks.
Clients and
Jobs use the Structured Data Plugin and Bureaucracy to create new
Client and
Job records.
Each
Client record uses datalist to display
Jobs associated with that
Client, as well as listing of Open Todos for that Client's Jobs.
Job records display Open ToDos and
Tasks (associated with that
Job). i.e. A Job Record contains Tasks for that Job on the same page.
With respect to your second question - I work around that problem by linking
Projects to
Jobs, and
Jobs to
Projects (though a
Project does not have to have an associated
Job). Project records are just descriptions, mainly for the purposes of providing a record of what
has happened, and documenting "how" it will be managed during the project rather than for actual project management (e.g. links to spec's, contracts, stakeholder and system analysis docs) - during the Project lifetime I use other software for managing resources (e.g. Kolab, Redmine
*¹/MS Project, and OTRS).
I've attached my template for
Projects in case it helps. Links to
Job records are inserted manually in the
Approach and Training section (as are links to relevant
Project records manually inserted into
Job records). A workflow I wish to improve, though fortunately my system is only accessed and modified by a small number of users, all of whom are competent in the use of DokuWiki.
tl;dr? I suspect what you call
Projects, I call
Jobs,
Projects,
and Tasks.
At present much of the invoice creation process is manual (but I'm working on automating that).
*¹ see the
Redmine plugin if you want to add that capability to your Projects.