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

The year cannot be typed in a date filter #7276

Closed
damians-filigran opened this issue Jun 9, 2024 · 0 comments
Closed

The year cannot be typed in a date filter #7276

damians-filigran opened this issue Jun 9, 2024 · 0 comments
Assignees
Labels
bug use for describing something not working as expected filters & search Linked to search results and filtering engine solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@damians-filigran
Copy link

Description

When trying to enter the date in a date filter (eg. on creating a dashboard), the year cannot be typed.

Environment

  1. OS (where OpenCTI server runs): SaaS
  2. OpenCTI version: 6.1.10
  3. OpenCTI client: Frontend Edge on MacOS
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Go to an editable dashboards
  2. Create a new widget
  3. Select filter "Creation date / greater than"
  4. Type the date (region setting is MM/DD/YYYY)

Expected Output

The UI should accept the date. eg. 06/01/2024

Actual Output

First, when the MM field is highlighted, the first keypress 'bounces out of focus' before being able to enter a value
Second attempt, the MM and DD fields accept input, but the YYYY field only accepts the first keypress. It uses the first digit entered taken (eg. "2") as the '1's value. (eg. "2002").

Additional information

Recording available

Screenshots (optional)

@damians-filigran damians-filigran added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Jun 9, 2024
@Jipegien Jipegien removed the needs triage use to identify issue needing triage from Filigran Product team label Jun 10, 2024
@Jipegien Jipegien added this to the Bugs backlog milestone Jun 10, 2024
@SarahBocognano SarahBocognano self-assigned this Jun 18, 2024
@Jipegien Jipegien added the filters & search Linked to search results and filtering engine label Jul 1, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jul 10, 2024
daimyo007 pushed a commit to fbicyber/opencti__opencti that referenced this issue Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected filters & search Linked to search results and filtering engine solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

4 participants