Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • satnogs-network satnogs-network
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 192
    • Issues 192
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • librespacefoundationlibrespacefoundation
  • SatNOGSSatNOGS
  • satnogs-networksatnogs-network
  • Issues
  • #862
Closed
Open
Issue created Aug 22, 2022 by Fabian P. Schmidt@kerel-fsDeveloper

/observations/new: Show valid range for "Split Duration" field

🐞 Problem

When using the "Split Duration" option, the valid input range is not known to the user. When the user entered an invalid value it doesn't show an error but uses the default value of 720 seconds. This is confusing. By experimentation I found 121 seconds to be the minimum accepted value (which is useful for testing during station development).

💡 Possible Solution

Add a comment or tooltip which lists the accepted range, or alternatively fail on invalid inputs with an error message.

Edited Aug 22, 2022 by Fabian P. Schmidt
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking