summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorlfbrock <lf.brock@spinpunch.com>2015-12-01 10:07:08 -0500
committerlfbrock <lf.brock@spinpunch.com>2015-12-01 10:07:08 -0500
commitff8573cfdf7957acfa4797089a116df92c85a7a7 (patch)
tree774a05937e0d33cea08ea5587de82d5d18cb363e /doc
parent62c96514bfa243029dba2d9b47b5b8a8322059e4 (diff)
downloadchat-ff8573cfdf7957acfa4797089a116df92c85a7a7.tar.gz
chat-ff8573cfdf7957acfa4797089a116df92c85a7a7.tar.bz2
chat-ff8573cfdf7957acfa4797089a116df92c85a7a7.zip
Update overview.md
Diffstat (limited to 'doc')
-rw-r--r--doc/process/overview.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/process/overview.md b/doc/process/overview.md
index af632e393..b34908782 100644
--- a/doc/process/overview.md
+++ b/doc/process/overview.md
@@ -64,7 +64,7 @@ Mattermost priorities are managed in Jira tickets, which are created by the core
On non-holiday weekdays new tickets are reviewed in a process called "triage", and assigned a Fix Version of "backlog", indicating the ticket has enough specificity that it can be assigned to a developer to be completed.
-By default, all tickets are created as internal-only, and the triage process reviews them for sufficient specifity and abscense of sensitive information before switching their visibility to public as part of the triage process.
+By default, all tickets are created as public unless they contain sensitive information. The triage process reviews them for sufficient specifity. If the ticket is unclear, triage may reassign the ticket back to the original reporter to add more details.
View [current issues scheduled for the next triage meeting](https://mattermost.atlassian.net/browse/PLT-1203?filter=10105).