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:
Launch app
Tap on a report with no prior conversation
Create a submit expense
Open newly created expense and tap header
Note tapping header user directed to details page and transaction thread header is tappable.
Create another submit expense
Tap on header in details page of 2nd created expense
Note transaction thread header is not tappable. Tapping header doesn't trigger any action.
Now open 1st created expense and tap on header in details page
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?
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 Owner Current Issue Owner: @sonialiap
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:
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?
Screenshots/Videos
Bug6464613_1714379187298.ippu.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @sonialiap