FSM UI/UX Audit

	Type	Estimation (in hours)	Assignee	Comment	Status	Reviewed by PM	Gaps (if any)		Reviewed by Antriksh
FSM home breadcrumb title all should align	Improvement	2	Anil Singha		Done	Y			Y
All text alignment should be left for FSM registry table	Improvement	2	Anil Singha		Done		Disable button alignment, Figure our dropdown	Antriksh will share design
The date of vehicle creation camel case needs to be fixed	Improvement	0.5	Anil Singha		Done	Y
Alignment of breadcrumbs and title should be out of the card and left	Improvement	3	Anil Singha		Done	Y
Vehicle details title and second card should be aligned	Improvement	2	Anil Singha		Done	Y
Remove the break line in the FSM details page	Improvement	2	Anil Singha	Follow Design same as New Desludging Application	Done	Y	Spacing between section header, field above and field below
(+91) in every mobile input field need to be added if it is not major changes	Improvement	16		91 Should be every where there is mobile number field	Done		Some are in old format and some are in new format	Look at entire application and check where gaps are
The rupee symbol needs to be removed from the left side and symbols should be left aligned	Improvement	2	Anil Singha		Done		Rupee is still coming on the left hand side in application form	Also look at the entire application and check where gaps are
Add vendor card need to be alligned for vehicle	Improvement	3	Anil Singha		Done
Add vendor pop-up close circle need to follow the Figma design, pop-up does not align for text properly	Improvement	2	Anil Singha		Done
Update trips, add driver, add vendor, add driver modal cancel icon need to be corrected	Improvement	2	Anil Singha		Done
Remove top padding in vendor/vehicle/driver details screen	Improvement	2	Anil Singha		Done
Vendor/driver/vehicle details screen title-breadcrumb-card should be aligned properly	Improvement	4	Anil Singha		Done
Vendor/driver/vehicle edit screen title-breadcrumb-card should be aligned properly	Improvement	Anil Singha		Done
Vendor/driver/vehicle edit screen title should be outside card	Improvement	Anil Singha		Done
Vehicle number search box in the vehicle tab should check the correct format	Improvement	2	Anil Singha		Done
HOME SCREEN REMOVE	Improvement	2	Anil Singha		Done
Pincode validation	Improvement	16			Done
Roles permission for FSM inbox links are not proper	Improvement	3	Anil Singha		Done
In collector screen, error for incorrect phone number is showing as Payment_Invalid_Mobile	Localisation	0.15	Anil Singha		Done
Sorting FSM inbox should follow common inbox for vendor/driver/vehicle tab -backend	Improvement	12	Sardar Shaik		Done
Sorting FSM inbox should follow common inbox for vendor/driver/vehicle tab- UI	Improvement	12	Anil Singha		Done
The vendor name dropdown UI sould be according to the Figma link and align left	Improvement	18	Anil Singha		Done
Show only go back to home if has only go back to home else show take action + If only one action is present in take action, then show only the action name	Improvement	12	Nabeel Md		Done
Redirection from SMS for payment, Showing as ES_PAYMENT_DETAILS_TOTAL AMOUNT and ES_PAYMENT_DETAILS_ADV_AMOUNT	Localisation		Anil Singha		Done
Wherever input text does not match validation, error message needs to show in real-time	Improvement	40		Blocker	Todo
Change is redirected to a page in form and then the entire form restarts. Expected action: Change button should go to required page and then Next button should go back to the same page	Improvement			Common Issue in Every Module. Antriksh, Jagan and team is looking into it
Different terminologies found for Payment Method. In the Generate Receipt page (Payment mode -> Cash, Cheque, Credit/Debit Card) where as In Complete Request Page (Payment Received -> Paid In Cash, Paid at Counter, Net Banking).	Improvement			Need Clarity on what method should be populated?
Receipt capacity instead of type	Improvement			Dependency on Backend PDF Service	Todo
Vehicly type and payment sections should be separate	Improvement			Dependency on Backend PDF Service	Todo
Receipt needs to be redesigned				Dependency of Core Team. Since Receipt is a core services
FSM registry table should be common component	Improvement	16		Already common component is using	Todo
Either we can keep the option for the advanced amount and full amount in collect page for citizen, or remove the option <Tahera will get back on this	Improvement		Tahera Bharmal	Addressed in Frontendedback section of advance pay	Todo	Will be covering in Advance Pay Section
Pay Now and Pay Later looks a little confusing. Check the localisation with other modules	Improvement		Tahera Bharmal	Addressed in Frontendedback section of advance pay	Todo	Will be covering in Advance Pay Section
After clicking pay now, it is showing advance amount which looks a little confusing. Need to check with PO	Improvement		Tahera Bharmal	Addressed in Frontendedback section of advance pay	Todo	Will be covering in Advance Pay Section
Login error message "This MobileNumber Already Register as UserName in System. Pls try Another UserName"/ Reword to "This Mobile Number Already Register in the System. Please try Another UserName"	Improvement	1		Core team work	Todo
Test the entire product					Todo
Scroll up to the field	Improvement	12			Todo
Next button should be disabled when data is not filled; next button usage is currently inconsistent	Improvement		Nabeel Md
View application screen for citizen should have data in the same format as the acknowledgement receipt	Improvement			new UI has to be developed on figma first