Expense Review: add display fields and group by them for analysis
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
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
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ucdavis/AD419
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 54/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Bug IronPython Python 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pyrevitlabs/pyRevit#4184 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
yusei36/KeePassPasskey#66 · 2 comments ·
Maintainers usually reply within 1 day
-
🐛 bug 🕒 low effort good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
guibranco/Sankhya-SDK-dotnet#654 ·
Maintainers usually reply within 1 day
-
巫女のセリフに声を付けるOpenassets claude-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Fialuxe/MouthOfGod_System#358 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
anatawa12/AvatarOptimizer#1828 ·
Maintainers usually reply within 1 day