Add issue reporting

profile/README.md

@@ -11,10 +11,11 @@ You can get involved in the [Puppet community](https://puppet.com/community/) by
 
 - 💬 https://slack.puppet.com
 - 🎫 https://tickets.puppet.com
-- 🎩 https://forge.puppet.com
+- 🛠️ https://forge.puppet.com
 - 🦊 https://voxpupuli.org
 - 🎙 https://dev.to/puppet
 - 🐘 https://fosstodon.org/@puppet
+- 👩‍💻 https://github.com/puppetlabs/community/discussions
 
 Don't forget that all participation is governed by our [Code of conduct](https://pup.pt/conduct).
 
@@ -24,6 +25,21 @@ Community contributions are awesome and part of the way that we make sure that o
 
 Most of our projects will use our standard [contribution guidelines](https://github.com/puppetlabs/.github/blob/main/CONTRIBUTING.md), but you should check individual repositories for a more specific guide before submitting a PR.
 
+### 🎟️ Reporting issues
+
+We have moved exclusively to GitHub Issues for reporting problems with any of our products. For open source products, you'll simply use their corresponding repositories. Some of the most common ones:
+  * [Puppet](https://github.com/puppetlabs/puppet)
+  * [Bolt](https://github.com/puppetlabs/bolt)
+  * [Facter](https://github.com/puppetlabs/facter)
+  * [PuppetDB](https://github.com/puppetlabs/puppetdb)
+  * [Puppet Server](https://github.com/puppetlabs/puppetserver)
+  * [Puppet Modules](https://github.com/search?q=topic%3Amodule+org%3Apuppetlabs+fork%3Atrue&type=Repositories) (take note of the support status)
+
+Some products, like Puppet Enterprise itself, are developed internally. These now have corresponding GitHub repositories that are currently only used for issue reporting.
+  * [Puppet Forge](https://github.com/puppetlabs/forge_issues)
+  * [Puppet Enterprise](https://github.com/puppetlabs/puppet-enterprise_issues)
+  * [CEM Modules](https://github.com/puppetlabs/cem_issues)
+
 ### 💻 Wanna come work with us?
 
 Check out our 📜 [job listings](https://www.perforce.com/careers) and see what strikes your fancy.