Hi @Stéphane,

Thank you for this suggestion with which I agree.

Let’s see how many votes it gets but I’m pretty sure you’re not alone with this need.

However, if we satisfy this request, it will certainly be in the as part of the new configuration UI, not in the legacy pages.

I’m sad to hear that. Centreon needs more bug fixes than a new configuration UI. What’s wrong with the current configuration UI?

Also, I hope you won’t make the same error than with the new monitoring UI (Resources Status page), deprecating the current working UI to force the use of a buggy new UI. That was (and still is) a non-sens.
Please provide this new UI as an optional beta feature first.

Still not possible nine month later and it sucks.

maybe

• unlock (in db)
• duplicate
• lock back?

Hi,
Yeah this is exactly what I’m doing when I need to. Do you think having to manually issue SQL commands can be considered as an acceptable way of doing that? There is a good reason for commands and templates to be locked: to prevent modification. There is absolutely no reason for them to be impossible to duplicate within the application, it’s a non-sense..

I hear ya, I am not in the loop for the WHY. I guess that is where the:

NEEDS VOTES

comes into play. I had upvoted b4. 

>However, if we satisfy this request, it will certainly be in the as part of the new configuration UI, not in the legacy pages.

The current code is so spaghetti-like that it is not possible to fix? If the problem would be having  the possibility to select a record while having then an action which does nothing, that is, indeed, not perfect, it really isn’t a problem, because this is already what we have if attempting to clone an object twice without renaming the first clone before creating the second one (or clone one, then clone the clone).
If an increment the suffix of clones is not something that could currently be implemented by the dev team I’m speechless.
 

Delivered in 24.10. See 

Nice. I hope I’d be able to test 24.10 soon. Currently our users still getting themselves used to the new Resource Status page and still ask for the legacy pages for few things.

From the link above:

“Duplicating a Locked Command: Centreon Monitoring Connectors now allow duplication and editing of Centreon-delivered locked commands.”

Hence what’s the specificity of a locked command, compared to a standard command? Also, does this apply to templates too?





 

Locked commands are the ones that Centreon delivers as packs with templates hence why they cannot be edited or that would cause issues at update/upgrade. The new feature allows to duplicate such command so you can work on your own copy.