Re: GitHub Issues

Thanks Am 13.03.2024 um 09:54 schrieb 'Daniel Beck' via Jenkins Developers: On Wed, Mar 13, 2024 at 9:08 AM 'Michael Kriese' via Jenkins Developers wrote: Found it. - https://maven.apache.org/pom.html#issue-management - https://github.com/jenkinsci/publish-over-ssh-plugin

Re: GitHub Issues

On Wed, Mar 13, 2024 at 9:08 AM 'Michael Kriese' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Found it. > > - https://maven.apache.org/pom.html#issue-management > - > https://github.com/jenkinsci/publish-over-ssh-plugin/blob/d6d29fda86b3db5e19d9130ca80ad7915eb1197c/pom.xml#L12

Re: GitHub Issues

Found it. - https://maven.apache.org/pom.html#issue-management - https://github.com/jenkinsci/publish-over-ssh-plugin/blob/d6d29fda86b3db5e19d9130ca80ad7915eb1197c/pom.xml#L122 Michael Kriese schrieb am Mittwoch, 13. März 2024 um 09:00:29 UTC+1: > Hi, > > Is there a way to only use GitHub issue

Re: GitHub issues option in HOSTING

> On 21. Feb 2021, at 16:50, Radek Antoniuk wrote: > > > Let me know if I missed something but for me this process looks exactly the > same when we replace Jira with GH Security Advisories system described > above. > The only thing I see missing here is probably the possibility for non-write

Re: GitHub issues option in HOSTING

>> Regarding Security issues - maybe GH new Security Advisories hub could be used for that? >> https://help.github.com/en/github/managing-security-vulnerabilities/about-github-security-advisories >> https://github.blog/2020-05-26-giving-credit-for-security-advisories/ > Our usual workflow is docum

Re: GitHub issues option in HOSTING

> On 15. Feb 2021, at 20:32, Radek Antoniuk wrote: > > Regarding Security issues - maybe GH new Security Advisories hub could be > used for that? > https://help.github.com/en/github/managing-security-vulnerabilities/about-github-security-advisories > https://github.blog/2020-05-26-giving-cred

Re: GitHub issues option in HOSTING

Resurrecting via PR: https://github.com/jenkinsci/.github/pull/42/files - let's discuss this there. Regarding Security issues - maybe GH new Security Advisories hub could be used for that? https://help.github.com/en/github/managing-security-vulnerabilities/about-github-security-advisories https://

Re: GitHub issues option in HOSTING

I know there's no consensus in this yet, it should get added to governance i think, but I'm fixing github issue ids in release notes https://github.com/jenkins-infra/plugin-site-api/pull/92 On Wed, Jun 24, 2020 at 8:59 AM Tim Jacomb wrote: > > > On Wed, 24 Jun 2020 at 16:17, Radosław Antoniuk

Re: GitHub issues option in HOSTING

On Wed, 24 Jun 2020 at 16:17, Radosław Antoniuk wrote: > > Since now we know we have the GH issues templates... what do you think > about creating a central (i.e. pre-defined and shared across all plugins), > how about: > - creating a unified GH issue template for the whole jenkinsci > organisati

Re: GitHub issues option in HOSTING

Since now we know we have the GH issues templates... what do you think about creating a central (i.e. pre-defined and shared across all plugins), how about: - creating a unified GH issue template for the whole jenkinsci organisation (i.e. pre-defined template) - push this template via PR to all the

Re: GitHub issues option in HOSTING

Hi, I think this mail discussion is a proof that we won't easily find a consensus any time soon. I just want to add that we started discussing with Linux foundation infra team to see if they could maintained a managed version of Jira for us, more information in this email

Re: GitHub issues option in HOSTING

On Fri, Jun 19, 2020 at 12:30 PM Tim Jacomb wrote: > On Fri, 19 Jun 2020 at 10:36, Daniel Beck wrote: > >> Having a screen like >> https://github.com/jenkinsci/configuration-as-code-plugin/issues/new/choose >> could help here, but that's far from universal right now. Is this something >> that co

Re: GitHub issues option in HOSTING

On Fri, 19 Jun 2020 at 10:36, Daniel Beck wrote: > Having a screen like > https://github.com/jenkinsci/configuration-as-code-plugin/issues/new/choose > could help here, but that's far from universal right now. Is this something > that could be defined via .github? Having a screen similar to this

