Details
-
Suggestion
-
Resolution: Fixed
-
None
-
14
-
Description
Display a meaningful error message if a user attempts to perform an action when their session has timed out. At present, the user is confronted with the error screen and a long stack trace (see JRA-5751).
Attachments
Issue Links
- details
-
JRASERVER-14664 Session Timeout warning 30 seconds before
- Closed
- incorporates
-
JRASERVER-17360 Session Timeout dumps exception when viewing manage attachments
- Closed
- is duplicated by
-
JRASERVER-2247 Session time out not captured properly
- Closed
-
JRASERVER-7298 User 'null' does not have permission error when accessing secured JIRA issue after session expires
- Closed
- is related to
-
JRASERVER-10013 User timeout exception for transition/create issue
- Closed
-
JRASERVER-14494 NullPointerException thrown when clicking the "Start" watching link in the "Manage Watch List" panel and not logged in
- Closed
-
JRASERVER-9583 When not able to see an issue because of a permission violation the error message should be more informative
- Closed
-
JRASERVER-11131 Create Issue when not logged shows invalid page
- Closed
-
JRASERVER-15079 Sent information is lost when data is submitted after session has expired
- Closed
- relates to
-
JRASERVER-9171 A timed out session causes stacktraces in half-completed actions
- Closed
-
JRASERVER-11539 Session timeout when adding comment generates different NPE
- Closed
-
JRASERVER-8050 Timeout generates an ugly error
- Closed
-
JRASERVER-10159 Log Work Done does not check for current session
- Closed
-
JRASERVER-11188 'System error' after session expires
- Closed
-
JRASERVER-10638 Clean up Permission Violation error reporting for all issue operations
- Closed
-
JRASERVER-12839 When session expires and a login is forced the add commet operation loses the original comment text
- Closed