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

fix: incorrect depr schedule and posting dates on selling of existing assets [v13] #35404

Merged
merged 1 commit into from May 24, 2023
Merged

fix: incorrect depr schedule and posting dates on selling of existing assets [v13] #35404

merged 1 commit into from May 24, 2023

Conversation

anandbaburajan
Copy link
Contributor

Description: asset.docx (from #35159). Fixes #35159.

@anandbaburajan anandbaburajan merged commit 20d3381 into frappe:version-13-hotfix May 24, 2023
6 of 7 checks passed
frappe-pr-bot pushed a commit that referenced this pull request May 31, 2023
# [13.51.0](v13.50.6...v13.51.0) (2023-05-31)

### Bug Fixes

* force to do reposting for cancelled document ([0228933](0228933))
* **Gross Profit:** 'company' column is ambiguous in filter ([270eb1d](270eb1d))
* incorrect `POS Reserved Qty` in `Stock Projected Qty` Report ([#35437](#35437)) ([139a193](139a193))
* incorrect depr schedule and posting dates on selling of existing assets [v13] ([#35404](#35404)) ([20d3381](20d3381))
* monthly WDV depr schedule for existing assets [v13] ([#35461](#35461)) ([6f43829](6f43829))
* retention stock entry: grab conversion factor from source ([d8dd22a](d8dd22a))

### Features

* Allow ceil & floor functions in salary slip formulae ([#35475](#35475)) ([63fba9d](63fba9d))
@frappe-pr-bot
Copy link
Collaborator

🎉 This PR is included in version 13.51.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 Mar 3, 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.

None yet

2 participants