[JENKINS-16227] ProjectNamingStrategy: remove Default Strategy from the UI

[timja]

The feature design allows a user to check Restrict project naming with the Default strategy. This is confusing. The user may wonder about the difference between not using the feature at all and selecting the Default strategy.
The Default strategy is an implemenation detail that should not surface to the user. Removing the choice from the configuration area and using it silently if the whole feature is disabled would improve clarity.

---

Originally reported by albers, imported from: ProjectNamingStrategy: remove Default Strategy from the UI

• status: Open
• priority: Trivial
• resolution: Unresolved
• imported: 2022/01/10

[timja]

danielbeck:

IMO the config page should get rid of the check box and just always show the option selection, but as a dropdown list, not the current radio button style, similar to e.g. Markup Formatter selection.

[timja]

albers:

This would be a much better solution than my original suggestion.

[timja]

integer:

+1 for show always, because jenkins always checks job name using ProjectNamingStrategy.
"Default" maybe renamed to "Allow all"

[timja]

albers:

for "Allow all"

[timja]

yogeek:

Hi, 

I am currently having a weird behaviour concerning the "Restrict project naming" option and I think it is related to the current issue :

• Initial state : the "Restrict project naming" checkbox is checked  and a Strategy is chosen (let's take "Default" one for example)
• I do not want to restrict naming so I uncheck the checkbox and save the configuration
• I reload the page : the checkbox is checked again !?! Seems impossible to disable this option

It is quite disturbing because in the UI, it seems possible to disable this option whereas I may understand with the current discussion that in reality the way to diable it is to choose "Default" strategy and the result is apparently the same. Is that right ?

I know it has been some time since this ticket has been opened but would it be possible to look at it again please ?

Environment : 

• Jenkins version : 2.121.1
• Role Strategy plugin version : 2.8.1

 

Update : after reading the code, it seems that this "Restrict project naming" checkbox component is currently an optionalBlock (cf. here).

Souldn't it be non-optional regarding to the real behaviour ?

[timja]

[Originally related to: JENKINS-23218]