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

Estimates: New estimate: "Amount" is not marked as obligatory. #41

Closed
Clairebaer opened this issue Apr 22, 2024 · 0 comments
Closed

Estimates: New estimate: "Amount" is not marked as obligatory. #41

Clairebaer opened this issue Apr 22, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@Clairebaer
Copy link

Describe the bug
New estimate: "Amount" is not marked as obligatory. When trying to save an error occurs:
SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'amount' cannot be null

To Reproduce
Steps to reproduce the behavior:

  1. Go to Estimates
  2. Click on "New estimate"
  3. Fill out project and title, leave "Amount" empty
  4. Click on "Save"
  5. See error

Expected behavior
"Amount" is marked as obligatory. Saving without an amount is not possible (a notice of missing information is shown).

Screenshots
If applicable, add screenshots to help explain your problem.

estimates-amount-cannot-be-null

System (please complete the following information):

  • Sales version: 2.1.9
@devmount devmount self-assigned this Apr 22, 2024
@devmount devmount added the bug Something isn't working label Apr 22, 2024
@devmount devmount closed this as completed May 3, 2024
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

No branches or pull requests

2 participants