search

dickinson-comp190 / GitKit-FarmData2-F23

Other
0 stars 20 forks source link

Seeding Report: Allows Invalid Inputs #54

Open braughtg opened 11 months ago

braughtg commented 11 months ago

Description: Users are able to enter invalid inputs such as negative values into the Seeding Input Log of FieldKit

Steps to replicate this problem:

  1. Log into FarmData2 with the correct user credentials
  2. Click on the tab FieldKit and then click on Seeding Input
  3. Under the label "Labor" fill in a negative value for workers and time
  4. Click submit and Generate Report

Observed Output

image

Desired Output

There should not be a bottom error option available to click to generate a negative value.

Issue by anlai46 Thursday Dec 16, 2021 at 08:52 GMT Originally opened as https://github.com/DickinsonCollege/FarmData2/issues/344

braughtg commented 11 months ago

Really nice bug report. This identifies the same issue as #333, which also highlights an issue with decimal values for some fields. This issue is being closed but will be referenced from that one.

Comment by braughtg Wednesday Dec 22, 2021 at 16:19 GMT

longbui23 commented 10 months ago

This is a duplicate of ticket #53, so it should be closed.

QuangPhung15 commented 10 months ago

This is a duplicate of #53 and should be closed.

Doquanglong commented 10 months ago

This is a duplicate of #53 and should be closed.

linhkhanhhoang commented 10 months ago

This should be closed since it is a duplicate of #53

evelynpham04 commented 10 months ago

This ticket should be closed because it is the duplicate of #53

SpencerGoodman commented 10 months ago

53 already points out this issue. This ticket should be closed.

FoxFGC commented 10 months ago

The issue is a duplicate of ticket number #53. This ticket should be closed.

jadoont commented 10 months ago

This issue is a duplicate of the ticket #53. It should be closed.

darcelypena commented 10 months ago

This is a duplicate of #53. Therefore, this ticket should be closed.

AzizbekMuminoff commented 10 months ago

This issue is a duplicate of the issue #53. Thus, it should be closed

Cubin1215 commented 10 months ago

This issue is already mentioned in issue #53. Therefore, it should be closed.

dlkm20041130 commented 10 months ago

This bug has been reported already, it is a duplicate of ticket #53.

shaikhibrahim2000 commented 10 months ago

This ticket should be closed since it is a duplicate of ticket #53.

YoussifGoda commented 10 months ago

This is a duplicate of #53. Thus, this ticket should be closed.