-
Type:
Enhancement
-
Status: Production Complete
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Recruit
-
Labels:None
-
Module:BenAdmin - Import
-
Reported by:Client
-
Item State:Production Complete - Closed
-
Issue Importance:Must Have
-
Sprint:WT Sprint 19
Import should support for recruit data import.
Details, deliverable and estimates to be filled once WT-6796 is completed.
- blocks
-
WT-8238 Import Recruit-DTS not showing for JOB data type import
-
- Closed
-
- causes
-
WT-7616 Export > Getting server error on LB on DTS and Field Mapping
-
- Closed
-
- is caused by
-
WT-5710 LONG Applicant data load into Workterra Stage
-
- Resolved
-
- relates to
-
WT-7608 Recruit- Candidate Data-Candidate social security No In DTS
-
- Closed
-
-
WT-7611 Recuirt:Job Data: specialization (DTS filed ) not showing on DTS page
-
- Closed
-
-
WT-7612 Recruit :Job Data:Duplicate entry inserted and import is getting failed.
-
- Closed
-
-
WT-7631 Recruit Job data-validation message is wrong
-
- Closed
-
-
WT-7633 Candidate Data import:Getting failed When we import same file second time
-
- Closed
-
-
WT-7634 Job Data Import Is getting Failed
-
- Closed
-
-
WT-7635 import template not getting open for Recruit Module
-
- Closed
-
-
- Time Spent:
- 5h
-
In Analysis, Understanding current implementation for Recruit module (Process, Implementation)
-
- Time Spent:
- 5h
-
Analysis on Implementation for Recruit Data
-
- Time Spent:
- 8h
-
Understand DB Structure
Populate DB fields for Candidate data import.
Added Import Type : Candidate Data and Job Data.
-
- Time Spent:
- 8h
-
Analysis
DTS Mapping for Candidate , Application , Jobs
-
- Time Spent:
- 1.5h
-
import code walk through
-
- Time Spent:
- 8h
-
Write a Business logic for Recruit Import
-
- Time Spent:
- 8h
-
Writing a Business logic for Recruit Import.
-
- Time Spent:
- 8h
-
Writing a Business logic for Recruit Import.
-
- Time Spent:
- 8h
-
Writing a Business logic for Recruit Import.
-
- Time Spent:
- 8h
-
Writing a Business logic for Recruit Import.
-
- Time Spent:
- 8h
-
Writing Business logic for Recruit Import.
-
- Time Spent:
- 9h
-
Writing business logic and unit testing for Candidate Import , Job Import , Job Application Import.
-
- Time Spent:
- 2h
-
Internal discussion about candidate import.
-
- Time Spent:
- 5h
-
Unit Testing and Implementation for Plain Text Password for Candidate.
-
- Time Spent:
- 0.5h
-
Candidate import discussion.
-
- Time Spent:
- 8h
-
Discussion on TableRef and Page ID mismatch.
Started Code changes to use existing page id to avoid duplication entries for pages.
-
- Time Spent:
- 1h
-
code review and follow up
-
- Time Spent:
- 8h
-
Code changes to avoid duplicate fields entry.
All changes are checked in to LB and it will deployed on LB with Next deployment patch.
-
- Time Spent:
- 1h
-
code review and discussion
-
- Time Spent:
- 2h
-
code review, discussion and follow ups
-
- Time Spent:
- 8h
-
Unit Testing and Code changes and Import file format creation.
-
- Time Spent:
- 9h
-
Unit testing , bug fixing , code fixes and deployment on LB.
-
- Time Spent:
- 7h
-
Bug fixing as reported in QA testing.
-
- Time Spent:
- 6h
-
tested on Stage with All reported issue
-
- Time Spent:
- 4h
-
Implemention for Dynamic Table Ref ID to avoid script failing issues.
-
- Time Spent:
- 2h
-
Code check in to Production.