Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • L LILAC
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 55
    • Issues 55
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LILAC
  • LILAC
  • Issues
  • #45

Closed
Open
Created Jun 19, 2019 by Lily Romano@nrr004Owner0 of 2 tasks completed0/2 tasks

Reword the scan status section

  • Possible enums (check on pickling)
  • Status persistence [Maybe a separate user enabled/disabled flag with message presentation]
    • The code flagged the scan invalid for some reason
    • The user marks the scan valid - The original codes are wiped out
    • The user then marks the scan invalid again
    • The original scan invalidity should be maintained somewhere. If the user marked it disabled again in the event of enabling it in error, they can no longer see the original status
Edited Jun 19, 2019 by Lily Romano
Assignee
Assign to
Time tracking