If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.
Version Number: 9.4.66-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @dannymcclain
Slack conversation (hyperlinked to channel name): #Expensify Bugs
Action Performed:
- Create a task and assign it to a user.
- Navigate to the task details page.
- Observe the arrows for the Title, Description, and Assignee push rows.
- Compare the arrow style and placement across the three rows.
Expected Result:
The Title, Description, and Assignee push rows should use consistent arrow styling and placement.
Actual Result:
The arrow in the Title push row has a different style and/or placement compared with the Description and Assignee push rows.
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Screenshots/Videos
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @linhvovan29546
If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.
Version Number: 9.4.66-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @dannymcclain
Slack conversation (hyperlinked to channel name): #Expensify Bugs
Action Performed:
Expected Result:
The Title, Description, and Assignee push rows should use consistent arrow styling and placement.
Actual Result:
The arrow in the Title push row has a different style and/or placement compared with the Description and Assignee push rows.
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Screenshots/Videos
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @linhvovan29546