<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/1a3929d7e6c743ce9eb75bddfa0fa8bd&quot; frameborder=&quot;0&quot; width=&quot;2304&quot; height=&quot;1728&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1728</height><width>2304</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1728</thumbnail_height><thumbnail_width>2304</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/1a3929d7e6c743ce9eb75bddfa0fa8bd-87ab56016c9992c1.gif</thumbnail_url><duration>156.364</duration><title>Getting Started With Changelogs</title><description>The demo walks through the process of creating a changelog update with Released. 

We start by selecting which issues to include, such as everything since the last announcement, updates from a specific time frame, or a particular version. You can apply filters based on labels, issue types, or Jira filters to refine the list of issues. 

Once the relevant issues are selected, you can either generate a description for each individual ticket or use a pre-set template to automate the process. 

The generated changelog can then be reviewed and published, ensuring stakeholders stay informed about recent updates.</description></oembed>