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

Add time-tracking events to webhook #18582

Open
anbraten opened this issue Feb 3, 2022 · 1 comment
Open

Add time-tracking events to webhook #18582

anbraten opened this issue Feb 3, 2022 · 1 comment
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@anbraten
Copy link
Contributor

anbraten commented Feb 3, 2022

Feature Description

To integrate tools like Clockify or Traggo with Giteas time-tracking adding a new event type for time-trackings to the webhook settings of a project would be helpful. Those tools have quite advanced analytics which I wont expect Gitea to implement in the near future, but as tracking time on issues and PRs in Gitea is quite cool and convenient, I would like to have some webhook to call a service which could for example create entries via the Clockify api.

Screenshots

No response

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Feb 4, 2022
@SystemZ
Copy link

SystemZ commented Aug 3, 2022

I migrated from gitlab recently. I wanted to integrate with clockify with gitea events like pressing start/stop of time tracking and manually entering time but unfortunately I discovered that there aren't any events for that.

Those events would be really helpful to prevent bloat of gitea itself, advanced reporting can be easily integrated in separate app with webhooks.

Kinda related issue: #3998

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

3 participants