What do we want to do with the plugin-proposals component on Jira?

35 views
Skip to first unread message

Tim Jacomb

unread,
Apr 17, 2026, 9:44:06 AMApr 17
to Jenkins Developers
Hi 

I'm looking into what should be done with the plugin proposals component on Jira:

There's 84 open and 380 issues total. It's one of the biggest remaining components on Jira.

Quickly reviewing them, they're mostly feature requests not really a 'plugin proposal'. Most are quite old.

Questions if any one has got any feedback?
* Do we want to have a plugin proposal issue tracker going forward? We could have an issue form on the jenkins core issue tracker to get a structured one? Or a different repo for it?
* Do we want to migrate the existing ones in for completeness? Or we could archive them in Jira?

Cheers
Tim

Mark Waite

unread,
Apr 17, 2026, 11:07:33 AMApr 17
to jenkin...@googlegroups.com
On Fri, Apr 17, 2026 at 7:44 AM Tim Jacomb wrote:
Hi 

I'm looking into what should be done with the plugin proposals component on Jira:

There's 84 open and 380 issues total. It's one of the biggest remaining components on Jira.

Quickly reviewing them, they're mostly feature requests not really a 'plugin proposal'. Most are quite old.

Questions if any one has got any feedback?
* Do we want to have a plugin proposal issue tracker going forward? We could have an issue form on the jenkins core issue tracker to get a structured one? Or a different repo for it?

I don't see any significant benefit to tracking plugin proposals.  I'd rather not clutter the Jenkins core issue tracker with plugin proposals.
 
* Do we want to migrate the existing ones in for completeness? Or we could archive them in Jira?

I think we should archive them in Jira without migrating them to any other location.

Mark Waite

Jesse Glick

unread,
Apr 20, 2026, 5:57:19 PMApr 20
to jenkin...@googlegroups.com
This seems like a better use of GtHub Discussions than an issue tracker.

CONFIDENTIALITY NOTICE: This email and any attachments contain confidential and proprietary information of CloudBees intended only for the named recipient(s). Unauthorized use or distribution is prohibited. If you received this in error, please notify the sender and delete this email.

Tim Jacomb

unread,
Apr 21, 2026, 5:45:19 AMApr 21
to jenkin...@googlegroups.com
Good point I was thinking a category on community.jenkins.io could work and then just archive the existing ones?

On Mon, 20 Apr 2026 at 22:57, 'Jesse Glick' via Jenkins Developers <jenkin...@googlegroups.com> wrote:
This seems like a better use of GtHub Discussions than an issue tracker.

CONFIDENTIALITY NOTICE: This email and any attachments contain confidential and proprietary information of CloudBees intended only for the named recipient(s). Unauthorized use or distribution is prohibited. If you received this in error, please notify the sender and delete this email.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1V7-eO_tZ7n6KVz173p6cdiUs%2BkoS%3DKvP4dTSMJehYdw%40mail.gmail.com.

Jesse Glick

unread,
Apr 21, 2026, 7:59:02 AMApr 21
to jenkin...@googlegroups.com
On Tue, Apr 21, 2026 at 5:45 AM Tim Jacomb <timja...@gmail.com> wrote:
a category on community.jenkins.io could work and then just archive the existing ones?

That would work too.
Reply all
Reply to author
Forward
0 new messages