# \[Scenes\] Pre-fill the title of a duplicated scene

**URL:** <https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341>\
**Category:** Demandes livrées\
**Tags:** scene, feature-request-ux\
**Created:** [January 28, 2025, 10:34pm UTC](https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341 "2025-01-28T22:34:29Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![StephaneB](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/stephaneb/32/15443_2.png) [@StephaneB](https://community.gladysassistant.com/u/StephaneB)\
**Post date:** [January 28, 2025, 10:34pm UTC](https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341/1 "2025-01-28T22:34:29Z")

</div>

When you duplicate a scene, its title is empty even though duplication is often intended to create a variant of the scene, so the title could be similar. This forces you to copy the title and paste it afterwards, so it would be more convenient if the title were pre-filled with «&nbsp;Copy of [original scene title]&nbsp;».

---

<div class="post-metadata">

**Author:** ![StephaneB](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/stephaneb/32/15443_2.png) [@StephaneB](https://community.gladysassistant.com/u/StephaneB)\
**Post date:** [January 28, 2025, 10:34pm UTC](https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341/2 "2025-01-28T22:34:55Z")

</div>

I’m copying Pierre-Gilles’s reaction:

The problem with that is the title then becomes the ‹&nbsp;selector&nbsp;› (the scene’s unique identifier), and so you’ll end up with scenes called ‹&nbsp;copie-de-detection-mouvement-entree&nbsp;›, instead of your scene’s proper name. Note that the selector is **immutable**.

It’s a choice — you could decide you don’t care about the selector, but it then creates small points of frustration. For example, if you use the Gladys API to trigger scenes, when identifying your scene you’ll have that title which doesn’t match the scene’s current name.

Now, which point of frustration is stronger?

---

<div class="post-metadata">

**Author:** ![StephaneB](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/stephaneb/32/15443_2.png) [@StephaneB](https://community.gladysassistant.com/u/StephaneB)\
**Post date:** [January 28, 2025, 10:37pm UTC](https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341/3 "2025-01-28T22:37:18Z")

</div>

And

---

<div class="post-metadata">

**Author:** ![lmilcent](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lmilcent/32/7023_2.png) [@lmilcent](https://community.gladysassistant.com/u/lmilcent)\
**Post date:** [January 29, 2025, 4:06pm UTC](https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341/4 "2025-01-29T16:06:24Z")

</div>

Good point. I myself often copy / paste the title to change a small part afterwards.

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [January 31, 2025, 8:19am UTC](https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341/5 "2025-01-31T08:19:40Z")

</div>

@StephaneB I know human nature well: if the title is pre-filled, 99% of users will click “Duplicate” without changing anything, thinking “I’ll change it later” 😅

Result: we end up with a multitude of selectors that do not match the title.

So my question: what’s the lesser evil?

---

<div class="post-metadata">

**Author:** ![mutmut](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/mutmut/32/14064_2.png) [@mutmut](https://community.gladysassistant.com/u/mutmut)\
**Post date:** [January 31, 2025, 11:19am UTC](https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341/6 "2025-01-31T11:19:02Z")

</div>

Personally, I prefer to do my own copy/paste if I need to reuse the same name and add something extra, it avoids clicking around and not understanding what’s going on (but that’s how I work).

---

<div class="post-metadata">

**Author:** ![lmilcent](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lmilcent/32/7023_2.png) [@lmilcent](https://community.gladysassistant.com/u/lmilcent)\
**Post date:** [January 31, 2025, 11:40am UTC](https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341/7 "2025-01-31T11:40:33Z")

</div>

That’s what Windows does, duplicating a file will by default show myfile(copy).txt.

I’m not shocked by any of the behaviors. That doesn’t help the thinking, sorry 😆

---

<div class="post-metadata">

**Author:** ![StephaneB](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/stephaneb/32/15443_2.png) [@StephaneB](https://community.gladysassistant.com/u/StephaneB)\
**Post date:** [January 31, 2025, 11:51am UTC](https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341/8 "2025-01-31T11:51:00Z")

</div>

When I happen to get a scene’s name wrong, and if I really want the selector to be clean, I simply duplicate the scene, give it a proper name, and then delete the scene that had the wrong name.

So in my opinion, whoever wants clean selectors will be careful to modify the «&nbsp;copy of [name of the duplicated scene]&nbsp;» or will fix it with the technique I just described, and whoever doesn’t care about selectors won’t be bothered that it keeps a «&nbsp;copy of …&nbsp;»

So I prefer the lesser evil: «&nbsp;prefilled duplicated scene name, even if the selector ends up being copy\_of\_… if I confirmed the name too quickly&nbsp;»

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [January 31, 2025, 12:30pm UTC](https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341/9 "2025-01-31T12:30:55Z")

</div>

Ok @StephaneB, I’m convinced 🙂

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [February 10, 2025, 9:17am UTC](https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341/10 "2025-02-10T09:17:56Z")

</div>

Fixed here:

> <https://github.com/GladysAssistant/Gladys/pull/2226>
>
> \### Pull Request check-list
> 
> To ensure your Pull Request can be accepted as fa…st as possible, make sure to review and check all of these items:
> 
> \- \[x\] If your changes affects code, did your write the tests?
> \- \[x\] Are tests passing? (\`npm test\` on both front/server)
> \- \[x\] Is the linter passing? (\`npm run eslint\` on both front/server)
> \- \[x\] Did you run prettier? (\`npm run prettier\` on both front/server)
> \- \[x\] If you are adding a new features/services, did you run integration comparator? (\`npm run compare-translations\` on front)
> \- \[x\] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community (\[french forum\](https://community.gladysassistant.com/)/\[english forum\](https://en-community.gladysassistant.com/)) for testing before merging.
> 
> \### Description of change
> 
> Fix https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [February 14, 2025, 9:54am UTC](https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341/11 "2025-02-14T09:54:57Z")

</div>

Fixed in Gladys Assistant 4.53.0 :

> [@Gladys Assistant 4.53.0 : ZWaveJS boosté & encore plus d'améliorations UX!](https://community.gladysassistant.com/t/gladys-assistant-4-53-0-zwavejs-booste-encore-plus-dameliorations-ux/9373):
>
> Salut à tous, Les améliorations UX continuent d’affluer dans cette nouvelle version ! rockethammer_and_wrench Améliorations générales Menu Profil : Le menu déroulant «&nbsp;Profil&nbsp;» dans l’en-tête se ferme désormais automatiquement lorsqu’on clique à l’extérieur. Correction du scroll dans la liste des intégrations : Un bug empêchant le retour en haut de la liste a été corrigé pour une navigation plus fluide. Tri amélioré pour les caméras : Les pièces sont maintenant classées par ordre alphabé…

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [February 14, 2025, 9:55am UTC](https://community.gladysassistant.com/t/scenes-pre-remplir-le-titre-dune-scene-dupliquee/9341/12 "2025-02-14T09:55:00Z")

</div>


