Feature Request: Grouping and aggregation in list view
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 15/100
Línea de trabajo
This is design work spanning the list view UI and the backend query layer, so start by reading how the existing list view filters and sorts work items and how the server builds that query. Agree on the grouping model and the SUM semantics (per-group and overall totals) with maintainers before writing code. Done means a maintainer-approved design plus an implementation that groups by one field and sums one numeric column, with tests.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Description
It would be very useful to extend the list view with grouping and aggregation capabilities.
The goal is to make the list view suitable not only for displaying and filtering work items, but also for creating structured overviews based on field values.
Two related capabilities would be particularly useful:
- Group work items by field values
- Calculate sums for numeric fields
1. Grouping by field values
Users should be able to select a field by which the current list is grouped.
For example, when grouping by an Asset custom field, Windshift could create a hierarchical/tree-like view such as:
- Customer A
- Work Item 1
- Work Item 2
- Work Item 3
- Customer B
- Work Item 4
- Work Item 5
- No value
- Work Item 6
The same concept should ideally work with other suitable field types as well, for example:
- Assets
- Select fields
- Status
- Assignee
- User fields
- Project
- Other custom fields with discrete values
Groups should be collapsible/expandable so that the user can navigate larger result sets efficiently.
Expected functionality
- Select a field to group the current list by
- Automatically create groups based on the field values
- Display the corresponding work items below each group
- Provide a separate group for work items without a value
- Allow groups to be collapsed and expanded
- Keep the configured columns visible within the grouped view
2. Aggregation of numeric fields
For numeric fields displayed as columns, it should be possible to calculate aggregated values.
At minimum, SUM would be very useful.
When grouping is enabled, the list could display:
- Sum per group
- Overall sum across all displayed work items
Example
| Work Item | Customer | Estimated Cost | Actual Cost |
|---|---|---|---|
| Customer A | 15,000 | 12,500 | |
| Work Item 1 | Customer A | 10,000 | 8,000 |
| Work Item 2 | Customer A | 5,000 | 4,500 |
| Customer B | 20,000 | 18,000 | |
| Work Item 3 | Customer B | 20,000 | 18,000 |
| Total | 35,000 | 30,500 |
Ideally, aggregation could later support additional functions such as:
- Sum
- Average
- Minimum
- Maximum
- Count
Use cases
This would make the list view significantly more useful for reporting and management use cases, for example:
- Grouping work items by customer/account asset
- Grouping projects by department or business unit
- Displaying budget totals per customer
- Comparing estimated and actual costs
- Summing effort or story points
- Portfolio and project management overviews
- Financial and capacity-related reporting
Expected outcome
The list view should provide a flexible way to structure work items by field values and calculate aggregates for numeric columns.
This would allow users to create lightweight reporting and management views directly in Windshift without requiring an external reporting tool for relatively simple grouped reports.
- 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