Skip to content

full check view/form #9

Description

@christianschaeffer

A process for performing full checks of a container / resource.

The process should guide users though the whole structure of the checklist. At least one full check view / form is required.

For each checklist item, one must be able to...

  • ...record the amount of items
  • ...record one (or several) expiry dates for the recorded items
  • ...say "all is good" and/or "same as last time" with a simple button press

In order to a) not overload the form views and b) not have to many steps, the full check process should be grouped by checklist compartment, i.e. have one view per compartment.
The "all is good" and/or "same as last time" button should also be usable for a full compartment, to simplify the process further.

One the whole checklist was traversed, the result must be confirmed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    [C] featureNew feature or request[P] majorImportant features or bugs that should be considered first

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions