| Long text,summary | |
| "Good Morning Team | |
| On the last working day, I worked on GD-14 | |
| In which create leave update, delete and single user leave request API. | |
| Today's plan Will crate the cronjobs in GD-14","on the last working day, the sender worked on GD-14, specifically focusing on creating leave update, delete, and single user leave request APIs. The plan for today involves creating cronjobs in GD-14." | |
| "Good morning team | |
| Last working day task details:- | |
| :- Project setup in Mysql and mongodb database | |
| :- Setup to git | |
| :- install all dependency for the project. | |
| Today will work on jira card no. AA-06","tasks for the last working day included setting up a project in both MySQL and MongoDB databases, configuring Git for version control, and installing all necessary dependencies for the project. Today's focus will be on working on Jira card number AA-06." | |
| "Good morning everyone | |
| Starting of the day | |
| Today's Working Details | |
| Will work on pending task for team and other cards","The speaker greeted everyone and mentioned the beginning of the day. They outlined their plans for the day, which include addressing pending tasks for the team and other work cards." | |
| "Good morning team | |
| Yesterday’s task details | |
| Worked on card KD-53 Done | |
| Worked on teams flow and changes {in-progress} | |
| Todays task | |
| Will work on pr review points and remaining teams flow","Yesterday's Tasks: | |
| Completed work on card KD-53. | |
| Made progress on teams flow and implemented changes. | |
| Today's Tasks: | |
| Review pull request points. | |
| Continue work on remaining aspects of teams flow." | |
| "Good Moring Team | |
| Yesterday I worked on GD-14 in which I created | |
| Cronjob for auto approval leaves | |
| added new fields in the leave schema | |
| created cronjob for auto add leave to leave bucket(inprogess) | |
| Todays | |
| will finish auto add leave to leave bucket and will create an PR for leave module V2.","Yesterday, I focused on GD-14, where I accomplished several tasks including setting up a Cronjob for automatic leave approval, integrating new fields into the leave schema, and implementing a Cronjob for automatically adding leave to the leave bucket when it's in progress. Today, my plan is to complete the automation for adding leave to the leave bucket and initiate a pull request for the leave module Version 2." | |
| "Good Morning team | |
| Yesday's working details-- | |
| Worked on card KD-48 for updating | |
| Debug members add issue due to radius field | |
| Worked on user deletion bug for team | |
| restructure code of announcement to ts file and minor correction | |
| Todays Task | |
| Will work on remaining things and bug points","Yesterday's tasks included working on card KD-48 to implement updates, resolving an issue related to adding members due to a radius field, fixing a bug concerning user deletion within the team, and restructuring the code for announcements into a TypeScript file with minor corrections. | |
| Today's agenda involves completing remaining tasks, addressing any remaining bugs, and ensuring the smooth progression of ongoing work." | |
| "Good morning Team | |
| Yesterday's task details | |
| Worked on Wellify project | |
| 1 Intergeted update admin API & admin edit model {Done} | |
| 2 integrated get API in users {Done} | |
| Today's task- | |
| Continue working on the wellify project","Yesterday, the team focused on tasks related to the Wellify project. They successfully integrated an update admin API and completed the admin edit model. Additionally, they integrated a get API into the users section, completing these tasks as planned. Today's agenda includes continuing work on the Wellify project." | |
| "Good Morning Team | |
| app name - vendor admin | |
| created a common context to manage order state globally - done | |
| hide update and cancel status on behalf of is_cancellable key - done | |
| integrated update order status API - done | |
| cancel order button functionality - done | |
| app name - dot | |
| show the service logo on the dispatch dropdown - done | |
| fixed the default selected service on the dispatch page - done | |
| fixed the marker location precision issue - done | |
| integrated vendor details API on the dispatch card - done | |
| show vendor logo and vendor name on dispatch card - in progress | |
| designed the badge to show status and its color as per status - in progress | |
| show placeholder images where the image is not available on the dispatch card - in progress","The team accomplished several tasks across two applications, ""vendor admin"" and ""dot"". For ""vendor admin"", they successfully implemented a common context for managing order state globally, hid update and cancel status based on a specific key, integrated an update order status API, and ensured the functionality of the cancel order button. As for ""dot"", they displayed the service logo in the dispatch dropdown, fixed issues related to default service selection and marker location precision, and integrated vendor details onto the dispatch card. Currently, they're working on displaying the vendor logo and name on the dispatch card, designing badges to show status and color accordingly, and implementing placeholder images for cases where images are unavailable on the dispatch card." | |
| "Good morning everyone | |
| App Name: Vendor Admin | |
| App name :- vendor admin | |
| Implemented all status deactive then show all orders - done | |
| Fixed issues filter not working on today order fetching data every 5 sec - done | |
| Create common component for shorting and show drop-down - done | |
| Implemented functionality for shorting ascending and descending - in progress | |
| Today's working details :- | |
| Continues with vendor admin project","Good morning, progress updates were provided for the Vendor Admin application. The team successfully implemented functionality to display all orders when all statuses are deactivated. They also resolved an issue related to the filter not functioning correctly when fetching today's orders data every 5 seconds. A common component for sorting and displaying dropdown options was created. Additionally, work began on implementing functionality for sorting orders in ascending and descending order, which is currently in progress. The team continued their work on the Vendor Admin project throughout the day." | |
| "Good Morning Everyone | |
| Starting of the day | |
| Yesterday's working details-- | |
| Worked on write for delete roles | |
| Worked on check the flow of checkIn and checkout API | |
| Today's working details-- | |
| Will work on remaining work","The speaker greeted everyone and initiated the day. They provided a brief overview of their work from the previous day, mentioning tasks such as writing code for deleting roles and reviewing the flow of the check-in and checkout API. For the current day, they plan to continue with pending tasks." | |
| "Good morning team | |
| Yesterday's completed work | |
| Yun Express Tracking | |
| Worked on fixing the issue of the corn job. | |
| Worked on the status of the order list module. | |
| ZestHrm Project | |
| Worked on the My projects of the dashboard module. | |
| Today's work plan | |
| Working on the code optimisation of dashboard module.","Yesterday, the team accomplished several tasks including resolving issues with Yun Express Tracking and fixing the corn job problem. They also made progress on the status of the order list module and worked on the My Projects feature of the ZestHrm Project dashboard module. Today's plan involves focusing on optimizing the code of the dashboard module." | |