Turn off Discussions (again)

[chadwhitacre]

In #1151 we deprecated the Discourse forum in favor of GitHub Issues. In https://github.com/getsentry/self-hosted/discussions/1468 we turned on Discussions after all to match what the rest of the org seems to prefer. I now regret that decision, as our support flow is more or less wrecked at this point. I want to go back to Issues-only.

[chadwhitacre]

Okay how are we going to do this?

[chadwhitacre]

It looks like there's no way to unconvert an issue ... i.e., reopen an issue that has been converted to a discussion. I'm not seeing UI on e.g. #1483. 🤔

[chadwhitacre]

Discussions have UI to open a new issue based on the discussion, so I guess that's our option? Reopen issues (they'll be under my name, boo) for all support requests currently in discussions, then delete/turn off the discussions.

[aminvakil]

I tried "Create issue from discussion button" in #1502 and it didn't do anything.

I thought they will do something, but AFAICS it doesn't. (I mean what's the difference between this and opening an issue manually then?)

[chadwhitacre]

Really? Could be a permissions issue but if so that seems like a bug (why show you the button if clicking it doesn't do anything?). When I click "Create issue from discussion" on (e.g.) #1483 I get a prepopulated issue form like this:

No comments are brought over, that's probably worth doing manually.

[chadwhitacre]

What do you get when you go directly here?

https://github.com/getsentry/self-hosted/issues/new?created_from_discussion_number=1496

[aminvakil]

What do you get when you go directly here?

https://github.com/getsentry/self-hosted/issues/new?created_from_discussion_number=1496

[chadwhitacre]

Interesting. Yet another reason to not use Discussions, if triage role can't convert discussions to issues. :-/

[chadwhitacre]

Aiming to power through this today. My plan is to work through old discussions and hard-delete them all and then turn off Discussions. For each discussion before deleting I'll convert to an issue. For the old support requests that I converted to discussions I'll link to the old support request issue.

[chadwhitacre]

Nevermind! It looks like I can simply unlock an issue to bring it back from the "converted to discussion" state. 💃

e.g. #1414

[chadwhitacre]

Okay! Learning more: the ability to unlock an issue to bring it back is only available if Discussions is disabled for the repo. Makes sense. 👍

[chadwhitacre]

Here they are, the issues I've reopened from Discussions:

• Alerts not being sent to Pagerduty #1286
• Cannot get backup and restore to work #1322
• Unable to upload source maps #1326
• Kafka Consumer Groups consuming excessive amounts of memory #1394
• Missing support for URL sub paths like https://example.com/sentry-subpath #1396
• Upgrading from 21.6.3 to latest nightly build removes events/issues from the UI #1401
• Cannot unsubscribe from notifications #1406
• Support connecting multiple Slack workspaces #1414
• Deleted data still shows in the UI #1419
• CPU usage peaks #1420
• How can I run the service in an intranet environment without Internet connect？ #1433
• Jira integration issue #1434
• Alert Rules don't seem to fire on new issues, despite an alert being set #1435
• Install.sh error: Error response from daemon: start failed: : fork/exec /usr/bin/containerd-shim-runc-v2: resource temporarily unavailable: unknown #1438
• Not match condition why trigger webhook #1440
• Unable to see uploaded source maps #1441
• 400: Please fill out the access category and reason correctly #1442
• No ulimits for various components #1445
• snuba-subscription-consumer-events: KeyError: 'query' #1472
• ERROR: for web Container "500ce61a98b7" is unhealthy #1483
• Can't setup 2FA (TOTP) on Sentry on-premise #1484
• Large increase in RAM usage from 21.12.0 to 22.4.0 #1491
• geoip keeps restarting #1493

I'm going through these one-by-one and bringing over any additional comments from the discussion to the issue before deleting the discussion.

[chadwhitacre]

Done! I manually copied over comments from Discussions to the issues (required toggling Discussions on and off as I could only edit one version at a time 🙄) and I created new issues for some new discussions:

• error for getsentry/snuba:nightly and maxmindinc/geoipupdate:v4.7.1 image #1523
• Sentry 21.02 on premise login problems #1525
• Self-hosted sentry doesn't get test event from sentry-cli #1526
• Best HA solution in AWS #1527

[chadwhitacre]

I also took a pass through the issues in #1499 (comment) and reopened just the ones that seemed to be still viable. Calling this good there. 👍