Re: GitHub issues option in HOSTING

> On 19. Jun 2020, at 11:47, Radosław Antoniuk wrote: > >> I would be surprised if we wouldn't regularly get 0-days because people with >> just a GH account don't bother to do it properly, and just report issues on >> GH. If that is enabled in repos without someone regularly reviewing incomi

Re: GitHub issues option in HOSTING

> > I would be surprised if we wouldn't regularly get 0-days because people > with just a GH account don't bother to do it properly, and just report > issues on GH. If that is enabled in repos without someone regularly > reviewing incoming issues, or by a maintainer who's unaware of how we > handle

Re: GitHub issues option in HOSTING

> On 18. Jun 2020, at 22:50, Tim Jacomb wrote: > > The security team already uses a different project in Jira to everyone else, > I don't think we need to change that currently, maintainers will just use > whatever the security team decides I would think? > > Mentioned this earlier: > > One

Re: GitHub issues option in HOSTING

To add to Jesse's numbers here's a summary for the JenkinsCI organisation: Org report: jenkinsci Total repositories: 2290 Number with GitHub issues enabled: 355 (15%) Total issues open: 3338 Total issues closed: 17941 Total issues: 21279 https://gist.github.com/timja/a939f198752b218c3270ac043eb08

Re: GitHub issues option in HOSTING

