<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Feature Request - Duplicate Meeting Type / Availability Schedule and/or Template system]]></title><description><![CDATA[<p dir="auto">When creating a Meeting Type or an availability Schedule, it would be great to be able to "duplicate" or "copy from" an existing one.</p>
<p dir="auto">Depending on the this would represent a certain amount of gained time at setup.</p>
<p dir="auto">An addition/alternative would be the possibility to define Meeting Time / availability Schedule Template, to derivate from when creating individual ones.</p>
<p dir="auto">This template system could also be relevant when deploying Tymeslot in an enterprise, where preset-enterprise template could be used by individual users to create individual meeting Type / availability schedule, based on company requirements (set in the template).</p>
<p dir="auto">Hopefully this makes sense too</p>
]]></description><link>https://forum.cloudron.io/topic/16133/feature-request-duplicate-meeting-type-availability-schedule-and-or-template-system</link><generator>RSS for Node</generator><lastBuildDate>Thu, 05 Nov 2026 06:34:21 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/16133.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 15 Oct 2026 16:11:52 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Feature Request - Duplicate Meeting Type / Availability Schedule and/or Template system on Fri, 16 Oct 2026 09:09:31 GMT]]></title><description><![CDATA[<p dir="auto">Yes, that sounds reasonable, I'll work on this, but there are a few more items with higher priority right now.</p>
]]></description><link>https://forum.cloudron.io/post/131086</link><guid isPermaLink="true">https://forum.cloudron.io/post/131086</guid><dc:creator><![CDATA[ekevu123]]></dc:creator><pubDate>Fri, 16 Oct 2026 09:09:31 GMT</pubDate></item></channel></rss>