Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • GGCE Server GGCE Server
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GGCE
  • GGCE ServerGGCE Server
  • Issues
  • #43
Closed
Open
Created Jun 16, 2020 by Matija Obreza@mobrezaOwner

Reporting: Availability indicator

@ncastaneda the proposed indicator is composed of:

  • health - conducted at inventory level.
  • viability - conducted at inventory level.
  • quantity sufficiency - conducted at inventory level.

Let's focus on viability. There are potentially multiple viability tests (and their results) per inventory.

I assume you want only the results of the last test. Even so:

  1. What is sufficient viability threshold so that the material considered viable?
  2. If the test is 10 years old, how do you consider the time since the test in marking something as sufficiently viable?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking