# No more Github issues?
**URL:** https://discuss.openedx.org/t/no-more-github-issues/871
**Category:** Community
**Created:** [November 19, 2019, 9:55am UTC](https://discuss.openedx.org/t/no-more-github-issues/871 "2019-11-19T09:55:53Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@regis](https://discuss.openedx.org/u/regis)
#### Post date: [November 19, 2019, 9:55am UTC](https://discuss.openedx.org/t/no-more-github-issues/871/1 "2019-11-19T09:55:53Z")
Howdy,
I just realized that issues were disabled in all github projects under the edx umbrella:
> **[edx/edx-platform](https://github.com/edx/edx-platform/pulls)**
>
> The Open edX platform, the software that powers edX! - edx/edx-platform
> **[edx/ecommerce](https://github.com/edx/ecommerce/pulls)**
>
> Service for managing edX's product catalog and handling orders for those products - edx/ecommerce
> **[edx/edx-ora2](https://github.com/edx/edx-ora2/pulls)**
>
> Open Response Assessment Suite. Contribute to edx/edx-ora2 development by creating an account on GitHub.
When was this change made? My opinion is that this is really unfortunate. The suppression of issues means that there are many links which are now broken. For instance, all issue numbers referenced in pull requests are now lost. These issues provided a lot of interesting context. Also, they were useful for SEO purposes: people facing an issue could google it and find the corresponding conversation. And what about issues that were previously open? Were they simply closed in the process?
I assume this change was made because edX uses Jira exclusively, internally. I’ll be blunt: Jira is a terrible tool that is very difficult to use for the community. It is difficult to search, requires authentication, it is not indexed by search engines and it does not integrate well with Github (at least for community users).
Is this change permanent? If yes, was there a discussion with the community about it? Can we come back on this decision?
---
### Author:  [@nedbat](https://discuss.openedx.org/u/nedbat)
#### Post date: [November 19, 2019, 11:53am UTC](https://discuss.openedx.org/t/no-more-github-issues/871/2 "2019-11-19T11:53:59Z")
GitHub issues are great for lightly managed single-repo projects. That does not describe Open edX work. JIRA is overly complex and confusing to use, but on the plus side it lets us do things we need to do: richer categorization, sprint orchestration, transfer issues between teams, work on issues that span repos, report on the flow of work, and so on.
I didn’t realize that disabling the issues would make existing issues unavailable. Was there much being recorded in GitHub issues?
We should talk about the specific speed bumps caused by JIRA, and see what we can do to smooth them out.
---
### Author:  [@regis](https://discuss.openedx.org/u/regis)
#### Post date: [November 19, 2019, 12:29pm UTC](https://discuss.openedx.org/t/no-more-github-issues/871/3 "2019-11-19T12:29:58Z")
> [@nedbat](#):
>
> Was there much being recorded in GitHub issues?
I can’t tell exactly, as I cannot access issues anymore 😓 But as far as I was concerned, yes, I frequently referenced github issues in commits, forum posts and documentation entries.
To be clear: this is not a question of whether I like Jira or not. I’m not trying to compare Github issues vs Jira. My personal impression is that Jira raises the bar even higher for contributing to Open edX, a project where the bar for contributing is already high enough. However, there is no way for me to assess whether this feeling reflects the reality because we won’t see contributions from people who shied away from Jira.
Anyway, let’s keep this debate for later. Right now, I’m concerned by the following points, which I think are **extremely problematic** :
1. Content that previously was in Github issues has now disappeared.
2. Issues that were previously open on Github are now closed (I assume?).
Is there any way at all these issues can be addressed?
---
### Author:  [@nedbat](https://discuss.openedx.org/u/nedbat)
#### Post date: [November 19, 2019, 12:31pm UTC](https://discuss.openedx.org/t/no-more-github-issues/871/4 "2019-11-19T12:31:56Z")
I’ll have to investigate what the options are for seeing GitHub issues that are now no longer visible. Just to make things super-concrete, do you have a link to a particular issue?
---
### Author:  [@regis](https://discuss.openedx.org/u/regis)
#### Post date: [November 19, 2019, 12:34pm UTC](https://discuss.openedx.org/t/no-more-github-issues/871/5 "2019-11-19T12:34:44Z")
> [@nedbat](#):
>
> do you have a link to a particular issue?
Yes, I discovered that issues had disappeared when I jumped back to an older PR:
>
>
> \`reverse\_lazy\` object cannot be dumped by \`json.dumps\`, which results in
> TypeEr…ror when attempting to convert the xblock response to json.
>
> Close #1139.
["TypeError: u'\' is not JSON serializable" on upload to backends other than S3 · Issue #1139 · openedx/edx-ora2 · GitHub](https://github.com/edx/edx-ora2/issues/1139) (this is now a 404)
---
### Author:  [@nedbat](https://discuss.openedx.org/u/nedbat)
#### Post date: [November 19, 2019, 12:51pm UTC](https://discuss.openedx.org/t/no-more-github-issues/871/6 "2019-11-19T12:51:24Z")
I can confirm the issues are still there (re-enabling issues in that repo makes the link work, and other old issues are still present).
---
### Author:  [@regis](https://discuss.openedx.org/u/regis)
#### Post date: [November 19, 2019, 12:59pm UTC](https://discuss.openedx.org/t/no-more-github-issues/871/7 "2019-11-19T12:59:11Z")
Ok so if you give me admin rights on that repo I’ll enable issues when I need them.
😝
---
### Author:  [@nedbat](https://discuss.openedx.org/u/nedbat)
#### Post date: [November 19, 2019, 7:38pm UTC](https://discuss.openedx.org/t/no-more-github-issues/871/8 "2019-11-19T19:38:42Z")
Perhaps we can re-enable issues, but write a big scary issue template that encourages people to go elsewhere?