Workspace is_hidden fixture is not being applied during migration
frappe/frappe 1 comments 1mo ago
lowopenScope: somewhat clearSkill match: maybeFrappe / ERPNextPython
Why this is a good first issue
Fixture property is not being applied during migration but works with manual import.
AI Summary
The issue involves Workspace fixtures not retaining their is_hidden property during migration, though it works when manually importing fixtures. The problem seems isolated to the migration process, but maintainer feedback is unclear and there may be underlying migration complexities.
Issue Description
Description of the issue
When migrating, the Workspace fixtures that include the is_hidden property do not apply as expected. Even though the fixture JSON specifies "is_hidden": 1, the value is ignored or overwritten during the migration process.
Context information (for bug reports)
Caused by https://github.com/frappe/frappe/pull/21470
Output of bench version
NONE
Steps to reproduce the issue
- Add a Workspace fixture with "is_hidden": 1.
- Run bench --site migrate.
- Check the workspace list or Desk
- Notice that the workspaces are still visible.
Observed result
Expected result
Workspaces marked with "is_hidden": 1 in fixtures should remain hidden after running bench migrate.
Actual Behavior
- The is_hidden flag is reset during migration, causing previously hidden workspaces to reappear.
- Running bench import-fixtures after migration applies the change correctly, but this does not persist automatically during migration.
Stacktrace / full error message
NONE
Additional information
ERPNext: v15.72.1 (version-15) Frappe Framework: v15.75.0 (version-15)
GitHub Labels
bug
Want to work on this?
Claim this issue to let others know you're working on it. You'll earn 10 points when you complete it!
Risk Flags
- maintainer feedback unclear
- potential migration complexity
Loading labels...
sokumon