On 05.02.2015, at 23:44, Arun Gupta <[email protected]> wrote: > Wondering why there is a separate JIRA as opposed to github issues > itself? This feels disconnected.
Off the top of my head: - Jira allows reassigning components when it turns out that a bug is the responsibility of another component - Jira is the one location users can go to report issues they experience for (almost) all plugins - Use of Jira predates use of Github by the Jenkins project - Jira allows use of a separate private project for reporting security issues that can still be linked to regular issues - Jira allows issues to span multiple components - Jira isn't a thousand separate trackers that make e.g. triaging incoming reports across a number of components, to ensure they have merit and aren't duplicates, almost impossible - We still have plugins in Subversion that need an issue tracker as well - There are even plugins that use neither Subversion nor Github to store their code but may want to integrate with Jenkins project's bug tracking The only thing really wrong with the current system is that some plugins use Github issues (presumably due to personal preference, but I don't know) when it actually only hurts in the overall project context, as it disconnects that specific plugin from what most others are using. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9BF34714-7721-495A-A2CF-37B80EB69CE2%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
