Update policy

.github/DISCUSSION_TEMPLATE/bugs.yml

@@ -0,0 +1,60 @@
+title: "[Bug]"
+labels: []
+body:
+  - type: markdown
+    id: description
+    attributes:
+      label: Description
+      description: |
+        A clear and concise description of what the bug is.
+  - type: markdown
+    id: setup
+    attributes:
+      description: |
+        Relevant configs and/or SLS files (be sure to remove sensitive info.
+        There is no general set-up of Salt. Please be as specific as possible
+        and give set-up details.
+  - type: checkboxes
+    attributes:
+      label: Check all that apply
+      options:
+        - label: on-prem machine
+        - label: VM (Virtualbox, KVM, etc. please specify)
+        - label: VM running on a cloud service, please be explicit and add details
+        - label: container (Kubernetes, Docker, containerd, etc. please specify)
+        - label: or a combination, please be explicit
+        - label: jails if it is FreeBSD
+        - label: classic packaging
+        - label: onedir packaging
+        - label: used bootstrap to install
+  - type: markdown
+    id: steps
+    attributes:
+      label: Steps to reproduce the behavior
+      description: |
+         Steps to reproduce the behaviour. Include debug logs if possible and relevant
+  - type: markdown
+    id: expected
+    attributes:
+      label: Expected behavior.
+      description: A clear and concise description of what you expected to happen.
+  - type: markdown
+    id: screenshots
+    attributes:
+      label: Screenshots
+      descrption: If applicable, add screenshots to help explain your problem.
+  - type: markdown
+    id: versions
+    attributes:
+      label: Versions Report(s)
+      description: Versions reports for any affected components (master, minsions, ect).
+      value: |
+          `salt --versions-report`
+          ```yaml
+          PASTE HERE
+          ```
+  - type: markdown
+    id: additional-context
+    attributes:
+      label: Additional context
+      description: Add any other context about the problem here.

.github/DISCUSSION_TEMPLATE/features.yml

@@ -0,0 +1,24 @@
+title: "[Feature]"
+labels: [Feature]
+body:
+  - type: markdown
+    id: description
+    attributes:
+      label: Description
+      description: |
+        Describe the feature request and ny problems it should address.
+      value: |
+        **Is your feature request related to a problem? Please describe.**
+        A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+        **Describe the solution you'd like**
+        A clear and concise description of what you want to happen.
+
+        **Describe alternatives you've considered**
+        A clear and concise description of any alternative solutions or features you've considered.
+
+        **Additional context**
+        Add any other context or screenshots about the feature request here.
+
+        **Please Note**
+        If this feature request would be considered a substantial change or addition, this should go through a SEP process here https://github.com/saltstack/salt-enhancement-proposals, instead of a feature request.

POLICY.rst

@@ -10,9 +10,17 @@ Salt Project and to encourage more active engagement from the Salt community.
 * `Pull request management`_
 * `Salt Enhancement Proposals (SEP) process`_
 
-
 Issue management
 ================
+
+.. warning::
+   **Effective immidiatly.**
+
+   - All opened but un-assigned bugs will be migrated to discussions.
+   - All new bugs should be opened as a discussion.
+   - The only bugs and features that should have a corresponding issue are things that are assigned and actively being worked on.
+   - We are currently working on updating the triage process. This document will be updated as things progress.
+
 Issues for the Salt Project are critical to Salt community communication and to
 find and resolve issues in the Salt Project. As such, the issue tracker needs to
 be kept clean and current to the currently supported releases of Salt. They also