Negative Values Accepted in Enatega Multivendor Admin Dashboard Fields

Open

#1,500 opened on May 8, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 42/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Quiet
Tech stack: javascript
Domain: frontend

Research direction

Start by locating the Enatega Multivendor Admin dashboard fields described in the issue and reproduce the behavior in Chrome with negative inputs. Identify which fields should reject negative values and verify that submission is blocked with an error message for those fields.

Written by the indexing model from the issue text.

Description

Describe the bug
A bug has been identified in the Enatega Multivendor Admin dashboard where negative values are being accepted in certain fields. This behavior can lead to inaccurate data representation and potential miscalculations. It is crucial to rectify this issue to ensure the reliability of the information presented in the dashboard.

To Reproduce
Steps to reproduce the behavior:

Log in to the Enatega Multivendor Admin.
Navigate to the dashboard or relevant section.
Attempt to input negative values in applicable fields (specify fields where negative values are accepted).
Observe that the system allows the entry of negative values without generating an error.
Expected behavior
Negative values should not be accepted in fields where they are not applicable. The system should validate the input and prevent the submission of negative values, providing an error message if attempted.

Screenshots
image
image
image
image
image
image

*Desktop:

Browser: chrome

Dominant language: JavaScript
Stars: 0
Forks: 0
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.