> Confirmed. Hi all. Sorry this was never a bug, but at least now I understand what's happening :)
Closed. The variable `org-icalendar-use-scheduled' controls how scheduled entries are exported. The default value is '(todo-start) With this setting, headlines that are scheduled do not seem to be exported. Consider headline of the form * Heading SCHEDULED: <2026-06-15 Mon> With the default as above, this is not exported. However, changing `org-icalendar-use-scheduled' to '(event-if-not-todo) the headline is then exported. To export both TODO and non-TODO scheduled, headlines set `org-icalendar-use-scheduled' to '(event-if-todo event-if-not-todo) See the docs for more information about how this variable works. There was also a question about changing `SCHEDULED:' to `:SCHEDULED:' and then it seems to export okay. This is not valid syntax for scheduling in org-mode (as far as I can tell). So org-mode doesn't considered it scheduled and so the above behaviour doesn't apply. The headline is just treated as a headline with a timestamp, and that is exported by default. You can see this in the exported ics file which contains DESCRIPTION::SCHEDULED: <2026-06-14 Sun> The string `:SCHEDULED:' is now part of the description. org-mode is just treating it as a string. Deleted `:SCHEDULED:' from the headline (but leaving the timestamp there still) results in the entry being exported with that timestamp as expected. In other words, adding `:SCHEDULED:' to a headline was essentially just treated as text with no specific meaning and was exported in the description (along with any other text in the entry). Hope that answers the question. Sorry for adding the spurious bug tag, but I guess that ups my numbers for closed bugs! Gotta' hit those KPI's ;) -- *Paul*
