We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Break down in numbered steps
Test if this issue gets auto close upon App PR being merged. For context: https://github.com/Expensify/Expensify/issues/173928
Describe what you think should've happened
Describe what actually happened
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Where is this issue occurring?
Version Number: Logs: https://stackoverflow.com/c/expensify/questions/4856 Notes/Photos/Videos: Any additional supporting documentation Expensify/Expensify Issue URL:
View all open jobs on Upwork
The text was updated successfully, but these errors were encountered:
mountiny
No branches or pull requests
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Break down in numbered steps
Test if this issue gets auto close upon App PR being merged. For context: https://github.com/Expensify/Expensify/issues/173928
Expected Result:
Describe what you think should've happened
Actual Result:
Describe what actually happened
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platform:
Where is this issue occurring?
Version Number:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
View all open jobs on Upwork
The text was updated successfully, but these errors were encountered: