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.

Sign up for GitHub

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

Jump to bottom

Max confidence level in user disabled field #6294

Closed
SamuelHassine opened this issue Mar 9, 2024 · 0 comments
Closed

Max confidence level in user disabled field #6294

SamuelHassine opened this issue Mar 9, 2024 · 0 comments
Assignees
@frapuks
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Release 6.0.6

Comments

@SamuelHassine
Copy link
Member

Description

  1. Go to a user
  2. Update it
  3. Put a max conf level to 400
  4. Field is disabled and you cannot go back to 100 (error is normal)
@SamuelHassine SamuelHassine added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team and removed needs triage use to identify issue needing triage from Filigran Product team labels Mar 9, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.6 milestone Mar 9, 2024
@frapuks frapuks self-assigned this Mar 11, 2024
frapuks added a commit that referenced this issue Mar 11, 2024
@frapuks
[frontend] dont disable when value > limit (#6294)
0376a1f
@frapuks frapuks mentioned this issue Mar 11, 2024
Merged
5 tasks
frapuks added a commit that referenced this issue Mar 12, 2024
@frapuks
[frontend] dont disable when value > limit (#6294)
2092cfa
frapuks added a commit that referenced this issue Mar 12, 2024
@frapuks
[frontend] use initialValue to manage disable (#6294)
62c5442
frapuks added a commit that referenced this issue Mar 12, 2024
@frapuks
[frontend] dont disable when value > limit (#6294)
698b5a3
@frapuks frapuks added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 12, 2024
@frapuks frapuks closed this as completed Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@frapuks frapuks

Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
Release 6.0.6
Development

No branches or pull requests
2 participants
@SamuelHassine @frapuks