[JENKINS-59482] Improve UX for selecting user-scoped credentials

Hi there, since JENKINS-58170">JENKINS-58170 there's a new checkbox - "List user credentials" in the credentials parameter, that's by default unchecked. When checked, the user-scoped secrets can be selected from the drop-down.

This changed the previous behavior which had no checkbox and the drop-down contained the user-scoped creds by default.

Although I think I understand the reasoning behind why it was added, I don't think all users need to explicitly consent twice that they want to select a user-scoped credential.

My whole team uses these parameters as a workaround to JENKINS-44772">JENKINS-44772 several times a day and we all would be thrilled for a fix. As I know there's quite some hesitance to fix it at all, we'll be grateful for at least some old-days compatible UX:

• One approach could be to add a config option for the default state of the user-scoped checkbox in the configuration/pipeline script (along these lines).


• Another option could be to allow selecting user-scoped credentials by default as before, but display the warning when a user-scoped credential gets selected.

Both options are IMHO quite easy to implement and they would give users more control while retaining the new safety measures where desired.

---
Originally reported by vit_zikmund, imported from: Improve UX for selecting user-scoped credentials

• status: Open
  
• priority: Minor
  
• component(s): credentials-plugin
  
• label(s): user-experience
  
• resolution: Unresolved
  
• votes: 3
  
• watchers: 3
  
• imported: 2025-12-08
  

Raw content of original issue

Hi there, since JENKINS-58170 there's a new checkbox - "List user credentials" in the credentials parameter, that's by default unchecked. When checked, the user-scoped secrets can be selected from the drop-down.


This changed the previous behavior which had no checkbox and the drop-down contained the user-scoped creds by default.


Although I think I understand the reasoning behind why it was added, I don't think all users need to explicitly consent twice that they want to select a user-scoped credential.


My whole team uses these parameters as a workaround to JENKINS-44772 several times a day and we all would be thrilled for a fix. As I know there's quite some hesitance to fix it at all, we'll be grateful for at least some old-days compatible UX:




	
One approach could be to add a config option for the default state of the user-scoped checkbox in the configuration/pipeline script (along these lines).

	
Another option could be to allow selecting user-scoped credentials by default as before, but display the warning when a user-scoped credential gets selected.



Both options are IMHO quite easy to implement and they would give users more control while retaining the new safety measures where desired.

• environment:  credentials-2.3.0