feat: base Roster Management (backport #1760)

[mergify]

Roster Management

Extension of the current shift management feature to a full-fledged roster management system.

Features

Calendar View

Details

Visualization of Employee - Shift, Leave, and Holiday mapping in an Employee vs Day of the Month representation.

Search and Filtering

Details

• Employee Multi Search
• Filtering Based on Company, Department, Branch, Designation, and Shift Type

Shift Creation

Details

The roster allows for two types of shifts to be created.

Regular Shifts

Creating a regular shift results in the creation of a single Shift Assignment. Shifts spanning a week or less are automatically created as regular. For shifts spanning over a week, the user will have to select all days from the Repeat On Days field, under Schedule Settings, to ensure that a regular shift is created.

Repeating/Scheduled Shifts

The user has the option to turn shifts spanning over a week into repeating shifts. This can be done by selecting specific days from the Repeat On Days field and setting the Frequency field—which represents the frequency of repetition. Doing so will create a Shift Assignment Schedule with the selected details.

Shift Assignment Schedule is a new DocType that can be used for creating repeating shifts automatically. Apart from Shift Details, Repeat On Days, and Frequency, this DocType also has an Enabled field, which needs to be selected to continue creating shifts automatically, and a Create Shifts After field, which is the date after which shifts will be created. When enabled, shifts will be automatically created via a background job for 90 days following the Create Shifts After date, if that date lies before or on the day of the job running.

While creating repeating shifts using the roster, there can be three scenarios:-

• Shift spanning below 90 days: Shift Assignments are created immediately, and the Shift Assignment Schedule is not enabled.
• Shift with End Date, spanning over 90 days: Creation of Shift Assignments is enqueued, and the Shift Assignment Schedule is not enabled.
• Shift without End Date: Shift Assignments for 90 days are created immediately, and the Shift Assignment Schedule is enabled.

If Allow Multiple Shift Assignments for Same Date under HR Settings is enabled, multiple shifts can be created on a single day, provided that their timings do not overlap.

Shift Update

Details

End Date and Status fields of submitted Shift Assignments can be updated using the roster.

Shift Deletion

Details

Clicking on the Delete button presents the user with three options:-

• Shift for [Date]: Deletes the shift only on that date. This is done by updating the Shift Assignment and creating another one if needed.
• All Consecutive Shifts: Deletes the Shift Assignment altogether.
• Shift Assignment Schedule: Deletes the Shift Assignment Schedule and all the Shift Assignments associated with it.

None of these actions can be performed if there are Employee Checkin or Attendance records linked with the Shift Assignment at hand.

Shift Moving

Details

Shifts can be dragged and dropped to move them. Dropping a shift on another one will swap it with that.

Shift.Moving.mov

---

This is an automatic backport of pull request #1760 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of cf3b371 has failed:

On branch mergify/bp/version-15-hotfix/pr-1760
Your branch is ahead of 'origin/version-15-hotfix' by 42 commits.
  (use "git push" to publish your local commits)

You are currently cherry-picking commit cf3b37100.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   hrms/api/roster.py
	modified:   roster/src/components/MonthViewTable.vue
	modified:   roster/src/components/ShiftAssignmentDialog.vue

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   hrms/hr/doctype/shift_type/shift_type.json

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[frappe-pr-bot]

🎉 This issue has been resolved in version 15.28.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