# How to optimize issue/support ticket like workflow?

**URL:** https://meta.discourse.org/t/how-to-optimize-issue-support-ticket-like-workflow/67820
**Category:** Community Building
**Created:** [2017年八月10日 15:01 UTC](https://meta.discourse.org/t/how-to-optimize-issue-support-ticket-like-workflow/67820 "2017-08-10T15:01:48Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2017年八月10日 20:45 UTC](https://meta.discourse.org/t/how-to-optimize-issue-support-ticket-like-workflow/67820/6 "2017-08-10T20:45:33Z")

</div>

> [@Sujan](#):
>
> (Today) The worst topics were those where users post code, but don’t format it with ```.

We wrote special code at Stack Overflow that tries to detect unformatted source code (there are a lot of unusual `[` and `{` characters per line, etc) and blocks the post until the user formats it. I believe there has been some discussion of such a plugin for Discourse, it wouldn’t be terribly hard to write.

Then users started posting screenshots of code ..

---

_[View the full topic](https://meta.discourse.org/t/how-to-optimize-issue-support-ticket-like-workflow/67820)._