Current situation : in Composer, as an admin, I can decide to clear the circulation of the cloned story when a user clones a story. This is fine.
Nevertheless, the primary website can't be cleared and still contains the value from original story. It creates a discrepancy in the production dashboard and some unexpected negative consequences in Websked search results (cf. ACS-24078).
Wished situation: I have several propositions to make here to make life easier for users.
as an admin, I should be able to configure Composer to clear the primary website of a cloned story (same way as for circulation)
It should be possible as an admin to move the primary website dropdown from Planning tab to Circulation (where it looks more sensible to have it)
When a story has one its circulations set on one single website then this website should be set automatically to this website by Composer
Other way to present previous option : as a user, if I set a website as the primary website of a story, when I open the circulation modal, this primary website should be automatically selected so that I simply have to choose the section(s) where I want to circulate my story. Of course, it should not prevent me from circulating in other websites.
Guillaume Lefebvre
With the release of Composer 2.0, we now have the ability to clear primary website from a modal when a user decides to clone a story.