Love this idea of the app!

However, cannot change ticket status with empty markdown editor content.

Check this screencast: https://youtu.be/bhDRIuYlIjs

The blacked-out background doesn't disappear when the modal does. You have to click the screen to get the UI back to normal.

Hi dpawluk,

Sadly i had to disable oops in our Zendesk today.
Only 2 out of 8 agents were using it, all of the others simply set the timer to OFF.
With the update every agents sees the dailog now, which is not the best behavior i think.
Maybe you reconsider this?

Best,
Andreas

Our settings page says "Version 1.0 - Last updated 3 days ago", but I can't figure out what exactly that includes. Does this have all of the latest fixes live in the marketplace, or do I need to install a private version of the app?

When I try to submit a change to a ticket without adding a comment (e.g. just changing priority), I get the "Oops: This app has prevented the submission of the ticket." error dialog.

If I add a comment, then I get the nice new modal dialog, and it works fine.

The new modal dialog confirmation pushed in recent updates does not render markdown based comments very well. The entire markdown text is displayed as one giant run-on sentence which makes the display of it rather pointless. It is not rendered in the format I typed it, line endings are not preserved in the very least and worse case the formatting is not in HTML form the customer will see. Please don't follow the mistakes of Zendesk and leave the markdown customers in a lurch.

Rather than implement a full markdown renderer, might I suggest providing an option to not even render the message I typed ( ie. I know what I typed, so no need to display a bunch of noise that is not rendered correctly anyways.). If that solution does not fit well, at the very least maintain any carriage returns in my message.

Alas, I much preferred the simpler notification there was before anyways.

When the new modal dialog displays, no other work can be done unless the dialog is explicitly dismissed.

With the old notification message in the top right corner, work could continue on other tickets if the agent wished, without some interaction required.

This makes the new oops app less effective for the 99.9% of cases where no cancelling of the message is required by the agent.

Please come up with an option that does not require explicit dismissal of the modal to skip waiting so that majority of use cases can be satisfied.

Hi,

After the update today, many of our employees are not able to reply to tickets. Here is a screenshot of an example error that is being thrown in Chrome's Dev Console.

Please let me know if there is any other information you need to further troubleshoot this issue

Upload Error
Missing required key from translations/en.json: installation_instructions, long_description

If you select "Stay on ticket" upon submission, the modal does not disappear after the timer is up. It only disappears when "Close tab" or "Next ticket in view" are selected.

The modal should say "You wrote the below message," not "Your wrote the below message."

If you select "Next ticket in view" upon submission and then revisit the ticket you just updated, the ticket stays in a state of trying to update. It cannot be updated. The only way to get it back to normal is to close your browser tab and re-open Zendesk.

We wanted to reassign a Zendesk ticket to a different group and encountered this error from the OOPs app. Any idea what this means?

Once I disabled the OOPs app, I was able to submit the change.

After last zendesk update, this app is not working. When I submit the ticket and after trying to click on "Cancel Submission" nothing happens and ticket gets submitted.

When agents trying to set app off pop-up window showing up and get stalled, till you click submit button.

Can you fix that? Thank you,

It appears that any JavaScript entered into a ticket comment is run by the modal prior to ticket submission. For example, when attempting to submit this comment:

Hello, again!

Your conversion pixel would actually look like the following:

<script>
ga('send', 'event', 'X', 'Y', 'Z'); 
</script>

Hope this helps! Let me know if you need any further assistance.

The modal will run that JavaScript and prevent the response from being submitted due to an app error:

Tried using markdown to format the JS in a code block, but didn't appear to make any difference. Disabling the app resolves the issue.

As of 12/7/16, "Cancel submission" button does not respond.

Here is a screencast of the reproduction: http://www.screencast.com/t/baB4ihG3t4m

Steps to reproduce:

1. Submit a ticket
2. Click "Cancel Submission"
3. Notice that submission is not cancelled and message is sent

One of my agents is unable to keep his "OOPS" configuration from resetting. Each time he goes to a new ticket the app changes back to 10 seconds. Any advice on how to troubleshoot this?