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

Improve Time Tracking Overview #7708

Closed
16 tasks done
knollengewaechs opened this issue Mar 20, 2024 · 0 comments · Fixed by #7733
Closed
16 tasks done

Improve Time Tracking Overview #7708

knollengewaechs opened this issue Mar 20, 2024 · 0 comments · Fixed by #7733

Comments

@knollengewaechs
Copy link
Contributor

knollengewaechs commented Mar 20, 2024

Detailed Description

Discuss requirements:

  • what is in the csv in detail? (user name/id/email? dataset orga/name or id?)
  • csv export of whole table: include per-annotation lines? or just sums of users?
  • How should this look for a non-privileged user (see only themselves in list I guess?)

TOOD back-end:

  • api/time/user/:userId/summedByAnnotation return summed per annotation for expanded table
  • api/time/overview return number of tasks and average time per task?
  • api/time/user/:userId/spans route for csv download per user
  • adapt e2e tests

ToDos frontend:

  • add export button to export user time spans
  • add stats:
    • no tasks,
    • avg time per task per user;
    • segments and trees per task/annotation
  • show id of annotation/task
  • group time spans per annotation/task
  • fix sorting in table
  • fix details: data is not matching overview

Follow-up for #5375

@knollengewaechs knollengewaechs self-assigned this Mar 20, 2024
@knollengewaechs knollengewaechs changed the title Remove Google Chart and Improve Time Tracking Overview Improve Time Tracking Overview Mar 26, 2024
@fm3 fm3 self-assigned this Mar 28, 2024
@fm3 fm3 closed this as completed in #7733 May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants