Back
Similar todos
- diagnose the issue of the 3x push to PDB ✅ #enpvqp
7. fix the auto push to PDB for QMWD3PP quotes ✅ #enpvqp
- test the push to PDB for SG quotes ✅ #enpvqp
6. look into the autopush to PDB for QMWD3PP quotes ✅ #enpvqp
- follow up on push to SG for PDB see if they work ✅ #enpvqp
8. fix the auto pull from PDB for QMWD3PP quotes ✅ #enpvqp
- allow PMSD3PP to work within the ASP linkage house ✅ #enpvqp
#enpvqp 🇵🇭📮
- ⭐ change the url for PDB production ✅
- ⭐ ensure the fix for the TNM repush tests are all okay ✅
- ⭐ deploy the changes and alter the states for 3PP and TNM where necessary ✅
- follow up on stuck QMWD ✅
- fix data issues for transfer of PDB url ✅
2. fix the stuck in pdb for res and PSS ✅ #enpvqp
- test the fix for push to PDB for SG quotes in production environment ✅ #enovqp
- fix the push to PDB for SG quotes ✅ #enovqp
- make ASP linkage document to work with PMSD3PP as well ✅ #enpvqp
added 3 test cases for the stuck in PDB situation for #enpvqp
- deploy and test the above fixes ✅ #enpvqp
- deploy bug fix and test ✅ #enpvqp
- deploy changes ✅ #enpvqp
- when push to PDB use this new user_facing_id_number ✅ #enpvqp
#enpvqp 🇵🇭📮
- ⭐️ fix the tests in [[IM DIY push TNM (MTT-521)|issues.MTT-521]] (2/5) => (3/5) (allocated: <= 60 mins) ✅
3. deploy new version ✅ #enpvqp
- also investigate to diagnose possible root cause for the failure to force push ✅ #enpvqp