You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-06-02] Device management - No period after Learn more link #91479
Version Number: 9.3.80-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#91323 Email or phone of affected tester (no customers):isjdosdjoijosdjosnj@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.2 / Chrome App Component: User Settings
Action Performed:
Go to staging.new.expensify.com
Go to Account > Copilot.
→ There is a period after Learn more link.
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
The Device Management page description string in en.ts:2294 ends with </a> but has no trailing period. The Copilot page avoids this because it renders the period as a separate JSX node after its <TextLink>, but the Device Management page uses RenderHTML with the translation string directly, so the period must be in the string itself.
What changes do you think we should make in order to solve the problem?
Add a period (.) after the closing </a> tag in the deviceManagementPage.description string in both en.ts:2294 and es.ts:2108.
Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.
changed the title [-]Device management - No period after Learn more link[/-][+][Due for payment 2026-06-02] Device management - No period after Learn more link[/+]on May 26, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.82-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@arosiclair The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
applause-bot commentedon May 22, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/51678879314b3b784ef6a7a98c15f053d63dc89a442ee13ce59005a3d6d95b48
melvin-bot commentedon May 22, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #91323
melvin-bot commentedon May 22, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 22, 2026
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
MelvinBot commentedon May 22, 2026
Proposal
What is the root cause of that problem?
The Device Management page description string in
en.ts:2294ends with</a>but has no trailing period. The Copilot page avoids this because it renders the period as a separate JSX node after its<TextLink>, but the Device Management page usesRenderHTMLwith the translation string directly, so the period must be in the string itself.What changes do you think we should make in order to solve the problem?
Add a period (
.) after the closing</a>tag in thedeviceManagementPage.descriptionstring in bothen.ts:2294andes.ts:2108.Next Steps for Contributor+ team: Reply with
@MelvinBot implement thisto create a draft PR,@MelvinBot <your feedback>to refine this analysis, or explain why you are rejecting Melvin's proposal.mountiny commentedon May 24, 2026
We dont have to block on this
[-]Device management - No period after Learn more link[/-][+][Due for payment 2026-06-02] Device management - No period after Learn more link[/+]melvin-bot commentedon May 26, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon May 26, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.82-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-06-02. 🎊
melvin-bot commentedon May 26, 2026
@arosiclair The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]