Feature Request: Grouping and aggregation in list view

Abierto
#277 0 comentarios 1 reacción 0 asignados Ver en GitHub

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
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
go
Área
backend, frontend

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

enhancement

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:

  1. Group work items by field values
  2. 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

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Windshiftapp/core

Todos los issues de Windshiftapp/core

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.