Wednesday, October 1, 2025
35 changes · 19.0
Resolved issues and error corrections
The customer order portal no longer shows the same manufacturing date twice for made-to-order manufactured products. This keeps the order details clearer for customers and avoids confusion when they review purchases online.
Original PR description
**Steps to reproduce:** 1.Install `website_sale` and `sale_mrp`. 2.In settings, enable `multi-route` and `unarchive` the Replenish MTO route. 3.Create a product with routes -> `Replenish MTO` and…
**Steps to reproduce:** 1.Install `website_sale` and `sale_mrp`. 2.In settings, enable `multi-route` and `unarchive` the Replenish MTO route. 3.Create a product with routes -> `Replenish MTO` and `Manufacturing` then publish it on the website. 4.Buy the product from the website and make the payment. 5.Go to My Account → Your Orders → Open your sale order. 6.In the Manufacturing section, the date appears twice. **Issue-** <img width="604" height="186" alt="image" src="https://github.com/user-attachments/assets/e4164564-8555-4005-8282-20e6f5de7e55" /> - Date found twice in Portal View of sale order **Cause-** https://github.com/odoo/odoo/blob/097c04156517bd97a2789bde22ffd0c69c0bf6bf/addons/sale_mrp/views/sale_portal_templates.xml#L18-L27 - Here using same field two time one it with condition and other is without condition so in some case when condition satisfied then same field are coming twice **Solution-** - Remove Conditional field because no meaning of using same field inside and outside of the condition **opw - 5096009** Forward-Port-Of: odoo/odoo#227997
The cohort reporting view now disables the download option when there is no data to export. This prevents users from running into an error in reports such as Helpdesk Ticket Analysis when the database has no matching records.
Original PR description
Currently, an error occurs when user tries to export data on cohort view with no data. Steps to replicate: - Install `helpdesk` (without demo data). - Go to `Helpdesk > reporting > Ticket Analysis` and go to cohort view. - Click download and error will occur. - If error doesnt occur, click on `Measure > Count`, and click Download again. Error: `IndexError: list index out of range` Cause: - The export button remained enabled even when no data available, this caused the export to be called without any data that caused the `Indexerror` at [1]. Solution: - Disabled the export button when no data in cohort view. [1]: https://github.com/odoo/enterprise/blob/475a802aa3e748a905be83c0f6408f8c20f03905/web_cohort/controllers/main.py#L30 sentry-6831823426 Forward-Port-Of: odoo/enterprise#93050
This fixes a crash that could happen when saving a view or editing a report in Web Studio if the view contained an attribute entry without a name. The system now skips those incomplete entries safely, helping users save views without encountering an unexpected error.
Original PR description
Currently, an error occurs when user tries to save a view with an attribute node without name. **Steps to replicate:** - Initialize a DB and open Views. - Create a new view and fill in random values…
Currently, an error occurs when user tries to save a view with an attribute node without name.
**Steps to replicate:**
- Initialize a DB and open Views.
- Create a new view and fill in random values for name and give a View Type.
- In the Architecture give value as `<attribute></attribute>`.
- Save and you will get the error.
(Same error can also be produced with Web Studio report editor.)
**Error:**
`AttributeError: 'NoneType' object has no attribute 'endswith'`
**Cause:**
- The error occurred because we received **key** as `None` at [1], as it was called from an attribute node with no name [2].
- In `saas-18.2`, we only checked if `node.get('name') not in TRANSLATED_ATTRS`. Since `node.get('name')` was `None` and `None` was not included in the `TRANSLATED_ATTRS` list, no error occurred.
**Solution:**
- Added a conditional check, so that attributes with no name skip the function call.
[1]: https://github.com/odoo/odoo/blob/f254da2253e7ce9426e51112b513fa9e6a474ce4/odoo/tools/translate.py#L83
[2]: https://github.com/odoo/odoo/blob/f254da2253e7ce9426e51112b513fa9e6a474ce4/odoo/tools/translate.py#L190
[3]: https://github.com/odoo/odoo/blob/0b700ec3c08ecd9c6f1597f9d10f6c1eee06bcee/odoo/tools/translate.py#L255
sentry-6877030439
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#227221Opening a Knowledge article activity now shows only the relevant articles with assigned activities instead of the full article list. This helps users quickly find the article that needs their attention and avoids confusion in the activities menu.
Original PR description
Currently, when the user tries to open any activity of the knowledge article, it opens all articles instead of the one which has an activity assigned to them. **Steps to reproduce this issue:** 1) Install the Knowledge module 2) Set up an activity for yourself on a Knowledge article 3) Open the activities from Activities (top left corner) **Issue:** You will end up in the all articles list, with no filters applied. **Cause:** When the user clicks on the activities, a default search filter is added in the context, which is then applied on the view. But in the knowledge article, we don't have any search filters for the activities. Therefore, it renders all knowledge article records. **Solution:** Add search filters for the knowledge articles. opw-4997201 Forward-Port-Of: odoo/enterprise#93609
The website shop now handles invalid category values in product page URLs more gracefully. Instead of causing a server error, it returns a clearer validation message, improving stability when links are mistyped or tampered with.
Original PR description
Currently, an error occurs when the `category` is received as a `string` and the code tries to evaluate `int(category)`. **Steps to reproduce:** - Install the `website_sale` module. - Open a product page in the website with an `invalid category` parameter, for example: `http://localhost:8069/shop/warranty-39?category=1;` **Error:** `ValueError: invalid literal for int() with base 10: '1;'` **Root Cause:** At [1], the code directly calls `int(category)` without validating the input. When the parameter contains `non-numeric` characters, Python raises an `error`. **Fix:** This commit ensures raising a `ValidationError`, improving the `error message` clarity, when users manually input `invalid or tampered` category values in the `URL`. [1]: https://github.com/odoo/odoo/blob/d32f98dd199f80d2b0031bd52a6ff74411c3e7e0/addons/website_sale/controllers/main.py#L1827 sentry-6658317828 Forward-Port-Of: odoo/odoo#226207
The POS now correctly recognizes when a self-order has already been sent for preparation, so the Order button is no longer incorrectly highlighted after loading it. This reduces confusion for staff and helps avoid mistakenly thinking an already-submitted order still needs action.
Original PR description
In the POS UI, the "Order" button was wrongly highlighted when loading a self-order, even though it had already been sent Steps to reproduce: - Create an order using self-order mobile (or kiosk). - Open the related POS terminal. - Load the self-order from the ticket screen. - Notice the "Order" button remains highlighted. Fix: - Ensure the last order changes updated when loading self-order in pos Task: 5005161 Forward-Port-Of: odoo/odoo#229246 Forward-Port-Of: odoo/odoo#223560
Nuvei payments could fail when a customer's first or last name was longer than Nuvei allows. The checkout process now shortens those names automatically so affected sales orders can be paid without error.
Original PR description
Steps: - Install sales and payment Nuvei. - Set up payment Nuvei. - Set customer long name and last name. - Try to pay that SO with Nuvei. Issue: - Error. Cause: - Nuvei only accept 30 character for first_name and 40 for last name Fix: - Truncate first and last name to only take required character. opw-5083827 Forward-Port-Of: odoo/odoo#227191
This update fixes an unreliable automated test for the HTML editor by ensuring the editor toolbar is fully ready before the test continues. It helps prevent false test failures, improving confidence in release validation without changing user-facing behavior.
Original PR description
The editor toolbar is affected by [1] and therefore needs to be properly awaited for. This test was missed by [2], probably because it did not explicitly waited for the toolbar itself. runbot-231692 [1]: https://github.com/odoo/odoo/pull/211426/commits/54da715df84789f9a1acc0cfc91be41dcdbab140 [2]: https://github.com/odoo/odoo/pull/213090 Forward-Port-Of: odoo/odoo#227989
The HTML editor now handles tables pasted from tools like ChatGPT when their first row is formatted as a table header. This prevents an error when users delete rows, making pasted table editing more reliable.
Original PR description
**Current behavior before PR:** Steps to reproduce: - Copy a table from chatGPT's response containing first row wrapped in `<thead>`. - Paste it in editor. - Select last row. - Pressing backspace leads to traceback. This issue happens because the copied table is pasted with first row wrapped in a thead element. Due to this, rows are wrongly calculated leading to traceback in removeRow method. **Desired behavior after PR is merged:** - This commit ensures that if a table has first row wrapped inside a `thead`, the row is moved from `thead` to the start of `tbody` ensuring that rows are calculated correctly. task-5048339 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#226990 Forward-Port-Of: odoo/odoo#224784
The project dashboard now prevents users from editing milestone quantity percentages when no sales order line is linked. This avoids confusing failed edits and makes milestone billing data behave consistently with the underlying sales order setup.
Original PR description
**Steps to Reproduce:** - Install sale_project. - Go to the project dashboard. - Click on Edit milestones. **Isuue:** When a sales order line exists, the quantity percentage can be updated. When no sales order line exists, the quantity percentage cannot be updated. **Fix:** Make the field readonly when no sales order line is linked. task-5068312 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#227922
The website builder tooltip for the footer visibility option has been corrected so it no longer describes the opposite behavior. This helps users understand whether the footer will be shown or hidden when adjusting page visibility settings.
Original PR description
A tooltip message was added to the option for the visibility of the footer in e0474c19d212d9c19fd1c3bbc9546b4258770018. The message indicates the opposite of the effect. This commit changes the message to match the behavior of the checkbox. Steps to reproduce: - Open website builder - Click on footer - Hover "Page Visibility" - Bug: the message "Enable to hide...", but enabling actually shows task-4991435
This fixes an issue in the HTML editor where images added from an empty formatted line could disappear after the user clicked elsewhere. The change preserves the inserted image during editor cleanup, helping users avoid lost content while composing pages or messages.
Original PR description
Problem: When an image is added inside a `data-oe-zws-empty-inline`, it is removed along with its parent during normalization. Solution: During normalization, replace `data-oe-zws-empty-inline` with the image inside instead of removing both. Steps to reproduce: - Press CTRL+B in an empty line - Press Enter - Click on "Insert image, ..." from the placeholder - Choose an image - Click in the previous paragraph - The image disappears without this fix task-5051343 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#228620 Forward-Port-Of: odoo/odoo#224922
The website and HTML editing tools now use Odoo’s slimmer close icon for a cleaner, more consistent interface. Some button layouts and dropdown behavior were also corrected so controls align better and remain usable on smaller screens.
Original PR description
This commit replaces occurrences of `fa-times` in the html builder and editor with our own `oi-close` icon, which is less bulky and more elegant. It also corrects button structures where icon classes were placed directly on the `button`, ensuring they are applied to a child `<i>` element as intended. It also ensures `.o-hb-selectMany2X-wrapper` has `min-w-0` so the dropdown is truncated properly without pushing the remove button out of the screen. task-5090805 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Swedish bankgiro accounts are now correctly marked as BGNR instead of BBAN in payment XML files. This helps ensure Swedish credit transfer files use the expected account type and are accepted by banking systems.
Original PR description
Issue: The only possible value for the bank account type is "BBAN". For a 'bankgiro' account it should be "BGNR". Solution: Input "BGNR" in the XML if the bank account type is 'bankgiro'. opw-5063368 Forward-Port-Of: odoo/enterprise#95467
The Swedish SIE4 export now uses the character encoding required by the official SIE specification. This helps ensure exported accounting files handle Swedish characters correctly and are accepted by systems expecting the standard format.
Original PR description
The SIE4 specification (page 8, section 5.8) requires the file character set to be IBM PC 8-bit extended ASCII (Codepage 437). Previously, 'ISO-8859-1' was used, which does not comply with the standard and may cause issues with Swedish characters. This commit updates the SIE4 export to use codepage 437, ensuring full compliance with the specification. Specification can be found here: https://sie.se/wp-content/uploads/2020/05/SIE_filformat_ver_4B_080930.pdf
The field service onboarding guide now works correctly even when a project already contains task templates. This helps new users complete setup without being blocked by pre-existing configuration.
Original PR description
This commit's purpose is to allow the fsm onboarding tour to work even if there are existing task template within the fsm project. note : This commit has to be edited in the 19.0 forward port, since its IsActive selector was updated. It should be ["body:has(.o-kanban-button-new.o-dropdown-caret"] instead. task-5088820 Forward-Port-Of: odoo/enterprise#94904
This fixes an issue where engineering change orders rounded very small bill of materials quantity updates to two decimal places instead of using the product unit precision. Businesses using precise measurements can now record and review small component quantity changes correctly.
Original PR description
Steps to reproduce the bug:
- Go to Decimal Accuracy → Product Unit of Measure → set digits to 4
- Go to Units of Measure Categories → select a unit → set rounding to 0.0001
- Create a storable product “P1” with a BoM:
- Component C1: 1.0000 unit
- Create an ECO for the BoM with type BoM update
- Start the revision
- Go to V2
Problem:
You cannot update the quantity of C1 to 1.0003 (for example) because the system uses the default 2 digits instead of the UoM digits.
opw-5082488
Forward-Port-Of: odoo/enterprise#95470
Forward-Port-Of: odoo/enterprise#95180This update ensures that errors in automated tests are correctly detected instead of being overlooked. It improves internal quality checks for the website helpdesk live chat area, helping teams catch issues earlier before they affect users.
Original PR description
This commit follows a community fix that restores proper error handling within and outside of unit tests. As such, it fixes tests reporting errors that were previously not picked up. Community PR: https://github.com/odoo/odoo/pull/228836 Forward-Port-Of: odoo/enterprise#95797
This fixes an issue in Indian payroll where the system could incorrectly check whether total allowances stay below the wage amount. The correction helps payroll teams avoid incorrect validation errors and improves confidence in salary rule checks.
Animated text and other elements in slide-over footers now trigger when visitors scroll to them. This prevents footer content from staying hidden and helps website pages display as intended.
Original PR description
Before this commit, using animation on text within the footer elements would not work if the footer was set on "slide over". The formula used to compute when to start the animation was incorrect. This commit fixes the formula. Steps to reproduce: - Set the Footer slideout to "Slide Over" - Set the Animation of an element to "On Appearance" - Save (when scrolling down, the animated element stay hidden) Forward-Port-Of: odoo/odoo#226562
This fixes an issue where entering a font size in the website editor could automatically change the value by adding unexpected decimals. Users can now set sizes such as 19px without seeing them altered, while the displayed value remains clean and readable.
Original PR description
__Current behavior before commit:__ When typing an integer value in the font size input, some decimals are added automatically because the value entered in `px` is first converted to `rem` then it's converted back to `px` but some precision is lost in `convertNumericToUnit` because `toFixed(3)` is called on the result. __Description of the fix:__ `toFixed` is removed from `convertNumericToUnit` to avoid any loss of precision on the value saved. However it's now used in `formatRawValue` so that the value displayed to the user is stays clean. This way we keep the behavior intended by [this PR]. __Steps to reproduce the issue on runbot:__ 1. Open the website builder. 2. Go to the *Theme* tab. 3. In Paragraph section, set the Font Size to 19px. => It gets changed to 19.008px automatically. [this PR]: https://github.com/odoo/odoo/pull/221754 Forward-Port-Of: odoo/odoo#224633
This fixes a purchase stock test so it consistently uses a consumable product, regardless of defaults introduced by localization modules. It prevents false test failures when Kenyan localization is installed, improving reliability without changing user-facing purchase or inventory behavior.
Original PR description
The test `test_receive_negative_quantity` is failing when run with the `l10n_ke` module installed. The failure occurs during the validation of the picking created from a negative-quantity purchase…
The test `test_receive_negative_quantity` is failing when run with the `l10n_ke` module installed. The failure occurs during the validation of the picking created from a negative-quantity purchase order. The test assumes the product is of type `consu`, which bypasses stock reservation. However, the following [XML default](https://github.com/odoo/enterprise/blob/17.0/l10n_ke_edi_oscu_stock/data/ir_default.xml#L5) in l10n_ke forces the product type to `product` (stockable), triggering reservation logic. Since the ordered quantity is negative, no reservation occurs, and the `_sanity_check()` fails with: `You cannot validate a transfer if no quantities are reserved.` We fix this by explicitly setting a product with the type `consu` in the test. This ensures that reservation is skipped regardless of which modules are installed or what defaults they apply. runbot:[108147](https://runbot.odoo.com/odoo/error/108147) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#228583 Forward-Port-Of: odoo/odoo#221042
The chatter follower menu now stays open after removing a follower, making it easier to remove several followers in one session. The subscription edit action now closes the menu consistently, reducing confusion for users managing followers.
Original PR description
**Description of the issue this PR addresses:** ------------------------------------------------ Removing multiple followers from the chatter is cumbersome because the followers dropdown closes immediately after each removal. Additionally, clicking 'Edit Subscription' next to 'Unfollow' did not close the dropdown, which was inconsistent with expected behavior. **Current behavior before PR:** --------------------------------- - Removing a follower from the chatter closes the followers dropdown immediately - Clicking 'Edit Subscription' next to 'Unfollow' leaves the dropdown open **Desired behavior after PR is merged:** ----------------------------------------- - The followers dropdown remains open after removing a follower, allowing multiple removals without interruption - Clicking 'Edit Subscription' next to 'Unfollow' closes the dropdown as expected **Task:** 4943867 Forward-Port-Of: odoo/odoo#222154
This update adjusts an internal sales test so it uses the configured sales confirmation email template instead of assuming a fixed one. It helps ensure payment and order confirmation behavior is tested accurately when businesses customize their email settings.
Original PR description
The email template for the sale confirmation can be changed through the config parameters so it's better to read it directly from there instead of having it hard-coded. This now correctly tests the function it's testing. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#226240
Creating a salesperson from a converted lead no longer copies unrelated lead phone details into the new salesperson record. This prevents incorrect contact information from being saved and reduces manual cleanup for sales teams.
Original PR description
To reproduce: ============= 1- add a lead 2- add a phone and a mobile number 3- convert it to opportunity 4- create salesperson from that view 5- salesperson contains lead number Problem: ========= Before this fix, creating a Salesperson inherited the global context, which included unrelated values as active_model was set to crm.lead. This led to incorrect default values being applied. https://github.com/odoo/odoo/blob/d155edfd729ab9b53f38939fe24b6d1e7b578083/addons/web/models/models.py#L872C13-L872C21 The default values contained the lead phone and lead number and was applied in the creation of salesperson. Solution: ========== Since we have some synchronization of some fields (email, phone) that is automatically done normally, it's reasonable to remove the code and see what it gives. opw-4871069 Forward-Port-Of: odoo/odoo#229171 Forward-Port-Of: odoo/odoo#217545
After DIOT 2025 rework in 4e6bee49e98b055e5aebe89fb19ab6317003b682 the report is missing some es translations Steps to reproduce: - With an MX Company and Spanish es_419 language set - Open Accounting > Reporting > Tax Report - Choose report Diot MX opw-5016650 Forward-Port-Of: odoo/odoo#229132 Forward-Port-Of: odoo/odoo#229085
Original PR description
After DIOT 2025 rework in 4e6bee49e98b055e5aebe89fb19ab6317003b682 the report is missing some es translations Steps to reproduce: - With an MX Company and Spanish es_419 language set - Open Accounting > Reporting > Tax Report - Choose report Diot MX opw-5016650 Forward-Port-Of: odoo/odoo#229132 Forward-Port-Of: odoo/odoo#229085
Website editors are now protected from errors when entering an invalid progress bar value. The progress bar input also displays percentages more cleanly, avoiding confusing duplicate percent signs.
Original PR description
Before this commit, putting an invalid input in the progressbar value would lead to a traceback. Moreover, the input could display "0%%" (one being in the input, the other being the displayed unit). This commit solves this issue by defining a saveUnit for the input and using the defaultValue when an input is invalid. Forward-Port-Of: odoo/odoo#227249
This update adjusts how Odoo's web test framework classifies and reports errors and warnings, so test issues are neither hidden nor treated as more severe than intended. It improves reliability of automated testing and helps developers catch real problems without unnecessary test interruptions.
Original PR description
This commit associates separate "issue levels" to the test runner's internal logger. These affect the logging and reporting of issues, i.e. errors and warnings: - suppressed (by 'test.todo'): issues are traced in the console but not reported in test results; - trace (default in test runs): issues are traced in the console and reported in test results; - global: issues are warned/errored in the console with "HOOT" prefix (i.e. won't interrupt the test run); - critical (default outside of test runs): issues are warned/errored in the console without "HOOT" prefix, thus interrupting the whole test run. This fix should hopefully solve errors that were too quiet before test run, or too "important" during the run. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#228836 Forward-Port-Of: odoo/odoo#228674
This fixes an issue where selecting only a space in the HTML editor caused the color picker to close unexpectedly. Users can now apply font color consistently, including to spaces between words, improving text formatting reliability.
Original PR description
Problem: When trying to apply font color on a space, the color picker suddenly closes. Solution: Allow adding styles on space characters. Steps to reproduce: 1. Add text "A B". 2. Select the space only. 3. Try to change font color. 4. Observe that the color picker suddenly dismisses. task-5111480 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
OSS reports can now open correctly when a fiscal position uses a country group, such as Mainland Spain VAT, instead of a directly assigned country. This helps businesses handle regional VAT setups like mainland Spain versus the Canary Islands without report access errors.
Original PR description
To be able to deal with Spain with Canary Islands and mainland, we have a country group that is Mainland Spain VAT, with Spain minus several states (Canary basically). People want to be able to use it for OSS. But currently, if you have an entry with a tax with a fp with this country group (and no country), you can't open your OSS Report. So take the countries of the country group if there is none in the fiscal position. Forward-Port-Of: odoo/enterprise#95795
This fixes the hover animation for the website categories showcase snippet, which had stopped responding when visitors moved their mouse over it. Restoring this visual feedback helps storefront pages feel interactive and polished again.
Original PR description
Since commit [1], the hover effect on the "categories showcase" snippet is no longer working. Nothing happens when it’s hovered with the mouse. This is caused by a missing comma in the CSS rule that handles the effect. [1]: https://github.com/odoo/odoo/commit/dea725a4e45b584689813bdbf09e51070a3c55d3
The website live chat no longer shows the chatbot's instant messaging status, preventing unnecessary presence details from appearing to visitors. The status remains available in other areas where it is still useful for internal or standard chat use.
Original PR description
**Description of the issue this PR addresses:** Chatbot's IM Status shouldn't be visible on the website **Current behavior before PR:** Before this PR, the chatbot's IM status was shown on the website during live chat. **Desired behavior after PR is merged:** This PR hides the IM status for chatbot when embedded in the website, while keeping it visible elsewhere. Backport of this: https://github.com/odoo/odoo/pull/220966 task-[4930194](https://www.odoo.com/odoo/project/1519/tasks/4930194) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Editing a message that includes a new mention no longer creates an extra duplicate link next to it. This keeps message content clean and avoids confusing recipients with repeated mention links.
Original PR description
Before PR #223808, `prettifyMessageContent()` was called when posting or editing a message. With the mentioned PR, prettifying happens while typing. So prettifying the content again when editing, causes creating an extra `a` tag in the message content. The part related to posting a message is already taken care of in that PR. This PR removes the prettifying when editing a message. task-5123493
This fixes an issue where delivery provider settings accidentally changed the default Apps list display, hiding useful module details like name, author, website, and version. The delivery-specific views now stay in their intended place, keeping the general Apps screen consistent for users.
Original PR description
This commit* introduced a new views for delivery provider modules, list and kanban. The new views are meant to target only this particular delivery provider view. But, since the priority of the list view is not defined, the default order (with the name) makes it used before the classic list view for modules in Apps. This has the effect to hide a few fields (name, author, website and version). This commit adds a priority to this list view such that it is not used by default to list ir.module.module records. A priority is also defined on the kanban view to avoid this issue to affect kanban view if anyone ever changes its name. *: https://github.com/odoo/odoo/commit/b798db1b2faa0e437baa4fc524821ec324136aff
Employee resume entries now skip the job title line when no job title is set. This prevents the word "False" from appearing in resumes, making employee profiles look cleaner and more professional.
Original PR description
If an employee doesn't have a job title set on his profile, the resume shows "False" line. The logic has been adjusted to skip the line in case the employee doesn't have a job title