Docsite: improve reporting_bugs_and_features.rst (#75234) (#75450)

* Docsite: improve reporting_bugs_and_features.rst

* Add clarification

(cherry picked from commit 61b81bcd10)

docs/docsite/rst/community/reporting_bugs_and_features.rst

@@ -37,12 +37,14 @@ If you find a bug, open the issue yourself to ensure we have a record of it. Do
   * Include output where possible
   * For multiple-file content, use gist.github.com, which is more durable than pastebin content
 
+.. _reporting_bugs_in_collections:
+
 Bugs in collections
 -------------------
 
 Many bugs only affect a single module or plugin. If you find a bug that affects a module or plugin hosted in a collection, file the bug in the repository of the :ref:`collection <collections>`:
 
-  #. Find the collection on Galaxy.
+  #. Find the collection on `Galaxy <https://galaxy.ansible.com>`_.
   #. Click on the Issue Tracker link for that collection.
   #. Follow the contributor guidelines or instructions in the collection repo.
 
@@ -54,3 +56,5 @@ Requesting a feature
 ====================
 
 The best way to get a feature into Ansible is to :ref:`submit a pull request <community_pull_requests>`, either against ansible-core or against a collection. See also :ref:`ansible_collection_merge_requirements`.
+
+You can also submit a feature request through opening an issue in the `ansible/ansible <https://github.com/ansible/ansible/issues>`_ for ``ansible-core`` or in a corresponding collection repository (refer to the :ref:`Bugs in collections<reporting_bugs_in_collections>` section to learn how to find a proper issue tracker).