• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: github-plugin
• Labels:

  None

1. 

   fairly-misleading-wording.png

   161 kB

   2017-10-20 05:23

[JENKINS-47597] Jenkins UI wording for removing a GitHub-based multibranch Pipeline project is very misleading

Giles Gaskell created issue - 2017-10-20 04:35

Giles Gaskell made changes - 2017-10-20 04:37

Attachment

New: definitely-not-what-happens.png [ 40072 ]

Giles Gaskell made changes - 2017-10-20 05:22

Description

Original: If I want to remove a multibranch Pipeline from Jenkins, I see the menu option *Delete Repository* instead of *Delete Multibranch Pipeline*. This is fairly confronting to the user, since they might think they're deleting their local Git repository (or one on GitHub, etc).

New: If I want to remove a GitHub-based Multibranch Pipeline from Jenkins, I see the menu option *Delete Repository* instead of *Delete Multibranch Pipeline*. This is somewhat misleading / fairly confronting to the user, since they might think Jenkins may try to delete their repository GitHub.

Giles Gaskell made changes - 2017-10-20 05:22

Summary

Original: Jenkins UI wording for removing a multibranch Pipeline project is very misleading

New: Jenkins UI wording for removing a GitHub-based multibranch Pipeline project is very misleading

Giles Gaskell made changes - 2017-10-20 05:23

Attachment

Original: definitely-not-what-happens.png [ 40072 ]

Giles Gaskell made changes - 2017-10-20 05:23

Attachment

New: fairly-misleading-wording.png [ 40073 ]

Giles Gaskell made changes - 2017-10-23 03:41

Description

Original: If I want to remove a GitHub-based Multibranch Pipeline from Jenkins, I see the menu option *Delete Repository* instead of *Delete Multibranch Pipeline*. This is somewhat misleading / fairly confronting to the user, since they might think Jenkins may try to delete their repository GitHub.

New: If I want to remove a GitHub-based Multibranch Pipeline from Jenkins, I see the menu option *Delete Repository* instead of *Delete Multibranch Pipeline*. This is somewhat misleading / fairly confronting to the user, since they might think Jenkins may try to delete their repository GitHub. I'm fairly certain there is existing wording (presumably in a resource file somewhere) which has *Delete Multibranch Pipeline*, as you see this as an option on the equivalent context-menu to delete a Multibranch Pipeline Project in Jenkins. Therefore, to fix this issue, perhaps the content-menu option resource for deleting a GitHub-based Multibranch Pipeline project in Jenkins should be the same as that for a Multibranch Pipeline Project?

Giles Gaskell made changes - 2017-10-24 05:16

Component/s		New: github-plugin [ 15896 ]
Component/s	Original: content [ 20860 ]
Key	Original: WEBSITE-423	New: JENKINS-47597
Workflow	Original: WEBSITE: Software Development Workflow [ 223323 ]	New: JNJira + In-Review [ 223386 ]
Project	Original: Jenkins Website [ 10401 ]	New: Jenkins [ 10172 ]
Status	Original: To Do [ 10003 ]	New: Open [ 1 ]