Updating the issue template (microsoft#779)

issue_template.md

@@ -1,23 +1,27 @@
-## Driver version or jar name
-Please tell us what the JDBC driver version or jar name is.
-
-## SQL Server version
-Please tell us what the SQL Server version is.
-
-## Client operating system
-Please tell us what oprating system the client program is running on.
-
-## Java/JVM version
-Example: java version "1.8.0", IBM J9 VM
-
-## Table schema
-Please tell us the table schema
-
-## Problem description
-Please share more details with us.
-
-## Expected behavior and actual behavior
-Please tell us what should happen and what happened instead
-
-## Repro code
-Please share repro code with us, or tell us how to reproduce the issue.
+## Driver version
+<!--- Provide the JDBC driver version (e.g. 7.0.0). -->
+
+## SQL Server version
+<!--- Provide the output of executing `SELECT @@VERSION` on your target SQL Server. -->
+
+## Client Operating System
+<!--- Provide the Operating System the client application is running on. -->
+
+## JAVA/JVM version
+<!--- Provide the JAVA/JVM version (e.g. java version "1.8.0", IBM J9 VM). -->
+
+## Table schema
+<!--- Provide the table schema. -->
+
+## Problem description
+<!--- Provide full details of the problem. -->
+1. Expected behaviour:
+2. Actual behaviour:
+3. Error message/stack trace:
+4. Any other details that can be helpful:
+
+## JDBC trace logs
+<!--- Provide the JDBC trace logs. Instructions can be found here: https://docs.microsoft.com/en-us/sql/connect/jdbc/tracing-driver-operation?view=sql-server-2017 -->
+
+## Reproduction code
+<!--- Provide standalone JAVA code that reproduces the issue, preferably raw JDBC code. -->