After pressing the "Purge" button, the queue is purged as expected, bu tthe user is taken back to the same page with the "Purge" button.
This is misleading as a user might not realize that the Queue is already purged (there is no feedback) and press the button repeatedly.
Ideally, after purging, the app should take the user back to the home page.

In the code, it navigates back to the previous page, but this being the submit for the purge button, the previous page ends up being the same page.

The Purge Build Queue plugin adds a menu item to the homepage that tries to use the images/32x32/gear2.png image, but that image was itself purged recently.

What feature do you want to see added?

On this plugin https://plugins.jenkins.io/purge-build-queue-plugin/ it purges all the queues but can we set a flag that allows users to select the queue type? pending vs stuck? so flow is when this plugin is installed, on gui, clicking it should give option to chose all or stuck.

Upstream changes

No response

Are you interested in contributing this feature?

yes.

JEP-229 should not result in "rc" versions. Make sure you applied https://www.jenkins.io/doc/developer/publishing/releasing-cd/#pom-file-modifications correctly.

Note that it's possible to continue having major/minor that are manually controlled, so it's not required to switch to "full" JEP-229 versions, see further down the docs.

(I suggest tooling improvements in jenkins-infra/jenkins-maven-cd-action#15 to prevent this in the future.)