Quickstart: create the first work item

The shortest way from “the plugin is installed” to “a work item exists, carries a history and can be exported as a wiki page”. Three steps, about ten minutes.

• wkdoworkitems, wkdocore, wkdostorage and wkcore are installed and enabled.
• A DWDO project exists — see the wkdocore quickstart.
• Your account holds a role in that project which permits editing: Contributor or higher.

Inside the project, open the New work item action:

/doku.php?id=en:projects:acme:start&do=wkdoworkitems_new

Fill in Title and Type — Epic, Feature, User Story, Task or Bug — and choose Create.

The item belongs to the project it was created in, and that boundary is enforced on every later operation rather than assumed once.

Create a second item and add a relation under Relations in the editor — Parent, Children, Related, Blocks, Blocked by or Duplicate.

You state one direction only. For a directed type the inverse is written for you, so a parent link produces the child link on the other item rather than leaving half a relation that only renders correctly from one side.

Choose Export snapshot in the editor. The description is written to a standalone wiki page, with a revision summary carrying the configured prefix (default [WI]).

This is where the suite's division shows: the fields stay rows, the prose becomes a page — and thereby acquires DokuWiki's revision history, diffs, search and permissions without any of them being rebuilt over a table.

• The item carries a number, a state (New, Active, Resolved, Closed) and, under History, the entry created with actor and timestamp.
• Both items show the relation, each from its own direction.
• The snapshot page exists and opens, diffs and searches like any other wiki page.

Two counter-checks worth doing deliberately once — they are worth more than any description of them:

• Cycle: try to make an item its own child, or A under B and then B under A. The refusal happens before anything is written. A cycle discovered later is a tree that can no longer be rendered; a cycle refused now is a message.
• Concurrent edit: open the same item in two browsers, save in the first, then change and save in the second. The second save is refused, with Save not applied — the work item changed meanwhile. A version marker and a field fingerprint are compared; nothing is lost.

• wkdoboards — the same items as a kanban board.
• wkdoqueries — filter over them and save the query.
• wkdodashboard — the figures that follow from them.
• wkdoworkitems (German) — the package page: state machine, relation policy, descrawmode and every setting.