I always wondered why those RuntimeException messages popped up in our
error.log file.

On Tue, Nov 26, 2013 at 1:58 PM, Matt Thomas notifications@github.comwrote:

Steps to reproduce the issue

Click http://issues.joomla.org/tracker/joomla-cms/2523
Expected result

The issue
Actual result

0 RuntimeException
Invalid Issue

https://monosnap.com/image/4Fi8tXizrAkZAr09UjQk6SlmJ
System information (as much as possible) Additional comments

—
Reply to this email directly or view it on GitHub#228
.

Mystery explained. Should that indeed be an error page, or "that item has been closed" message?

If the issue isn't in the database (I don't see it on the tracker?) then it'll definitely throw an error page. I did a dump of everything but the users data when I merged the milestone PR from Andrew to the server, so a lot of data was taken with it.

So it's a feature ;)
Maybe the message could be a bit friendlier but hey - I prefer error messages to be as verbose as possible.
But for production we might just stick with the "invalid issue" message, without logging etc.

So it's a feature ;)

Since the goal is to make this application easily used, even by non-developers, I'd suggest something like

That issue does not exist, or the ID you typed is incorrect. Please try searching for the issue.

I would vote for: show a nice message to the user, write a verbose message to the log.

Nice