summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjames-mm <34751054+james-mm@users.noreply.github.com>2018-04-25 14:39:58 -0500
committerJesse Hallam <jesse.hallam@gmail.com>2018-04-25 15:39:58 -0400
commitd3f09b54e2be65981f0496938f9d5f97507874e6 (patch)
treeac5e6453631ccbbc76fea255d2c86f98819f08e4
parent3224d2f6a3bd95293fff25d6cc417b30b4f6e334 (diff)
downloadchat-d3f09b54e2be65981f0496938f9d5f97507874e6.tar.gz
chat-d3f09b54e2be65981f0496938f9d5f97507874e6.tar.bz2
chat-d3f09b54e2be65981f0496938f9d5f97507874e6.zip
Update ISSUE_TEMPLATE.md (#8292)
* Update ISSUE_TEMPLATE.md Customer wanted us to be more explicit on this page about searching for existing tickets in JIRA vs Github before proceeding to submit a new ticket. * Update ISSUE_TEMPLATE.md * Shorten proposed text
-rw-r--r--ISSUE_TEMPLATE.md8
1 files changed, 6 insertions, 2 deletions
diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md
index 8bc8e160d..774c5022a 100644
--- a/ISSUE_TEMPLATE.md
+++ b/ISSUE_TEMPLATE.md
@@ -1,9 +1,13 @@
-Per Mattermost guidelines, GitHub issues are for bug reports: http://www.mattermost.org/filing-issues/
+Per Mattermost guidelines, GitHub issues are for bug reports: <http://www.mattermost.org/filing-issues/>.
For troubleshooting see: http://forum.mattermost.org/.
For feature proposals see: http://www.mattermost.org/feature-requests/
-If you've found a bug--something appears unintentional--please report using the following format:
+If you've found a bug--something appears unintentional--please follow these steps:
+
+1. Confirm you’re filing a new issue. [Search existing tickets in Jira](https://mattermost.atlassian.net/issues/) to ensure that the ticket does not already exist.
+2. Confirm your issue does not involve security. Otherwise, please see our [Responsible Disclosure Policy](https://about.mattermost.com/report-security-issue/).
+3. [File a new issue](https://github.com/mattermost/mattermost-server/issues/new) using the format below. Mattermost will confirm steps to reproduce and file in Jira, or ask for more details if there is trouble reproducing it. If there's already an existing bug in Jira, it will be linked back to the GitHub issue so you can track when it gets fixed.
#### Summary
Bug report in one concise sentence