[ASTPPCOM-1240] Rate Group Create API - Validation message not display for invalid trunk_id, status and reseller_id parameter Created: 03/Oct/22  Updated: 19/Oct/22  Resolved: 19/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: 2h 59m
Original Estimate: Not Specified

Attachments: File IssueFacing.mp4     PNG File StatusNotchanged.png     File ValidationNotAppliedOnTrunk_id.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 Create API
3. Now enter valid input for all parameters and enter characters for trunk_id, status and
reseller_id parameter and run the api
4. Now check response

Expected result : Validation message should be display for Invalid trunk_id, status and
reseller_id parameter.

Actual result : API run succeessfully and 200 response code get for Invalid Trunk_id, status and reseller_id parameter.



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

This issue has been resolved in the below MR.

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

Comment by Yash Shah [ 10/Oct/22 ]

Validation message is display it's fine but Status not changed in response as False. so it's issue.
AND I also edited issue. so please also check and apply validation for status and reseller_id parameters.

Comment by Kinjal Prajapati [ 10/Oct/22 ]

Changed status from true to false in the RateGroup create API.

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

Comment by Yash Shah [ 11/Oct/22 ]

Still facing issue in status and reseller_id parameter. So it's issue

Comment by Kinjal Prajapati [ 11/Oct/22 ]

Please take the latest pull and verify this issue.

Comment by Yash Shah [ 12/Oct/22 ]

I am moving this issue into resolved Because it's closed by Neetu Nogia.

Comment by Yash Shah [ 12/Oct/22 ]

Working fine as expected

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