fix: value of depreciable assets not updating after manual depr entry [v14] (backport #35010) #35029
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
… [v14] (#35010) * fix: update value of asset with calc_depr on after manual depr entry * fix: value of asset with calc_depr on after manual depr entry not reflecting in asset_depr_and_bal report * chore: add validation for depr journal entry * test: manual_depr_for_depreciable_asset and manual_depr_w_incorrect_jv_voucher_type * chore: unlink depreciable asset from manual depr entry (cherry picked from commit 3c75e55) # Conflicts: # erpnext/accounts/doctype/journal_entry/journal_entry.js
mergify
bot
requested review from
anandbaburajan,
deepeshgarg007 and
ruthra-kumar
as code owners
anandbaburajan
approved these changes
Apr 25, 2023
frappe-pr-bot
pushed a commit
that referenced
this pull request
Apr 25, 2023
## [13.49.14](v13.49.13...v13.49.14) (2023-04-25) ### Bug Fixes * `PermissionError` in Work Order ([5680045](5680045)) * Advance payment against payment terms ([#34872](#34872)) ([d215a85](d215a85)) * internal Purchase Receipt GL Entries ([b73422e](b73422e)) * Payment entry with TDS in bank reco statement ([#34961](#34961)) ([5f28b1d](5f28b1d)) * Payment Request flow fixes from Order to Payment Entry ([#33350](#33350)) ([d5a80b5](d5a80b5)) * SLA permissions ([#34981](#34981)) ([c1187be](c1187be)) * **test:** `test_backdated_stock_reco_cancellation_future_negative_stock` ([d010b04](d010b04)) * Unable to allocate advance against invoice ([#35007](#35007)) ([61a3121](61a3121)) * use filter_by_finance_book instead of only_depreciable_assets in fixed asset register (backport [#35031](#35031)) ([#35036](#35036)) ([be2095a](be2095a)) * validation for internal transfer entry ([91b5a33](91b5a33)) * value of depreciable assets not updating after manual depr entry [v14] (backport [#35010](#35010)) ([#35029](#35029)) ([9087ac0](9087ac0)) * wrong qty of remaining work orders to be created when using "Create" > "Work Order" ([#34726](#34726)) ([189b020](189b020))
|
🎉 This PR is included in version 13.49.14 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automatic backport of pull request #35010 done by Mergify.
Cherry-pick of 3c75e55 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com