-
Bug
-
Resolution: Unresolved
-
Minor
-
None
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?
[JENKINS-47597] Jenkins UI wording for removing a GitHub-based multibranch Pipeline project is very misleading
| Attachment | New: definitely-not-what-happens.png [ 40072 ] |
| 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. |
| 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 |
| Attachment | Original: definitely-not-what-happens.png [ 40072 ] |
| Attachment | New: fairly-misleading-wording.png [ 40073 ] |
| 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? |
| 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 ] |
I agree, the current wording sounds like it's going to delete your git repository. Yikes!
If it's going to delete the Jenkins Pipeline, why not just call it "Pipeline" in the menu?
Agree that it's really misleading. Even on a recent version of Jenkins, it says "Delete Repository" on both the context menu and on the detail page for the job itself. I think "Delete Pipeline" would also work and is a bit briefer.