diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 52d96c24e..ecce26ca3 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -16,26 +16,32 @@ labels: bug
 
 ---
 
-<!--- When filing a bug, please include the following headings if possible. Any example text in this template can be deleted. --->
+<!---
+When filing a bug, please include the following headings if possible.
+Any example text in this template can be deleted.
+--->
 
 ### Overview of the Issue
 
-<!--- Please describe the issue you are having and how you encountered the problem. --->
+<!---
+Please describe the issue you are having and how you encountered the problem.
+--->
+
 
 ### Reproduction Steps
 
 <!--- 
-
 In order to effectively and quickly resolve the issue, please provide exact steps that allow us the reproduce the problem. If no steps are provided, then it will likely take longer to get the issue resolved.
-  
 --->
 
+
 ### Logs
 
 <!---
-
 Provide log files from Atlantis server
 
+logs can be retrieved from the deployment or from atlantis comments by adding `--debug` such as `atlantis plan --debug`
+
 <details>
   <summary>Logs</summary>
 
@@ -44,29 +50,32 @@ log output
 ```
 
 </details>
-
 --->
 
+
 ### Environment details
 
 <!---
-
 If not already included, please provide the following:
+
 - Atlantis version:
+- Deployment method: ecs/eks/helm/tf module
 - If not running the latest Atlantis version have you tried to reproduce this issue on the latest version: 
 - Atlantis flags:
 
 Atlantis server-side config file:
-```
+
+```yaml
 # config file
 ```
 
 Repo `atlantis.yaml` file:
-```
+
+```yaml
 # config file
 ```
 
-Any other information you can provide about the environment/deployment.
+Any other information you can provide about the environment/deployment (efs/nfs, aws/gcp, k8s/fargate, etc)
 --->
 
 
@@ -74,4 +83,7 @@ Any other information you can provide about the environment/deployment.
 
 <!---
 Additional context on the problem. Docs, links to blogs, or other material that lead you to discover this issue or were helpful in troubleshooting the issue. 
+
+Use a bulleted list to link to tickets
 --->
+