Work Items

Work items are the tasks, defects and QA findings for a project — the list of what still needs doing and who is doing it. They live on the project's Work Items tab, and they can be raised from the portal or from udStream, where an item can be pinned to a point in a scene.

Seeing the tab requires the View Work Items permission. What you can do beyond looking is set by the other work item permissions.

The Board and the List

Work items open on the Board — one column per state, with each item as a card. Drag a card between columns to change its state. Some moves stop to ask for something first; see Changing State below.

Switch to List for a table view. The list can be sorted, and Columns chooses which fields are shown: type, tags, state, assignee, who raised it, and the created and updated dates.

Finding things

Both views share the same filters:

  • Search by name.
  • State, Type, Resolution, Tags, Assignee and Raised by.
  • Assigned to me for your own queue.
  • Closed items — closed items with no recent activity are hidden by default so the board stays readable. Change the window, or Show them, to bring them back.

Clear filters resets the lot.

Anatomy of a Work Item

FieldNotes
NameWhat the item is.
DescriptionMarkdown, with a preview tab while you write.
TypeIssue, Task, Defect or Observation.
StateOpen, In progress, Waiting, In review or Closed.
ResolutionHow it ended. Only recorded on closed items.
TagsFrom the project's shared tag catalogue.
AssigneeAn organisation member, or nobody.
ImageA project file path, or an external image URL.
LocationA point and a camera viewpoint in the scene.

Tags

Work item tags come from the same per-project catalogue as scene tags, and each tag records whether it applies to scenes, work items, both, or neither. If no tag in the project is enabled for work items you will be told so, with a link to the project settings — the catalogue is managed there, by someone with the Manage Projects permission.

Images

Paste or drop an image straight onto the item and it is uploaded into workitems/ in the project's files, then referenced from the item. That needs the Manage Files permission, since it writes to project storage. You can also point the field at a file already in the project, or at an external URL.

If you upload an image and then abandon the item without saving, you are offered the chance to delete the uploaded file rather than leaving it orphaned in storage.

Location

Location holds a point — an EPSG code and X, Y, Z — and a camera viewpoint. These are normally recorded for you by udStream when an item is raised from inside a scene, which is what lets somebody else open the item and be taken to the spot it describes. You can also enter a point by hand. Coordinates go in as a complete set: the EPSG code and all three axes, or none of them.

Changing State

Anyone with Edit Work Items can move an item between the everyday states. Two moves are treated differently:

  • Waiting requires a comment. Something parked with no explanation is worse than not parked at all, so the board is made to explain itself.
  • Closed requires the Resolve Work Items permission, and records a resolution: Fixed, Won't do, Duplicate, Not reproducible or No action required. Moving a closed item back out clears the resolution again.

Resolving is a separate permission from editing on purpose — deciding that something is finished is a different call from working on it.

Comments

Anyone who can see a work item can comment on it. Comments support markdown. You can edit or delete your own; deleting somebody else's needs the Manage Work Items permission.

Activity

Activity is the item's history — created, updated, assigned, deleted — recorded automatically as people work on it, alongside the comments. It is not editable, which is the point: it is the record of what actually happened.

Deleting

Delete removes a work item and needs the Manage Work Items permission.