The Bangladesh payroll configuration now uses the correct name for a yearly minimum tax parameter instead of incorrectly calling it a maximum tax. This helps keep payroll tax rules clear and reduces the chance of confusion when maintaining salary calculations.

The rule parameter l10n_bd_yearly_maximum_tax should really be called l10n_bd_yearly_minimum_tax.

Knowledge article filtering now correctly includes items whose internal permission is either set to 'none' or left blank. This helps ensure users see the expected articles and avoids missing content due to inconsistent permission handling.

The operator "=?" does not handle null values correctly and will be fixed in the future. However, the intention of the filtered domain is to return articles that have their permission set to 'none' or not set.

This update corrects how several business apps use shared Odoo utilities, preventing breakages caused by outdated internal import paths. There is no intended change to day-to-day workflows, but it improves reliability across accounting, payroll, localization, manufacturing, subscriptions, social, and worksheet features.

This update corrects a spreadsheet edition test so it matches the expected behavior for comment threads. It reduces false test failures, helping keep development and release checks more reliable without changing user-facing functionality.

The test `Selecting the cell with a unsolved thread does not open the thread popover` was sometimes failing.

After investigation, it seems like the test is plain wrong. The thread popover should open for unsolded threads, it's for resolved threads that it should not open. Running the test in debug make it clear that the threads popoved is opened. I'm not sure how the test was somehow passing before.

Task: [4042515](https://www.odoo.com/web#id=4042515&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)

This fix corrects how the Appointment Details page displays in the Calendar module. Previously, the appointment resource section would appear even when no resources were assigned to an appointment. Now, the resource details section only displays when resources are actually configured, providing a cleaner and more accurate user experience.

Steps to reproduce:
1. Create an event with an appointment-type set.
2. In the Calendar module, open the event you created for the appointment.
3. Navigate to the 'Appointment Details' page.

Before This Commit:
The 'Appointment Details' page is displayed even if no resources have been set.

After This Commit:
Appointment resource records will only be shown if resources are set.

Task:3918574