[BUG] Saving Configure Board hides all workspace tools (Iterations, Milestones, Pages...) and enables Queue
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- Medio día
- Aptitud para principiantes
- 68/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- javascript
- Área
- frontend
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Go
- Estrellas
- 421
- Forks
- 50
- Merge medio
- 17 h 34 min
- PR fusionados (30 d)
- 80
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Windshiftapp/core
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Windshiftapp/core#542 ·
Los mantenedores suelen responder en 1 día
-
Time Tracking FilteringAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Windshiftapp/core#334 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Windshiftapp/core#259 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
[Bug][AI chat] Select menu dont appear when on index pagePosiblemente ocupada @valentimarco la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 20/100
Windshiftapp/core#541 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
Windshiftapp/core#538 · 1 reacción ·
Los mantenedores suelen responder en 1 día
Todos los issues de Windshiftapp/core
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
karmada-io/karmada#8101 ·
Los mantenedores suelen responder en 1 día
-
product:platform
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Infisical/infisical#9746 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
CrossEntropyFilter raises on zero probabilities and single-class resultsPosiblemente ocupada @NopeCharon la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
txn2/mcp-data-platform#2728 ·
Los mantenedores suelen responder en 1 día
-
effort:s impact:low raised-by:worker risk:low
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
medici-finance/assay#7259 · 1 comentario ·
Los mantenedores suelen responder en 1 día