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-02-27] Room - Yes and No button show in whisper message different shape #82867
👋 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.
Classification: Frontend bug Causing PR: Unable to determine with high confidence Related Issues: None identified
Recommendation: NEEDS INVESTIGATION
Unable to identify the specific causing PR from the current staging deploy checklist. The issue involves Yes/No buttons showing different shapes in a whisper message when typing "#hey" in a workspace chat. This is clearly a UI rendering issue affecting button styling/border-radius.
Next Steps:
Need design/frontend engineer to investigate DecisionModal component and Button component styling
Check for any recent changes to button border-radius, padding, or shape properties
Investigate if there are conditional styles being applied differently to the two buttons
Labels: KEEP both DeployBlockerCash and DeployBlocker labels until the causing PR is identified (this is staging-only and not reproducible on production, so we should be conservative about label removal)
Detailed Analysis
Evidence
Issue is reproducible on staging (v9.3.22-0) but NOT on production
Symptoms: Yes and No buttons in a whisper message display different border shapes
Trigger: Typing "#hey" in a workspace chat
Platform: MacOS Chrome/Safari
Component likely: DecisionModal using Button components
No obvious button or styling PRs found in the recent deploy
Root Cause
Unable to determine without further investigation. The bug appears to be a styling inconsistency where two Button components rendered in the same modal have different border-radius values applied.
Why Investigation Failed
The causing PR may be:
A PR that indirectly affected button styles through theme or StyleUtils changes
A PR with subtle conditional logic affecting button rendering
Part of a larger refactoring that wasnt obvious from PR titles/files
changed the title [-]Room - Yes and No button show in whisper message different shape[/-][+][Due for payment 2026-02-27] Room - Yes and No button show in whisper message different shape[/+]on Feb 20, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.23-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@Julesssss@joekaufmanexpensify 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
melvin-bot commentedon Feb 18, 2026
Triggered auto assignment to @joekaufmanexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Feb 18, 2026
Triggered auto assignment to @srikarparsi (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Feb 18, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Feb 18, 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:
OSBotify commentedon Feb 18, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: Unable to determine with high confidence
Related Issues: None identified
Recommendation: NEEDS INVESTIGATION
Unable to identify the specific causing PR from the current staging deploy checklist. The issue involves Yes/No buttons showing different shapes in a whisper message when typing "#hey" in a workspace chat. This is clearly a UI rendering issue affecting button styling/border-radius.
Next Steps:
Labels: KEEP both DeployBlockerCash and DeployBlocker labels until the causing PR is identified (this is staging-only and not reproducible on production, so we should be conservative about label removal)
Detailed Analysis
Evidence
Investigation Attempts
Root Cause
Unable to determine without further investigation. The bug appears to be a styling inconsistency where two Button components rendered in the same modal have different border-radius values applied.
Why Investigation Failed
The causing PR may be:
17 remaining items
Julesssss commentedon Feb 19, 2026
MelvinBot commentedon Feb 19, 2026
[-]Room - Yes and No button show in whisper message different shape[/-][+][Due for payment 2026-02-27] Room - Yes and No button show in whisper message different shape[/+]melvin-bot commentedon Feb 20, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Feb 20, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.23-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-02-27. 🎊
melvin-bot commentedon Feb 20, 2026
@Julesssss @joekaufmanexpensify 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]
abzokhattab commentedon Apr 7, 2026
Can we open this issue for payment ... i worked on the PR review #83048nvm i just found out that its a deployment blocker and the main issue was paid