I guess we will have a lot of People creating tickets with JIRA but with Github, we will have more People, willing to creating tickets, because they are still Browsing GitHub and the incubator netbeans repo and it is easy to go to that repo, go to issues and create a new one. And we have the GitHub Events, like the hacktoberfest, which is of Course only one, dunno, whether there are more or not.
Yes the duplicates are the Problem. So Maybe we should leave it as it is, until we find a very good synch mechanism between both Systems. My ideal world is to find a Plugin for JIRA, which will create the +1000 tickets, that we have into the GitHub repo, only to have it there as a history and to close them as fixed etc. and vice versa, the issues at GitHub, will create JIRA tickets. We Need a Plugin to only create a ticket in jira, which will create a GitHub issues with a specific template like ticket type, components, labels, etc. (we will not cover all Features of jira) and the same for GitHub to JIRA. My 2 cents. Cheers Chris P.S. when I will have time and if we find a common sense, I can have a look whether I will find a JIRA Plugin or whether I have to create my own for this. Von: Eirik Bakke Gesendet: Donnerstag, 18. Oktober 2018 16:53 An: [email protected] Betreff: RE: Hacktoberfest I suspect having two issue trackers active at the same time would become very messy. Some bugs will have JIRA issue numbers, others will have GitHub-generated issue numbers, some bugs will exist in just one system, some in both etc. And if people can file bugs without being aware of JIRA, there will be more duplicates filed (as you mention). And there would not be an easy way to mark a bug as a duplicate of a bug in the other system. And bug discussions would be split between two systems. And people without JIRA accounts would not be able to follow JIRA bugs. And so on. I'd encourage sticking to just JIRA as the official "system of record", pointing people there to file new bugs. -- Eirik -----Original Message----- From: Christian Lenz <[email protected]> Sent: Thursday, October 18, 2018 3:46 AM To: [email protected] Subject: AW: Hacktoberfest Maybe it is to late but we also should activate the GitHub issues again. I asked in the infrachat and if I understand it correct, there is no Problem while using GitHub as an issue Tracker too. It seems possible to create jira tickets from GitHub issues, but not vice versa (Plugin missing, must be written, etc.) to cover the Basic stuff. I know that jira and GitHub issues are very different Systems, but for Basic Generation of issues, that could be possible. Anyway, we will also have the Problem of duplicates. So is there anything else, what doesn’t make sense to Show issues on the incubator-netbeans repo? A lot more People will create tickets on the favorite repo System, instead of creating a JIRA account. And, again the issue section will help us with the next hacktoberfest, where we can have Benefits out of it. Cheers Chris Von: Christian Lenz Gesendet: Dienstag, 2. Oktober 2018 09:48 An: [email protected] Betreff: Hacktoberfest Hey, I didn’t know how it was handled but the repos add the label hacktoberfest to their issues. The problem with our repo is, that we don’t show our issues, because it is in jira. I don’t know whether it is possible to sync issues from jira to GitHub, to Benefit from the hacktoberfest. Don’t know whether it is to late and to much effort, Maybe next year 😃. Cheers Chris --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
