[ASTPPCOM-764] Community upgrade :- Order view:- Registration date and next billing date is wrong displaying in order view page. Created: 07/May/21  Updated: 25/Oct/21  Resolved: 19/Oct/21

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

Type: Bug Priority: Medium
Reporter: Prashant Kumar Assignee: Ashish Gohil
Resolution: No Change Required Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 55m
Original Estimate: Not Specified

Attachments: PNG File 1days.png     PNG File 30daysorder.png     PNG File 4Days.png     PNG File chrome_fXw0AsiRY9.png     PNG File chrome_KKtzIm8cvI.png     File Registration date-next billing date wrong display.mp4    
Issue Links:
Relates
relates to ASTPPCOM-804 Community upgrade script verification Done
Reproducibility: always
Category: Functional
Edition: Community

 Description   

Order view:- Registration date and next billing date is wrong displaying in order view page.

Steps to Reroduces:-

===================================

  1. Login as Admin/customer.
  2. Go to services.
  3. Go to Order new.
  4. Assign any product to the customer.
  5. Now Click on order id and verify Registration date and Next billing date.

Actual Result:- Next billing date taking as one day extra from actual date.

Expected Result:-  Registration date and and Next billing date should be take proper according to billing days.

For example:-

  1. If product has one day purchased 18/10/2021 then it should be display as Register date= 18/10/2021 and next billing/terminated date=  19/10/2021.
  2. if product has daily recurring purchased 18/10/2021 then it should be display as Register date= 18/10/2021 and next billing date=  19/10/2021.
  3. if product has 2 days recurring purchased 18/10/2021 then it should be display as Register date= 18/10/2021 and next billing date=  20/10/2021.

See Attached latest screenshot :- 



 Comments   
Comment by Ashish Gohil [ 19/Oct/21 ]

As i was checked for the same it working as expected, see attached screenshot.

Comment by Prashant Kumar [ 25/Oct/21 ]

Verified in latest source, after upgrade in v5.0, change applied done, working fine 

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