On Thu, 18 Jun 2020 at 21:44, James Nord wrote: > > am I missing something in this thread > > security reports? > > currently they are all triaged by the security team so the team can track > disclosure deadlines etc. > how would that worknif the plugin is usimg GH issues? (yes I know gh > issues

Re: GitHub issues option in HOSTING

> am I missing something in this thread security reports? currently they are all triaged by the security team so the team can track disclosure deadlines etc. how would that worknif the plugin is usimg GH issues? (yes I know gh issues can now handle security reports but does that mean the secu

Re: GitHub issues option in HOSTING

Agreed, I think we need to have this as a topic in that meeting. I think there are two parts of this topic: 1. Do we want to allow both Jira and Github issues to coexist in the Jenkins infrastructure? 1. This is _somewhat_ moot at this point because we already have a large numbe

Re: GitHub issues option in HOSTING

> Am 18.06.2020 um 19:48 schrieb 'Gavin Mogan' via Jenkins Developers > : > > > Puh, that is a lot. That means we already cerated a mess for our users by > > providing two different tools for the same thing :-( > > Which is why I want to know what and how we want to support things officiall

Re: GitHub issues option in HOSTING

> Puh, that is a lot. That means we already cerated a mess for our users by providing two different tools for the same thing :-( Which is why I want to know what and how we want to support things officially so I can add it to the plugin site. > The superiority of Jira in terms of features is obvi

Re: GitHub issues option in HOSTING

Puh, that is a lot. That means we already cerated a mess for our users by providing two different tools for the same thing :-( > Am 18.06.2020 um 19:36 schrieb Jesse Glick : > > stashnotifier-plugin -- You received this message because you are subscribed to the Google Groups "Jenkins Develop

Re: GitHub issues option in HOSTING

On Thu, Jun 18, 2020 at 12:51 PM Ullrich Hafner wrote: >> we are already past that point as the plugins are already mixed up between >> Jira and GH. > > I don’t think that we are past the point yet, just because a couple of > plugins managed it to enable GitHub issues. jshell> for (GHRepository

Re: GitHub issues option in HOSTING

> > > > > About consistency, I fully agree, but we are already past that point as > the plugins are already mixed up between Jira and GH. > > I don’t think that we are past the point yet, just because a couple of > plugins managed it to enable GitHub issues. From my understanding the > hosting proc

Re: GitHub issues option in HOSTING

> Am 18.06.2020 um 18:00 schrieb Radosław Antoniuk : > > The superiority of Jira in terms of features is obvious but it shouldn't be > an argument. Why not? > Most of the projects do not use Sprint Boards etc. and I still think that we > should aim to be as close/easy for the contributor/r

Re: GitHub issues option in HOSTING

Hi Radek Jira cloud isn’t an option due to our number of users and a couple of other reasons (there’s a ticket with a summary somewhere in jira) Linux foundation have offered to host jira though which may at least get us one we don’t have to maintain. Fully agree with your other points Maybe we

Re: GitHub issues option in HOSTING

On Fri, Jun 12, 2020 at 6:07 AM Dominik Bartholdi wrote: > I fully agrees with Uli and James… the main reason for me is the > searchability of the issue IDs. Many many times I have the JIRA Issue ID > (e.g. in commits) and then a simple Google search brings up the exact issue > - with GH-Issues,

Re: GitHub issues option in HOSTING

I fully agrees with Uli and James… the main reason for me is the searchability of the issue IDs. Many many times I have the JIRA Issue ID (e.g. in commits) and then a simple Google search brings up the exact issue - with GH-Issues, this gets lost all the way :( /Domi > On 11 Jun 2020, at 19:25,

Re: GitHub issues option in HOSTING

According to https://issues.jenkins-ci.org/browse/INFRA-2010?jql=text%20~%20%22jira%22%20and%20text%20~%20%22ldap%22%20and%20text%20~%20%22cloud%22 there's also an issue that you can't import only 5k users total, and we have more than 100k users. https://confluence.atlassian.com/cloud/saml-single-

Re: GitHub issues option in HOSTING

The issue with the cloud version is that it is not compatible with our LDAP (at least that is what I believe Olivier said last time). On Thu, Jun 11, 2020 at 2:28 PM James Nord wrote: > I agree with Ulli's statements. > > There seems to be comments that our hosted Jira is sluggish or hard to > m

Re: GitHub issues option in HOSTING

I agree with Ulli's statements. There seems to be comments that our hosted Jira is sluggish or hard to maintain. I've asked before but why can,t the cloud version be an option? we should be able to spin up a stateless SAML to LDAP integration for Jira Cloud with much less effort than continuing

Re: GitHub issues option in HOSTING

I prefer Jira, from a developer and a user perspective: Developer perspective: - Having the ability to move issues from one component to another is very helpful for me. I don’t see how to do this in GitHub. My plugin uses different components and I want to easily move issues from one component t

Re: GitHub issues option in HOSTING

On Thu, Jun 11, 2020 at 11:26 AM Jeff Thompson wrote: > Jenkins is a system of interacting components and issues may involve multiple. Every time I have worked with a Jira issue with multiple components, I have wound up regretting the resulting confusion. It gets marked fixed by one person due to

Re: GitHub issues option in HOSTING

On 6/11/20 8:32 AM, Slide wrote: The big problem with GitHub issues is when a bug involves multiple components, or is filed against the wrong component. If you filed an issue in the wrong component, what would you expect the maintainers of that component to do? I don't think it should be on the

Re: GitHub issues option in HOSTING

Wouldn't you either transfer it or ask them to re-file with the correct component? Same as with Jira? I doubt issues filed with the wrong component in Jira are ever seen by the right people either. Thanks Tim On Thu, 11 Jun 2020 at 15:33, Slide wrote: > The big problem with GitHub issues is wh

Re: GitHub issues option in HOSTING

The big problem with GitHub issues is when a bug involves multiple components, or is filed against the wrong component. If you filed an issue in the wrong component, what would you expect the maintainers of that component to do? I don't think it should be on them to find the right component, so the

Re: GitHub issues option in HOSTING

I agree. I'd love to see Jenkins migrate from Jira to GH. As a user, if I want to submit an issue to Jenkins, it's a bit cumbersome to create an additional account for Atlassian just so that I can create a ticket. However, it's highly likely that I already have a GH account and have even browsed

Re: GitHub issues option in HOSTING

personally, as someone who replies to emails/tickets on my phone a lot, I'd love to see everything migrated from self hosted jira to github, and have one less item that the infra team needs to manage. Plus easier for people to report bugs since they don't need to make an ldap account first On Wed,

Re: GitHub issues option in HOSTING

> > Am 10.06.2020 um 11:47 schrieb Radosław Antoniuk >: > > Not sure I got the question right, but IMO it's each plugin's maintainer > responsibility to transfer the issues from Jira to GH (with a pre-prepared > solution I mentioned long ago). > > > I think we are still one step before: should we

Re: GitHub issues option in HOSTING

> Am 10.06.2020 um 11:47 schrieb Radosław Antoniuk : > > Not sure I got the question right, but IMO it's each plugin's maintainer > responsibility to transfer the issues from Jira to GH (with a pre-prepared > solution I mentioned long ago). I think we are still one step before: should we as pr

Re: GitHub issues option in HOSTING

On Wed, Jun 10, 2020 at 3:46 PM Slide wrote: > We could remove the component from Kira for the plugin. It wouldn't stop > someone from opening one and assigning it to the wrong component, but > people assign to the wrong component all the time anyway. > Yes, removing the category is the other op

Re: GitHub issues option in HOSTING

We could remove the component from Kira for the plugin. It wouldn't stop someone from opening one and assigning it to the wrong component, but people assign to the wrong component all the time anyway. On Wed, Jun 10, 2020, 02:47 Radosław Antoniuk wrote: > Not sure I got the question right, but I

Re: GitHub issues option in HOSTING

Not sure I got the question right, but IMO it's each plugin's maintainer responsibility to transfer the issues from Jira to GH (with a pre-prepared solution I mentioned long ago). The question is how to prevent opening new issues in Jira afterwards, but this actually could be automated via a simple

Re: GitHub issues option in HOSTING

Yea I want to get the discussion restarted so a conclusion can happen. And no, was just thinking of transferring tickets between plugins that do GitHub issues. And the triaging issues within, but yea that's another issue with the mixed env On Wed., Jun. 10, 2020, 1:14 a.m. Ullrich Hafner, wrote:

Re: GitHub issues option in HOSTING

> Am 10.06.2020 um 01:24 schrieb 'Gavin Mogan' via Jenkins Developers > : > > So re surfacing this old topic now that we've merged and deployed the updated > plugin site with GitHub releases and jira issues > Seems that I overlooked the PR for the new plugins site. Nice work, thanks for tha

Re: GitHub issues option in HOSTING

So re surfacing this old topic now that we've merged and deployed the updated plugin site with GitHub releases and jira issues My next steps is start supporting GitHub issues for plugins that uses them. But this topic never came to a conclusion. If we are officially supporting GitHub issues, then

Re: GitHub issues option in HOSTING

I used this one: https://github.com/warden/jira-issues-importer -- 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-dev+unsubscr...@googlegroups.com.

Re: GitHub issues option in HOSTING

That's cool Radek, was this what you used to migrate them? https://github.com/parcelLab/jira-to-github Or something else? On Wed, 25 Mar 2020 at 16:27, Radek Antoniuk wrote: > I would like to vote +1 for GitHub Issues. > > I tried migration via the API for jira plugin and the only thing that we

Re: GitHub issues option in HOSTING

I would like to vote +1 for GitHub Issues. I tried migration via the API for jira plugin and the only thing that we would lose is the original reporter (it would be noted in the comment but not the issue creator) - I think that this can be lived with. See https://github.com/warden/jira-plugin/i

Re: GitHub issues option in HOSTING

On Fri, Feb 14, 2020 at 4:59 PM Jesse Glick wrote: > > Right. It would be great to switch to GitHub SSO, avoiding the > confusion between oleg-nenashev vs. oleg_nenashev and so on, and > ending a bunch of issues such as old email aliases. JIRA and > Artifactory would need to support this connecto

Re: GitHub issues option in HOSTING

Since the thread is indeed pretty well derailed by now, On Fri, Feb 14, 2020 at 9:17 AM Daniel Beck wrote: > The major obstacle as I see it is the mapping of users. This applies to every > alternative not backed by our LDAP. Right. It would be great to switch to GitHub SSO, avoiding the confusi

Re: GitHub issues option in HOSTING

> On 11. Feb 2020, at 08:11, Tim Jacomb wrote: > > I feel like we can work something out for the security project, possibly > there’s a better tool for it... > > I don’t think it’ll work easily in the cloud version either Since it seems like we've managed to finally really derail this threa

Re: GitHub issues option in HOSTING

I am happy that we start this discussion early enough before the current Jira version becomes at the end of life. It's a topic important enough to have as much feedback as possible but also whatever we decide we won't have support from 100% of the contributors otherwise we wouldn't have this lon

Re: GitHub issues option in HOSTING

I feel like we can work something out for the security project, possibly there’s a better tool for it... I don’t think it’ll work easily in the cloud version either For transferring you need at least write and possibly admin on both ends to use the GitHub ui for it, but there’s a GitHub app for i

Re: GitHub issues option in HOSTING

I'll freely admit I dislike jira, but I think the mix for plugins of using jira and github are very confusing. I see a major issue, that security issues can't really work in github, since they can't be made private for certain people, which means if you'd have issues for a plugin in both github an

Re: GitHub issues option in HOSTING

> On 2. Feb 2020, at 12:13, Tim Jacomb wrote: > > GitHub issues use is growing in the ecosystem, many plugins are now using it, Given the discussion, I now seriously doubt that this would be beneficial over the long-term to the project. Not because the proposal is a bad idea on its own (it'

Re: GitHub issues option in HOSTING

Who is going to update it? And what benefit does that bring? And moving to the cloud version brings less features, a new account type everyone has to sign up to, but less maintenance On Mon, 10 Feb 2020 at 10:28, Ullrich Hafner wrote: > Ok, then let us summarize the side track: > We cannot and

Re: GitHub issues option in HOSTING

Ok, then let us summarize the side track: We cannot and do not want to drop Jira because it is used in a lot of places and the features are superior to GitHub issues. We can improve performance and usability of Jira if we would deploy a more recent version of Jira (or use the cloud version). Th

Re: GitHub issues option in HOSTING

> What other services are using our LDAP? They are so many places where we use ldap that we won't get rid of it easily, especially in the infra part, and I am really not concerned about it, as it's really easy to maintain --- gpg --keyserver keys.gnupg.net --recv-key 52210D3D --- On Mon, Feb 1

Re: GitHub issues option in HOSTING

> On 10. Feb 2020, at 10:08, Ullrich Hafner wrote: > > What other services are using our LDAP? Account app (duh), Wiki (sort of going away very slowly), all our Jenkins instances (ci, trusted.ci, and cert.ci), and Artifactory (this is why you use your Jenkins user name in https://github.co

Re: GitHub issues option in HOSTING

> On 10. Feb 2020, at 09:50, Olblak wrote: > > The second element, excepted Tyler and me, nobody "maintains" it and > unfortunately, we can only accept trusted people to work on > issues.jenkins-ci.org as it contains the security work. Any option that removes issues.j.o entirely will need t

Re: GitHub issues option in HOSTING

> Am 10.02.2020 um 09:50 schrieb Olblak : > > Let's bring back the infrastructure point of view into the discussion > > Jira to Jira Cloud INFRA-2010 > > If someone is willing to do more experimentation with it, be my guest but for > what I un

Re: GitHub issues option in HOSTING

Let's bring back the infrastructure point of view into the discussion Jira to Jira Cloud INFRA-2010 If someone is willing to do more experimentation with it, be my guest but for what I understand contributors require an Atlassian account to connec

Re: GitHub issues option in HOSTING

> On 9. Feb 2020, at 00:53, Chris Kilding > wrote: > > there seems to be common ground on solving the *access* problem for users > that report issues. > > If we can get a GitHub connector up and running for Jira, so that any user > who wants to report an issue can simply sign in with the G

Re: GitHub issues option in HOSTING

As far as I know for jira cloud the only log in options are atlassian account or SAML (may be premium option, can’t find docs for it) For server there’s this paid add on: https://marketplace.atlassian.com/apps/1217688/oauth-openid-connect-oidc-for-jira-sso?hosting=server&tab=overview but nothing f

Re: GitHub issues option in HOSTING

While there are differences of opinion on the issue *storage* problem (ie do we store our issues in Jira or GitHub), there seems to be common ground on solving the *access* problem for users that report issues. If we can get a GitHub connector up and running for Jira, so that any user who wants

Re: GitHub issues option in HOSTING

On Sat, Feb 8, 2020 at 2:46 PM Tim Jacomb wrote: > (replies inline) > On Sat, 8 Feb 2020 at 12:13, Daniel Beck wrote: > >> >> On Fri, Feb 7, 2020 at 7:31 PM 'Gavin Mogan' via Jenkins Developers < >> jenkinsci-dev@googlegroups.com> wrote: >> >>> I also really want to see issues.jenkins go away, b

Re: GitHub issues option in HOSTING

(replies inline) On Sat, 8 Feb 2020 at 12:13, Daniel Beck wrote: > > On Fri, Feb 7, 2020 at 7:31 PM 'Gavin Mogan' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> wrote: > >> I also really want to see issues.jenkins go away, but mostly due to how >> slow it is. I don't think cloud is a

Re: GitHub issues option in HOSTING

On Fri, Feb 7, 2020 at 7:31 PM 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > I also really want to see issues.jenkins go away, but mostly due to how > slow it is. I don't think cloud is a lot better, but way less maintenance > for people. > When was the last time

Re: GitHub issues option in HOSTING

Oh cool, I didn't know about that feature. On Fri, Feb 7, 2020 at 5:35 PM James Nord wrote: > >With jira, I'm either auto assigned the issue due to whatever component > was first picked, or nothing at all. Groups of maintainers can't be > notified. Un-assigned tickets don't get notified > > crea

Re: GitHub issues option in HOSTING

>With jira, I'm either auto assigned the issue due to whatever component was >first picked, or nothing at all. Groups of maintainers can't be notified. >Un-assigned tickets don't get notified create a filter that matches things you want to be notified for. subscribe to that filter in https://is

Re: GitHub issues option in HOSTING

I also really want to see issues.jenkins go away, but mostly due to how slow it is. I don't think cloud is a lot better, but way less maintenance for people. I think the big push in the past for jira was because you couldn't migrate issues between repos before in github. That got changed.. though

Re: GitHub issues option in HOSTING

> On 7. Feb 2020, at 15:56, James Nord wrote: > > it kills me every time I need to file an issue and try and work out where it > is to be reported and I consider myself knowledgeable about Jenkins and it's > plugins. I mentioned it in a previous response, but here's the link: https://git

Re: GitHub issues option in HOSTING

> On 2. Feb 2020, at 12:13, Tim Jacomb wrote: > > • Much easier to be a co-maintainer, with JIRA only the ‘component > lead’ gets notified by default, you _can_ create your own filters and > subscriptions, but it’s a lot more effort and most people (including me) > don’t do that. At

Re: GitHub issues option in HOSTING

Technically we could migrate all issues to github, at least I saw some python scripts doing that. I would be more concerned by the security issues, so indeed we could also have both tools in place where most of the things are on github issues --- gpg --keyserver keys.gnupg.net --recv-key 52210

Re: GitHub issues option in HOSTING

I generally agree with Ulli's comments. so far we are all talking about the developer experience when interacting with issues. we need to also think of the user experience to Jenkins users too. it kills me every time I need to file an issue and try and work out where it is to be reported and

Re: GitHub issues option in HOSTING

For maintaining history, I've done something similar in the past when migrating a project from codeplex to GitHub. The script I had migrated the comments and the attachments as best it could. I could try a proof of concept of people are interested. On Fri, Feb 7, 2020, 07:06 Jesse Glick wrote: >

Re: GitHub issues option in HOSTING

On Fri, Feb 7, 2020 at 8:50 AM Olblak wrote: > We migrate from Jira to Jira Cloud > We migrate from Jira to Github Issues Can we migrate to Jira Cloud with history intact, _and_ encourage use of GitHub issues for new components? -- You received this message because you are subscribed to the Goo

Re: GitHub issues option in HOSTING

Maintaining issues.jenkins-ci.org is time-consuming, and it's hard to find someone who wants to do it. While I totally agree that we shouldn't use multiple ticket system, I don't see real good solution he re We migrate from Jira to Jira Cloud -> We keep the history -> No maintenance -> We can on

Re: GitHub issues option in HOSTING

Any other opinions? So far we have 3 +1, and 1 -1 This isn't asking that we move everything over, but make it easier for new plugin maintainers to use GitHub issues. Thanks Tim On Mon, 3 Feb 2020 at 13:06, Chris Kilding wrote: > I'm inclined to agree with Joseph and Tim. > > When maintaining

Re: GitHub issues option in HOSTING

I'm inclined to agree with Joseph and Tim. When maintaining my plugin I often wonder how many bug reports I'm losing because users either: - Can't find their way through our bug tracking system (and all the labels and categories that a bug must be annotated with), compared to GH Issues which i

Re: GitHub issues option in HOSTING

As a maintainer I find it very difficult that I have to use Jira for inter project work. - Question what username you have on Jira not always the same - find Jira searching very bothersome compared to some of the logical either code searches or be it issue searches. - Tim and I have been very

Re: GitHub issues option in HOSTING

I don’t think that this is a good idea to support two different issue tracker landing pages. As we encourage every body to host everything in *one* location (i.e., GitHub) we should also enforce (well at least work towards) a unique landing page for issues from our users. Otherwise users are con