Offshot of #1618. Make sure that JSON import dump as given by TG imports well. This depends on resolving other issues ([#1766], [#1767], etc).
what's the status on this one? The TG folks have sort of moved on to just hand importing only the open tickets, so the value here is just getting the kinks out of the import system.
Mark, this ticket is for test import of TG dump, just to make sure we can handle realistic data corpus as supplied by customers. I'm currently give priority to writing proper unit and integration tests for import functionality, and intend to do this final testing step once it's reproducibly clear that entire import pipeline works well.
Stats: import of TG dump (2443 tickets) into localdev took 76mins.
So, the dump imports well on localdev, but on sandbox it fails due to [#1899].
[#1899] was fixed and TG basically imports well, but there're some things to improve to make import process more ready for user availability:
Ok, the feature above were implemented, and entire TG dump has imported well (no user mapping was done): https://sf-psokolovsky-3020.sb.sf.net/p/test/tickets/
The code is in ps/1768 . The previous issues which precluded TG dump to import were fixed in other tickets (with tests added as appropriate), so this can be closed after review/merge. Alternatively, the TG dump can be imported another time, to get another perspective how usable it is. (TG dump was previously posted to sfengineers, I can attach it here if needed).
Log in to post a comment.