Expense Review: add display fields and group by them for analysis

Open
#145 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
csharp
Domain
analytics

Research direction

The issue does not name files, tests, or which display fields to add. First identify the Expense Review results and grouping entry points, then ask the maintainer to decide which fields belong in scope. Done means the chosen fields appear in results and analysts can group by them with totals for each group.

Written by the indexing model from the issue text.

Description

Add more display fields to Expense Review and let the analyst group results by those fields for analysis.

Scope

  • Add the extra display fields to the Expense Review results
  • Allow grouping by those fields, with totals per group

Open question

  • Which fields to add
Dominant language
C#
Stars
0
Forks
0
Avg merge
1d 23h
Merged PRs (30d)
16

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ucdavis/AD419

All issues in ucdavis/AD419

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.