Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: configurable depreciation calculation via accounts settings (backport #42276) #42301

Merged
merged 1 commit into from
Jul 12, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jul 12, 2024

Introduced a checkbox in account settings to enable calculation of daily depreciation based on the total number of days in the depreciation period, including leap years.

  • Default method divides the asset amount on a per-day basis and then by the days in the year.

  • Enabling the checkbox changes the calculation to divide the asset amount by the total days in the depreciation period.

no-docs


This is an automatic backport of pull request #42276 done by Mergify.

…2276)

* feat: configurable depreciation calculation via accounts settings

* refactor: code optimization

* style: changes in description and label

(cherry picked from commit b04da63)
@mergify mergify bot requested a review from deepeshgarg007 as a code owner July 12, 2024 08:57
@mergify mergify bot requested a review from ruthra-kumar as a code owner July 12, 2024 08:57
@khushi8112 khushi8112 merged commit ad228d8 into version-15-hotfix Jul 12, 2024
12 checks passed
@khushi8112 khushi8112 deleted the mergify/bp/version-15-hotfix/pr-42276 branch July 12, 2024 13:02
@frappe-pr-bot
Copy link
Collaborator

🎉 This issue has been resolved in version 15.30.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants