[Feature]: Add ticket to calendar event

[lilosti]

What is your set up?

Self Hosted Docker

Is your feature request related to a problem? Please describe

No response

Describe the solution you'd like

It would be nice to be able to quickly log time from a calendar event. This could be done by being able to add a ticket to an event, and then log the time the event is occupying in the calendar on that ticket. Use the calendar information as a comment on the worklog.

Additional context

No response

[marcelfolaron]

What would be the difference between the event and a task that has a scheduled date? Would it be easier to have a task type that is called "event" or similar? Or is this primarily for external events that don't have a task in leantime yet?

[lilosti]

Hi, The problem is this: I have a lot of meetings everyday, scheduled in my calendar. I have to register all my time, and what it is spent on. I have imported my calendar from outlook to leantime - very nice, I don't have to create all the content twice - if there was an easy way to connect an event in the calendar to an issue it would be very easy for me to use the calendar to register my time. Does it make sense? I don't need a todo for each calendar entry, as they sometimes needs to be registered on the same todo. Don't hesitate if you have more questions! /Line Fra: Marcel Folaron ***@***.***> Sendt: 30. januar 2025 20:01 Til: Leantime/leantime ***@***.***> Cc: Line Løfquist Stiil ***@***.***>; Author ***@***.***> Emne: Re: [Leantime/leantime] [Feature]: Add ticket to calendar event (Issue #2914) ***@***.*** What would be the difference between the event and a task that has a scheduled date? Would it be easier to have a task type that is called "event" or similar? Or is this primarily for external events that don't have a task in leantime yet? - Reply to this email directly, view it on GitHub<#2914 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOQPLPVA57LBA3PDGYU7UUT2NJZE7AVCNFSM6AAAAABWCR4ATGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRVGMZTCOBUHA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[marcelfolaron]

Thank you, that makes sense. I'll take a look at how we may be able to implement this.