PNE-1548 | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 66822cc9-cc0c-3dea-9001-d658bc73fee4 |
---|
key | PNE-1548 |
---|
|
Currently shift data resides in a series of monthly xml files. This information needs to be moved in to the database. Copied from Jira Legacy |
---|
server | System JIRA |
---|
serverId | 66822cc9-cc0c-3dea-9001-d658bc73fee4 |
---|
key | PNE-566 |
---|
|
Create 3 database tables to migrate information from files to DB (Shift Mapping, Shift Pattern and Shift Schedule) - 1-2 days Write a utility to migrate existing data from files to Database, figure out how to handle missing files like ShiftPattern on some machines - 4 days Change the loading of shift information from database instead of files for reporting - 3 days Change the Shift Calendar saving to database (currently files are generated on front end and sent back via fupload) - 8 days Change the API for copying shift calendar from one machine to another - 3 days Change how schedule is autogenerated from pattern file once the existing schedule runs out (2 years apply forward) - 3-4 days The ability to copy shifts from machine to machine available from PEConfig’s clone machine/copy settings
DetailsDesignDatabasehttps://dbdiagram.io/d/61684ced940c4c4eec95e3d3 Demohttps://www.db-fiddle.com/f/5j1zjMq8atqMy4wLwx3yZs/38 |