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
[$175] Insight - "Explain" button is not displayed in each insight card using gmail account #107520
Version Number: v9.5.49-0 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from BrowserStack:#106908 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Windows 11 / Chrome App Component: Other
Action Performed:
Steps:
Create a new gmail account on Expensify
Create a workspace or set any onboarding that will create a workspace
Navigate to workspace -> enable Tags feature
Navigate to Tags -> Import Multilevel tags
Create & submit 2 expenses with different multilevel tags
Navigate to Insight tab
Expected Result:
"Explain" should be displayed in each insight card so user can tap on it
Actual Result:
Explain" button is not displayed in each insight card using gmail account
changed the title [-]Insight - "Explain" button is not displayed in each insight card using gmail account[/-][+][$175] Insight - "Explain" button is not displayed in each insight card using gmail account[/+]on Nov 20, 2026
Confirmed: Explain is part of a gated AI rollout, not standard Insights access. Creating a workspace and importing multilevel tags does not establish eligibility.
Not yet confirmed: Whether this tester lacks AI access or has another missing prerequisite. There is no verified Gmail-specific restriction.
The rollout documentation explicitly distinguishes existing Insights access from AI cards and contextual Explain access: Upcoming-AI-And-Automation.md:12–16.
These findings explain how all controls can be absent, but do not identify which prerequisite failed for the reported account. No runtime reproduction or production confirmation was obtained.
What changes do you think we should make in order to solve the problem?
Verify the QA prerequisites before proposing a code fix:
Check the affected account’s resolved insightsAI eligibility.
If enabled, verify its Concierge report is loaded and the affected charts contain data.
Retest with an explicitly enrolled account, then verify that multilevel-tag Explain requests retain the correct parent and level.
If eligibility is missing as intended, update the QA prerequisites rather than removing the gate. If eligibility is unexpectedly missing, escalate rollout/enrollment verification to an internal engineer. There is currently insufficient evidence to recommend an App code change.
What alternative solutions did you explore? (Optional)
Removing the beta gate or reverting the tag-scope PR is not supported by the evidence. Missing Concierge readiness remains an alternative explanation requiring account-state inspection.
Next Steps for Contributor+ team: To refine:@MelvinBot <your feedback> with the eligibility and Concierge-readiness results. To reject: Explain which finding is incorrect.
Activity
applause-bot commentedon Nov 20, 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/19e90ebf16e0d469aa2d2384ab9e4577038c3e1bd439ccb556e1acef2fe6e087
https://platform.applause.com/services/links/v1/external/a932d5c613f7c9258d8e399e1da52fd1007cd4a2cd173e74fe3cf1913cf11e8e
expensify-chore-bot commentedon Nov 20, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jayeshmangwani (
External)[-]Insight - "Explain" button is not displayed in each insight card using gmail account[/-][+][$175] Insight - "Explain" button is not displayed in each insight card using gmail account[/+]expensify-chore-bot commentedon Nov 20, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022123697530015506887
MelvinBot commentedon Nov 20, 2026
Proposal
What is the root cause of that problem?
Confirmed: Explain is part of a gated AI rollout, not standard Insights access. Creating a workspace and importing multilevel tags does not establish eligibility.
Not yet confirmed: Whether this tester lacks AI access or has another missing prerequisite. There is no verified Gmail-specific restriction.
Code evidence and alternative explanations
insightsAIeligibility and a ready/loading chart: InsightsChartWidget.tsx:238–245.These findings explain how all controls can be absent, but do not identify which prerequisite failed for the reported account. No runtime reproduction or production confirmation was obtained.
What changes do you think we should make in order to solve the problem?
Verify the QA prerequisites before proposing a code fix:
insightsAIeligibility.If eligibility is missing as intended, update the QA prerequisites rather than removing the gate. If eligibility is unexpectedly missing, escalate rollout/enrollment verification to an internal engineer. There is currently insufficient evidence to recommend an App code change.
What alternative solutions did you explore? (Optional)
Removing the beta gate or reverting the tag-scope PR is not supported by the evidence. Missing Concierge readiness remains an alternative explanation requiring account-state inspection.
Next Steps for Contributor+ team:
To refine:
@MelvinBot <your feedback>with the eligibility and Concierge-readiness results.To reject: Explain which finding is incorrect.
view run