Back
Similar todos
- follow up on the TNM activity replacement ā
#enpvqp
- add new TNM linkage ā
#enpvqp
- changes to ASP add form > 383 AOB short term ā
#enpvqp
- changes to ASP edit form > 383 AOB short term ā
#enpvqp
- Outline the changes required to allow IM to self-repush TNM ā
#enpvqp
- test the new report for TNM ā
#enpvqp
#enpvqp - fix the bugs found for TNM ā
2. investigate why TNM got stuck ā
#enpvqp
3. solve the TNM pull from PDB hotfix that was discovered today ā
#enpvqp
2. fix the issue abt the change name in tnm person auto recalculate team display ā
#enpvqp
- meeting abt how to proceed with the new fields for AOB type ā
#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 ā
- deploy changes ā
#enpvqp
- deploy latest changes for enpvqp ā
#enpvqp
4. changes to ASP excel to vendor > 383 AOB ā
#enpvqp
- change query for tableau to pull AOB data ā
#enpvqp
- deploy fix MTT-596 ā
#enpvqp
- and deploy the newest change ā
#enpvqp
#enpvqp šµšš®
- ā translate the first step of outline in [[IM DIY push TNM (MTT-521)|issues.MTT-521]] into first code change ā
- some data admin ā
#enpvqp šµšš®
- š NJ team unable to access TNM ā
- execute the 4th step of outline in [[IM DIY push TNM (MTT-521)|issues.MTT-521]] into code change => spent 3 hrs on this. still stuck ā