Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

Issues Tracker Battle (Github vs JIRA)

63 views
Skip to first unread message

Nikolas Falco

unread,
Dec 6, 2024, 7:09:30 AM12/6/24
to Jenkins Developers
Hi developers,
As a new maintainer of bitbucket-branch-source-plugin I found myself with a lot of open issues to manage, this might be normal. What doesn't seem normal to me, is having two different issue trackers.
When I became maintainer there were about 100 issues on gibhub and more than 100 on JIRA. Now, the effort I'm spending to match issues on github -> JIRA and vice versa, collecting comments, use cases, steps to reproduce the problem... is way too much.
I had a look in this group to see what the decision was for the default issue tracker, but from what I read in a couple of threads it's that the decision was never made but only discussed.
Since most of the core plugins are on JIRA and other plugins I'm the mantainer are on JIRA and, my preference is JIRA because of the workflow, notifications are not mixed with CD tasks notifications, it's easy to switch components, automatic assenee etc etc... all without losing history.
I am here to ask you if the maintainer is able to freeze one of the issue trackers as documented on https://github.com/jenkins-infra/repository-permissions-updater?tab=readme-ov-file#managing-issue-trackers
with the report attribute set to false.
Then I would announce the choose in the README.MD place in the plugin repository and, after all issues are resolved or manually migrated to JIRA (if not already present from another reported), finally remove the issue tab.

Mark Waite

unread,
Dec 6, 2024, 10:42:48 AM12/6/24
to Jenkins Developers
On Friday, December 6, 2024 at 5:09:30 AM UTC-7 nikola...@gmail.com wrote:
Hi developers,
As a new maintainer of bitbucket-branch-source-plugin I found myself with a lot of open issues to manage, this might be normal. What doesn't seem normal to me, is having two different issue trackers.

Thanks for asking.  I have a similar problem in one or more plugins that I've adopted.
 
When I became maintainer there were about 100 issues on gibhub and more than 100 on JIRA. Now, the effort I'm spending to match issues on github -> JIRA and vice versa, collecting comments, use cases, steps to reproduce the problem... is way too much.
I had a look in this group to see what the decision was for the default issue tracker, but from what I read in a couple of threads it's that the decision was never made but only discussed.

The decision remains with the plugin maintainer.
 
Since most of the core plugins are on JIRA and other plugins I'm the mantainer are on JIRA and, my preference is JIRA because of the workflow, notifications are not mixed with CD tasks notifications, it's easy to switch components, automatic assenee etc etc... all without losing history.
I am here to ask you if the maintainer is able to freeze one of the issue trackers as documented on https://github.com/jenkins-infra/repository-permissions-updater?tab=readme-ov-file#managing-issue-trackers
with the report attribute set to false.

That is allowed as far as I understand it.
 
Then I would announce the choose in the README.MD place in the plugin repository and, after all issues are resolved or manually migrated to JIRA (if not already present from another reported), finally remove the issue tab.

That's the same transition that I'm likely to make on a few of the plugins that I maintain, because I prefer Jira for reasons that are similar to yours.

Mark Waite 

Nikolas Falco

unread,
Dec 7, 2024, 12:53:29 PM12/7/24
to Jenkins Developers
Reply all
Reply to author
Forward
0 new messages