[FR] adding an end hour for an event.

[Pikuboy]

Is your feature request related to a problem? Please describe.

Hello,

I didn’t see anything related to this so sorry if I’ve missed it. I recently noticed that you can export the data to ics which is awesome but all events are by default scheduled to 1 hour. Would it be possible to add a field to either mark a duration or and end hour.

Like for example, if you’re doing a guided tour in a museum and it says « duration of the tour 2 hours » it would be very helpful to have that data within the day and then to carry it over the ics.

Thank you!

Describe the solution you'd like

No response

Additional context

No response

Could you implement it?

No - I can't implement it right now

Implementation plan (optional)

No response

[sjorge]

I think I asked for this in the past but I forgot why this wasn't possible.

Places have a duration field but items do not.

I just note down the end time in my description but I can see if you use the calendar this is not a good workaround.

[Pikuboy]

I think I found the post you are mentioning

#140

Add 2 planned items one for the start and one for the end time (There is a duration field on a place but not on a plan item, which is a bit confusing IMHO), personally I just add the expected duration in the comment field on the first line.

itskovacs also replied:

Apologies for the delay; I confused this thread with discussion #155.
TRIP follows a double-entry logic similar to accounting software. This requires users to create separate plans for the start and the end so they can have distinct properties. While I recognize this structure is debatable, it is a deliberate design choice for the application.
Changing this would require rewriting a lot of the backend and logic, so it's not feasible at the moment.

I searched before posting but weirdly, I didn’t find this post. It makes sense it’s not possible but at the same time it doesn’t (at least for me).

To be honest, I never saw the duration field in places because it doesn’t make sense for me to field it before planning.
What confuse me the most is that the ics doesn’t seem to carry that information by creating each event for 1h, this is something that can be manually adjusted after the import in the calendar app of course.

I’ll try to use your workaround by creating two events for one place.