Skip to content

Chat - Unavailable to access an account detail page via the header of conversation #29335

New issue
New issue
Closed
Closed
Chat - Unavailable to access an account detail page via the header of conversation#29335
Assignees
peterdbarkerUKthienlnam
Labels
BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Description

@lanitochka17
lanitochka17
opened on Oct 11, 2023

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

Version Number: 1.3.81-5

Reproducible in staging?: Yes

Reproducible in production?: No

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

Action Performed:

  1. Go to https://staging.new.expensify.com/
  2. Log in with any user
  3. Create a group with 2 other accounts you have access
  4. Navigate to the created conversation and access account detail page via the header

Expected Result:

Available to access the account details page via the header

Actual Result:

Unavailable to access an account detail page via the header of created conversation

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
  • Windows: Chrome

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
Windows: Chrome
Bug6233232_1697039951741.access_the_2_account_details_page.mp4

View all open jobs on GitHub

Activity

  1. lanitochka17
    added
    DeployBlockerCashThis issue or pull request should block deployment
    DailyKSv2
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 11, 2023
  2. melvin-bot
    assigned
    peterdbarkerUK
    on Oct 11, 2023

  3. melvin-bot commented on Oct 11, 2023

    @melvin-bot
    melvin-botBot
    on Oct 11, 2023

    Triggered auto assignment to @peterdbarkerUK (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  4. melvin-bot commented on Oct 11, 2023

    @melvin-bot
    melvin-botBot
    on Oct 11, 2023

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  5. github-actions
    added
    Engineering
    HourlyKSv2
    and removed
    DailyKSv2
    on Oct 11, 2023

  6. OSBotify commented on Oct 11, 2023

    @OSBotify
    OSBotify
    on Oct 11, 2023
    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.
  7. melvin-bot
    assigned
    thienlnam
    on Oct 11, 2023

  8. melvin-bot commented on Oct 11, 2023

    @melvin-bot
    melvin-botBot
    on Oct 11, 2023

    Triggered auto assignment to @thienlnam (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  9. techievivek
    removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Oct 11, 2023

  10. techievivek commented on Oct 11, 2023

    @techievivek
    techievivek
    on Oct 11, 2023
    Contributor

    This is not a blocker but rather an expected behaviour, we updated the way group chat headers behaves: #27394

    I am not sure what is the procedure to update the regression test for this.

    CC @MitchExpensify @trjExpensify

  11. MitchExpensify
    added
    DailyKSv2
    and removed
    HourlyKSv2
    on Oct 11, 2023

  12. MitchExpensify commented on Oct 11, 2023

    @MitchExpensify
    MitchExpensify
    on Oct 11, 2023
    Contributor

    Switching to Daily as a not a blocker according to @techievivek

  13. techievivek commented on Oct 13, 2023

    @techievivek
    techievivek
    on Oct 13, 2023
    Contributor

    Going to close this as this is an expected behaviour, we will need to update the regression tests for group chat which we will do as part of the original GH: #27394

  14. techievivek
    closed this as completedon Oct 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions