How to change the default session timeout

The information on this page relates to customizations in JIRA Applications. Consequently, Atlassian Support cannot guarantee the provision of any support for the steps described on this page as customizations are not covered under Atlassian Support Offerings. Please be aware that this material is provided for your information only and that you use it at your own risk.

Also, please be aware that customizations done by directly modifying files are not included in the upgrade process. These modifications will need to be reapplied manually on the upgraded instance.

Overview

The default timeout for web sessions from JIRA 4.3 onwards is 300 minutes (5 hours). This page discusses how you could modify it.

Solution

(warning) If you are deploying JIRA as a closed .war file you will need to unzip the .war, edit the file, and re-create the .war with exactly the same structure as it originally had.

 

To change the default session timeout you must edit the  $JIRA_INSTALL/atlassian-jira/WEB-INF/web.xml file. The value within the  session-timeout tag defines the amount of time the session will exist, in minutes.

 

<web-app ...>
...
     <session-config>
         <session-timeout> 300 </session-timeout>
     </session-config>
...
</web-app>

Anything 0 or below sets it to an unlimited timeout

JIRA needs to be restarted after the above changes to have effect the new session timeout.

If you are running multiple Atlassian applications on the same server, JIRA users may still get consistently logged out. In this case, you may need to change the context path according to the Logging into Another Atlassian Application Logs Me Out of Confluence.

(warning) Please take into account these two feature requests:

JRA-14311 - Getting issue details... STATUS

JRA-60844 - Getting issue details... STATUS

Last modified on Mar 28, 2017

Was this helpful?

Yes
No
Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.