Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: "per_task" type of CSV report #100

Closed
pwa-tapptic opened this issue Oct 24, 2023 · 3 comments
Closed

Feature request: "per_task" type of CSV report #100

pwa-tapptic opened this issue Oct 24, 2023 · 3 comments

Comments

@pwa-tapptic
Copy link

pwa-tapptic commented Oct 24, 2023

Hello guys, thanks for the awesome tool you've created!
I'm rather hardcore UTT user and it would be extremely helpful to extend a bit the CSV reports, for they can be nicely "piped" into tools such as csvlens (utt ... --csv-section ... | csvlens). Now there is actually only per_day "mode" which is not entirely helpful in analyzing a particular day(s) in details.

The proposition would be to have per_task that will print a bit detailed overview, i.e.:

Tasks,Project,Date,Duration,
"coding","awesome project",2023-10-24,1h55
"meeting","awesome project",2023-10-24,1h55
"reviewing","awesome project",2023-10-24,1h55

csvlens print:

────────────────────────────────────────────────────────────────────────────────
      Tasks        Project            Date          Duration
───┬────────────────────────────────────────────────────────────┬───────────────
1  │  coding       awesome project    2023-10-24    1h55        │
2  │  meeting      awesome project    2023-10-24    1h55        │
3  │  reviewing    awesome project    2023-10-24    1h55        │

I could help in contributing if you find it worth including in the main package.

@pwa-tapptic
Copy link
Author

@larose what do you think? I can implement it as my local extension but IMO it makes sense to include it in the main package, for idea of different types of csv reports is actually expressed in the parameters.

@larose
Copy link
Owner

larose commented Dec 9, 2023

Hi @pwa-tapptic! Absolutely, I'd appreciate your contribution as it appears to be a valid use case. To include it in this repo, make sure your pull request has at least some integration tests. Thanks!

@larose
Copy link
Owner

larose commented Jan 18, 2024

Implemented in #101

@larose larose closed this as completed Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants