Skip to content

Insights - "Top Tags" chart is displayed in "Bar" view instead of "Pie" #107216

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.5.41-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: #105096
Email or phone of affected tester (no customers): ibellicotest+3215@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Other

Action Performed:

Prerequisite: User is owner of a workspace with "Tags" enabled and at least 6 different tags created.
Prerequisite 2: Have more than five tagged expenses created with different tag values.

  1. Open the staging.new.expensify.com website.
  2. Navigate to "Insights"
  3. Scroll down to "Top Tags" chart.
  4. Note that "Top Tags" chart is displayed in "Bar" view instead of being visible as a donut (Pie view)

Expected Result:

"Top Tags" chart should be displayed in "Pie" view (being visible as a donut) with all the used tags ranked.

Actual Result:

Tags are ranked in "Bar" view in "Top Tags" chart instead of being visible in "Pie" view.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7317334_1794976767839.Top_Tags.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7317334

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 18, 2026
  2. applause-bot commented on Nov 18, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/3f72684672ad6fb9b98c1639a9181ce6eae8977912060154cdfd863b3ec07414

  3. expensify-chore-bot commented on Nov 18, 2026

    @expensify-chore-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #105096

  4. expensify-chore-bot commented on Nov 18, 2026

    @expensify-chore-bot

    @aldo-expensify @daledah you have been assigned to this deploy blocker because you reviewed the offending PR: #105096

  5. expensify-chore-bot commented on Nov 18, 2026

    @expensify-chore-bot

    @luacmartins you have been assigned to this deploy blocker because you authored the offending PR: #105096

  6. expensify-chore-bot commented on Nov 18, 2026

    @expensify-chore-bot

    💬 A slack conversation has been started in #expensify-open-source

  7. github-actions commented on Nov 18, 2026

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  8. MelvinBot commented on Nov 18, 2026

    @MelvinBot
    Contributor

    Deploy-blocker investigation

    Conclusion: likely expected behavior, not yet a confirmed defect. Do not revert based on the current report.

    Add Top tags to the Insights dashboard introduced this feature and is included in the affected staging release. Its specification explicitly calls for:

    • A donut with multiple tag results and no comparison.
    • Bars for comparisons or a single result.
    • Only the top five tags, not every used tag.
    Code evidence

    The report does not identify the comparison setting or the number of tag groups remaining after filtering. Having six tags globally does not establish either condition.

    Required confirmation: On web, explicitly select Compare → None, with at least two tagged groups inside the selected dates, workspace, and tag level. That should display a donut; Previous period and Average should display bars.

    If those expectations pass, this should be treated as expected behavior rather than a blocker. If the no-comparison case still displays bars, retain the blocker and investigate that specific state.

    Confidence: High in the intended behavior; unconfirmed explanation for the tester’s session. Investigation was static—no live browser verification was performed. No code or labels changed.


    view run

  9. mhawryluk commented on Nov 18, 2026

    @mhawryluk
    Member

    that's expected with compare:previous-period

  10. luacmartins commented on Nov 18, 2026

    @luacmartins
    Contributor

    As said above, this is expected. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringHourlyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions