[ASTPPCOM-1270] Status is not change as false for 400 response of bad request Created: 10/Oct/22  Updated: 13/Oct/22  Resolved: 13/Oct/22

Status: Closed
Project: ASTPP Community
Component/s: None
Affects Version/s: v6.0
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Yash Shah Assignee: Kinjal Prajapati
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 3h 11m
Original Estimate: Not Specified

Attachments: PNG File Customer_Delete.png     PNG File DID_Delete API.png     File DIDListAPI_400StatusIssue.mp4     File Origination_Rate_list_API.mp4     PNG File Product_Delete_API.png     File Product List API.mp4     File Rate_Group_API.mp4     File Rate_Group_list_API.mp4     File Termination_Rate_ListAPI.mp4    
Issue Links:
Blocks
blocks ASTPPCOM-975 Create API For Community V6 Version Done
Reproducibility: always
Category: UI
Edition: Community

 Description   

Steps :

1. Login as Admin
2. Go to tarrif > Rate Group > Rate Group List API
3. Now check response for every api for 400 request

Expected result : For 400 code, status should be changed as False.

Actual result : For 400 code, status is display as true.

Note: Kindly check every API of Admins as well as customer's api. Also check screenshots/videos for other API issue of status

Note : This issue is also facing in Origination Rate List API, Rate Group List API, DID List API in Validation.

 Comments   
Comment by Kinjal Prajapati [ 11/Oct/22 ]

Changed status from true to false if we got 400 in the response.

https://gitlab.com/inextrix/ITPLATP/ASTPPCOM/-/merge_requests/846/diffs

 

Comment by Yash Shah [ 11/Oct/22 ]

Working fine as expected

Comment by Yash Shah [ 12/Oct/22 ]

Facing issues in below API
DID List API - Call type, County_id, accountid, status (Paramters) 400 status True Display, so kindly change this.

Comment by Kinjal Prajapati [ 12/Oct/22 ]

https://gitlab.com/inextrix/ITPLATP/ASTPPCOM/-/merge_requests/855

Comment by Yash Shah [ 13/Oct/22 ]

Working fine as expected

Generated at Sat Feb 10 07:24:38 CET 2024 using Jira 8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a.