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-08-25] Clean up page header styles #98459
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.54-4 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-08-25. 🎊
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]. If no checklist is needed for this issue, you can click: [no checklist button]
@truph01 plz complete the BZ checklist and tag me in a post once you have. I think QA might want to check this monthly, as they do with other design-related test cases.
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR:
Link to the comment on the Issue:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Precondition:
Test:
Open any Account settings page (e.g. Profile, Preferences, Security, Wallet, About), any Workspace page (e.g. Overview, Members, Categories, Accounting), and any Domain page (Admins, Members, Groups, SAML).
Verify each page's header title renders at the h2 headline size (smaller than the previous larger title) and that no decorative illustration appears next to the title.
Open the Workspace editor and Domain editor and verify the LHN title (workspace/domain name) renders using the h2 headline style.
Verify the top-bar page title (e.g. Inbox/Reports) renders at the h2 size.
Activity
melvin-bot commentedon Aug 12, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @truph01 (
External)melvin-bot commentedon Aug 12, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022087596208263227293
[-]Clean up page header styles[/-][+][Due for payment 2026-08-25] Clean up page header styles[/+]melvin-bot commentedon Aug 18, 2026
@truph01
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.54-4 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-08-25. 🎊
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]. If no checklist is needed for this issue, you can click: [no checklist button]
melvin-bot commentedon Aug 21, 2026
@truph01 Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Aug 24, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Aug 24, 2026
Payment Summary
Resolving PRs:
Clean up page header styles and remove header illustrations #98461
Reviewer: @truph01 owed $250 via NewDot
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Aug 26, 2026
Payment Summary
Contributor+: @truph01 due $250 via NewDot
@truph01 plz complete the BZ checklist and tag me in a post once you have. I think QA might want to check this monthly, as they do with other design-related test cases.
truph01 commentedon Aug 28, 2026
Contributor+ Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR:
Link to the comment on the Issue:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
garrettmknight commentedon Sep 7, 2026
$250 approved for @truph01