AFC

Private

Project *AFC ai genetic for bench sales APPFORSOLARArrow LogisticsArtificial Intillegence  » Algo Trade Automation  » Algo Trade Manual  » Bulk mail Automation with web interface  » Bulk Mail Service For Bench Sales  » Code Generation Tool  » Cold Emailing Automation (AI-Driven)  » Invoice Inventory Automation  » invoice to inventory for evergreen  » Test Automation  » What's app Bulk messaging with AI agents  » Zelle Payment for evergreenAsk RideBowls&blendsCharan Technologies _ DevelopmentEver green Farms USA (static website)Evergreen farms (pos)Evergreen React ApplicationFinwareHackthonLucky BraidsMy Produce StandNexPumpNexZen Printer AgentNoxa_JewelleryOffice Requirments  » Daily Tasks For Madhu  » Employees requirements  » Recruitment senior mern stack developer  » Red MIne Speed  » Senior Mern Stack DeveloperOPT - (USA) UpdatesQA TestersRare FruitsRegal SolarRegal Solar DMRegal Solar Energy_ ReactReliance Home Builders_ reactRemit2AnyRestaurant POSRSVPRushi GardensRV_ EngraverSoloar AppSri Farms _ DMSri_FarmsSuthra OneSuthra QNova LabsTech FourceTechnical RequirementsTechy_DevelopmentTechy_POS Travel Matex

Tracker *Bug Feature Support Testing

Subject *

Description Edit *Request Page issues* *1. Created By Field Issue (List Page)* *Issue:* In the Created By column, a hyphen (-) is displayed when the user does not have a last name. *Expected* : Display the available name (e.g., First Name only), OR *2. Request Template & Customer Selection Behavior* *Issue:* The placeholder indicates that the request template selection is independent of customer selection. However, when a request template is selected, the customer field is also getting auto-selected. *Expected:* Either enforce dependency (and update placeholder accordingly) *3. Property Location Issue* *Issue:* Property location is not displaying or behaving correctly (inconsistent or incorrect data). *Expected:* Property location should display accurate and consistent data across all request views. *4. Site Visit Fields Editable After Completion* *Issue:* Even after Site Visit is marked as completed, the user is able to edit site visit details in request edit mode. *Expected:* Once site visit is completed, all related fields should be disabled (read-only) to prevent further modification. 5. Incorrect Action History Logging *Issue:* When editing a request without making any changes, the action history logs an update (e.g., Transport: 0 → 150). *Expected:* No history entry should be created if there are no actual changes. *6. Mandatory Field Validation Missing* *Issue:* When mandatory fields are left empty, there is no clear visual indication for the user. *Expected:* All mandatory fields should be highlighted in red with proper validation messages when not filled.