Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relative timeframe validation not working correctly #240

Open
lucafwp opened this issue Jun 5, 2024 · 0 comments · May be fixed by #244
Open

Relative timeframe validation not working correctly #240

lucafwp opened this issue Jun 5, 2024 · 0 comments · May be fixed by #244
Assignees
Labels
bug Something isn't working

Comments

@lucafwp
Copy link

lucafwp commented Jun 5, 2024

Describe the bug

When selecting a relative timeframe the text validation accepts string clearly not valid

To Reproduce

Steps to reproduce the behavior:

  1. Create a new time frame
  2. Check "Relative start"
  3. Insert following text as Start: -2 banana
  4. Check "Relative end"
  5. Insert following text as End: -1 banana
  6. Create a report using newly created Timeframe
  7. Generate the report

Expected behavior

Validation should accept only valid strings.

Screenshots

image

image

Your Environment

  • Module version: 1.0.2
  • Dependent module versions:
    ** icinga-php-library: 0.13.2
    ** icinga-php-thirdparty: 0.12.1
  • Icinga Web 2 version and modules (System - About): 2.12.1
  • Web browser and version: Chrome Version 125.0.6422.141
  • Icinga 2 version used (icinga2 --version): 2.14.2-1
  • PHP version used (php --version): 8.3.6
  • Server operating system and version: Ubuntu 24.04
@sukhwinder33445 sukhwinder33445 self-assigned this Jul 23, 2024
@sukhwinder33445 sukhwinder33445 added the bug Something isn't working label Jul 23, 2024
@sukhwinder33445 sukhwinder33445 linked a pull request Jul 23, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants