App: [$250] [Tags] Newly added tag status is `disabled` and refreshing the page changes to `enabled`
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.52-0 Reproducible in staging?: y Reproducible in production?: n If this was caught during regression testing, add the test name, ID and link from TestRail: n/a 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:
Precondition:
- User is an admin of Collect workspace.
- Go to staging.new.expensify.com.
- Go to Settings > Workspaces > Collect workspace.
- Go to Categories.
- Click Add category and add a category.
- Note that the status of the new category is “Enabled”.
- Go to Tags.
- Click Add tag and add a tag. observe the status of the tag
- As employee, initiate a expense report flow and click on the tag OR
- Refresh the page at the step 7
Expected Result:
Newly added tag should be enabled by default or the tag should not show for employee since it is disabled by default
Actual Result:
- New tag status is
disabledand when refreshing the page it changes toenabled - For employee the added tag showing to select
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
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/1df25d9b-e364-4ac6-a7c3-0b3ec4bc0fc3
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~010353991d7fc3df7f
- Upwork Job ID: 1768104273053810688
- Last Price Increase: 2024-03-14
About this issue
- Original URL
- State: closed
- Created 4 months ago
- Comments: 19 (13 by maintainers)
@trjExpensify adding to wave-collect as this is tag related
Thanks for the ping. We’ll address this in a follow up PR since this feature is still WIP. cc @waterim all tags should be enabled by default.
@jeremy-croff Good point! cc: @luacmartins for clarification on the proper behavior here 🙏
The requirements for this are unclear as there’s no real precedence. Should the default state of tags be enabled, or disabled, and the BE shouldn’t be enabling it?
There’s a design doc on this in here https://github.com/Expensify/App/issues/37311 but I don’t have access. Is this experience confirmed?