[BUG] Saving Configure Board hides all workspace tools (Iterations, Milestones, Pages...) and enables Queue
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start in frontend/src/lib/settings/BoardConfigurationPage.svelte: the fallback at ~line 207 builds enabledViews from workspaceViewItems, and the save branch at ~line 774 writes it whenever view_settings exists. Read navigation/workspaceNavigation.js for workspaceViewItems, workspaceOnlyViews and DefaultWorkspaceNavItemIDs, then WorkspaceNavigation.svelte to see how enabledNavIds filters the Tools section. Done means saving columns/backlog alone writes no enabled_views and tools stay visible; note the linked issue #456 blocks the UI recovery path.
Written by the indexing model from the issue text.
Description
Summary
Saving the workspace-scope Configure Board page (/workspaces/:id/board/configure) writes an explicit view_settings.enabled_views override that contains only the collection views plus queue. All workspace tools (agents, iterations, milestones, analytics, actions, pages) disappear from the Tools section of the workspace sidebar, and Queue — opt-in by default — shows up.
Because of #456 the Configure navigation page can't be used to turn the tools back on, so the only way out in the UI is gone.
Environment
- Windshift v0.9.3 (Docker image
ghcr.io/windshiftapp/windshift:v0.9.3, SQLite) - The relevant code is identical on
main(checked at5f1578b)
Steps to reproduce
- Create a new workspace (no explicit navigation override yet). The Tools section shows Agents, Iterations, Milestones, Analytics, Actions, Pages.
- Open Board → Configure, change the columns and/or the backlog statuses (I left Completed work: Show all as is).
- Click Save Changes.
Actual: The Tools section only shows Look and Feel and Settings; Queue appears under the views. The board configuration now contains:
"view_settings": {
"completed_visibility": "all",
"enabled_views": ["backlog", "board", "list", "tree", "map", "roadmap", "queue"]
}
Expected: Saving columns/backlog leaves the navigation as it was (tools visible, Queue off), i.e. no enabled_views override is written unless the user changed the Views tab.
I observed this once on a fresh workspace; the cause below is from reading the code, and the stored list matches it exactly.
Cause
frontend/src/lib/settings/BoardConfigurationPage.svelte:
-
When the scope has no override, the Views state falls back to the collection views only (line ~207):
enabledViews = Array.isArray(effectiveViews) && effectiveViews.length > 0 ? [...effectiveViews] : workspaceViewItems.map((view) => view.id); // backlog … roadmap + queue, no toolsworkspaceViewItems(innavigation/workspaceNavigation.js) contains the six board views andqueue; the tools live inworkspaceOnlyViews. -
On save, that list is written as an explicit override as soon as
view_settingsexists at all — which it does oncecompleted_visibilityhas been stored (line ~774):} else if (viewsDirty || boardConfig?.view_settings) { viewSettings.enabled_views = [...enabledViews]; }
WorkspaceNavigation.svelte then filters the Tools section by enabledNavIds(workspaceId), so every tool that isn't in the list is hidden. queue is in workspaceViewItems, so it becomes enabled although it isn't part of DefaultWorkspaceNavItemIDs.
Suggested fix
- Don't write
enabled_viewsunless the Views tab was actually changed (viewsDirty) — an existingview_settingsobject (e.g. onlycompleted_visibility) is not a reason to materialise the default. - At workspace scope, keep the ids this page doesn't manage when saving, e.g. merge back every id from the effective set that isn't one of the page's view ids (tools), instead of replacing the whole list.
- For the inherited case, fall back to the real workspace default (
DefaultWorkspaceNavItemIDs) rather thanworkspaceViewItems.
Workaround
PUT /rest/api/v2/workspaces/:id/board-configuration (token with collections:read + collections:write) with the current configuration and the tool ids appended to view_settings.enabled_views. Columns must be sent in request shape (id, name, display_order, wip_limit, color, status_ids), see #456. PATCH returns 405 on /rest/api/v2.
- Dominant language
- Go
- Stars
- 421
- Forks
- 50
- Avg merge
- 17h 34m
- Merged PRs (30d)
- 80
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Windshiftapp/core
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Windshiftapp/core#542 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Windshiftapp/core#334 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Windshiftapp/core#259 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
[Bug][AI chat] Select menu dont appear when on index pagePossibly taken @valentimarco claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 20/100
Windshiftapp/core#541 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Windshiftapp/core#538 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in Windshiftapp/core
Similar issues
-
good first issue help wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
fullsend-ai/fullsend#9733 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
karmada-io/karmada#8101 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day