Feature Request: Grouping and aggregation in list view

Aperta
#277 0 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
go
Ambito
backend, frontend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Go
Stelle
421
Fork
50
Merge medio
17h 34m
PR unite (30g)
80

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Windshiftapp/core

Tutte le issue di Windshiftapp/core

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.