Details
-
Suggestion
-
Resolution: Won't Fix
-
None
Description
We should have a more graceful way to handle an exception page.
For example:
If users are not logged in and they tried to access JIRA by url, http://jira.atlassian.com/secure/ManageWatchers!default.jspa?id=12345, they will see an error page that looks like this:
com.atlassian.jira.exception.IssueNotFoundException: Issue with id '12345' or key 'null' could not be found in the system at com.atlassian.jira.web.action.issue.AbstractIssueSelectAction.getIssue()Lorg/ofbiz/core/entity/GenericValue;(AbstractIssueSelectAction.java:85) at com.atlassian.jira.web.action.issue.ManageWatchers.isCanViewWatcherList()Z(ManageWatchers.java:218) at com.atlassian.jira.web.action.issue.ManageWatchers.doDefault()Ljava/lang/String;(ManageWatchers.java:41) ...
Ideally, we can have a page that looks like this:
You are not logged in, and do not have the permissions required to manage the watchers as a guest. To manage the watchers first login or signup for an account.
Cheers,
Terry
Attachments
Issue Links
- is related to
-
JRASERVER-10638 Clean up Permission Violation error reporting for all issue operations
- Closed
- relates to
-
JRASERVER-11077 More graceful way to handle exception page
- Closed