Feature Request: Grouping and aggregation in list view

Ouverte
#277 0 commentaires 1 réaction 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
15/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Calme
Stack technique
go
Domaine
backend, frontend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Go
Étoiles
421
Forks
50
Merge moyen
17 h 34 min
PR mergées (30 j)
80

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Windshiftapp/core

Toutes les issues de Windshiftapp/core

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.