During JIRA development, our internal systems were deployed with a version of JIRA that had a broken JQL parser. The effect was to make JIRA Agile's welcome and management pages unusable due to an internal server error.

This suggests three separate problems:

1. The JQL parser needs to be fixed
2. JIRA should be hardened to avoid exposing plugins to undeclared runtime exceptions if unparsable JQL is encountered in the database. This is important because the ability of OnDemand customers to export and import to their on premise instance means that they could have created search requests (filters) in the OnDemand instance that the on premise instance cannot yet support.
3. JIRA Agile should be hardened against exceptions that occur when trying to retrieve a search request (filter).

This last point is what this issue is meant to cover; the other two are being tracked internally by JIRA development.