v15.60.4

frappe/hrmsv15.60.4Jun 3, 2026by frappe-pr-bot

AI Summary

This patch release addresses bugs in Salary Slips, Leave Allocations, and Expense Claims, ensuring component settings are preserved and statuses update correctly. It also introduces a buffer period for Shift Assignments to prevent premature inactivation.

Key Highlights

  • Restores 'Do Not Include in Accounts' and 'Exempted From Income Tax' fields in Salary Slip.
  • Fixes Leave Allocation expiry logic to reset values and hide specific fields for earned leave.
  • Resolves Expense Claim status issues when claims are partially covered by advances.
  • Adds a one-day buffer for Shift Assignment records to stay active after their scheduled end date.
  • Attendance requests now correctly fill in the Shift even if the related assignment is inactive.

Full Release Notes

## Bug Fixes
* Adds the missing _Do Not Include in Accounts_ and _Exempted From Income Tax_ fields to **Salary Slip**, so these salary component settings are carried over when a slip is created. (https://github.com/frappe/hrms/pull/4567)
* When a **Leave Allocation** expires, its _New Leaves Allocated_ and _Total Leaves Allocated_ values reset to 0, and the form refreshes so the updated values appear immediately. The _New Leaves Allocated_ field is hidden for earned leave allocations. (https://github.com/frappe/hrms/pull/4559)
* Fixes **Expense Claim** so claims with an advance stay "Unpaid" when the advance covers only part of the claim amount. (https://github.com/frappe/hrms/pull/4590)
* Adds a one-day buffer before **Shift Assignment** records are marked inactive, so assignments that end today stay active until the following day. (https://github.com/frappe/hrms/pull/4618)
* Attendance requests for past dates now fill in the assigned _Shift_ even if the related **Shift Assignment** is inactive. (https://github.com/frappe/hrms/pull/4620)

**Authors**: @deepeshgarg007, @iamkhanraheel, @krishna-254
**Reviewers**: @ruchamahabal, @deepeshgarg007

<details>
<summary>AI content</summary>

 For these release notes, we used an LLM (OpenAI gpt-5.4-mini) to review and summarise the code changes, along with the associated issue and PR descriptions. It may contain typical errors and inaccuracies. You can read the prompt [here](https://github.com/barredterra/pretty_release_notes). 

Changes with the following labels were excluded:
- skip-release-notes

Changes with the following types were excluded:
- style
 - docs
 - refactor
 - test
 - build
 - ci
 - chore

</details>