Skip to content

[$250] Expense-When there is more than an expense,transaction thread header is not tappable #41196

Description

@izarutskaya

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.4.67-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4522261
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

  1. Launch app
  2. Tap on a report with no prior conversation
  3. Create a submit expense
  4. Open newly created expense and tap header
  5. Note tapping header user directed to details page and transaction thread header is tappable.
  6. Create another submit expense
  7. Tap on header in details page of 2nd created expense
  8. Note transaction thread header is not tappable. Tapping header doesn't trigger any action.
  9. Now open 1st created expense and tap on header in details page
  10. Now note for 1st expense also, transaction thread is not tappable.

Expected Result:

When there is more than one expense also , the transaction thread header must be tappable.

Actual Result:

When there is only one expense, the header is tappable. But, when there is more than one expense, the transaction thread header is not tappable.

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

Screenshots/Videos

Bug6464613_1714379187298.ippu.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01f6dab494ed59d319
  • Upwork Job ID: 1786024164842852352
  • Last Price Increase: 2024-05-02
  • Automatic offers:
    • dukenv0307 | Reviewer | 0
    • bernhardoj | Contributor | 0
Issue OwnerCurrent Issue Owner: @sonialiap

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorMonthlyKSv2ReviewingHas a PR in review

Type

No type

Fields

No fields configured for issues without a type.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions