We have a customer, who releases new product versions periodically (e.g., every 6 months) often create new release notes by cloning existing categories and articles. Since the differences between versions are minimal, cloning helps reuse most of the existing content.
However, after cloning, customers need to update the slug of each article to reflect the new version number. When there are a large number of articles (e.g., 100+), manually updating each slug becomes time-consuming and prone to errors.
Customer requests to provide an automation or bulk action that allows them to update the slug for multiple articles at once (for example, replacing the version number in the slug across all selected articles). This would significantly reduce manual effort when preparing release notes for new product versions.