[ASTPPCOM-837] Community version upgrade v4.0 to 5.0 - after upgrade success in v5.0 after update successfully Support Ticket Add-on, Existing data not displaying into grid in admin, reseller and customer portal. Created: 30/Oct/21  Updated: 09/Nov/21  Resolved: 01/Nov/21

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

Type: Bug Priority: High
Reporter: Prashant Kumar Assignee: Ashish Gohil
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 4h 16m
Original Estimate: Not Specified

Attachments: PNG File afterupgrade111 (1).png     PNG File afterupgrade111 (2).png     PNG File afterupgrade111 (3).png     PNG File afterUpgrade11.png     PNG File AfterUpgrade.png     PNG File chrome_5K7wGieS3j.png     PNG File chrome_5mp4MoTpak.png     PNG File chrome_9aID4IfHEe.png     PNG File chrome_hwSqlqOHHS.png    
Issue Links:
Relates
relates to ASTPPCOM-804 Community upgrade script verification Done
Reproducibility: always
Category: Functional
Edition: Community

 Description   

Steps :- 

  1. Install ASTPP v4.0
  2. Login as admin.
  3. Go to Get Addon > Community.
  4. Install  Support Ticket addon.
  5. Re-login as admin
  6. Go to Services > Support Ticket.
  7. Create Department and some some ticket. (Created records will be display in grid) 
  8. Now Upgrade ASTPP version 4.0 to 5.0
  9. After successful upgrade.
  10. Login as admin.
  11. Go to Get Addon >Community.
  12. Update Support Ticket Add-on.
  13. Re-login as admin/reseller/customer.
  14. Go to services > Support ticket.
  15. Verify existing records which have already created before upgrade in 5.0.

Actual result :- Existing Records are not displaying into grid.

Expected result :- It should be display in grid.

See Attached Screenshot :- 

 Comments   
Comment by Ashish Gohil [ 01/Nov/21 ]

This issue is resolve, changes done regarding as per comment.

PR

https://github.com/iNextrix/ASTPP/pull/629

Comment by Prashant Kumar [ 09/Nov/21 ]

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

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