Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

About session timeout and remember me default values


Currently, among all Atlassian products I'm using I've noticed that there are different timeout values defaults regarding authentication and "Remember me" feature.

ApplicationAuthentication TimeoutRemember me Timeout
JIRA300 mins (5h)2 weeks
Confluence60 mins (1h)2 weeks
Bitbucket30 mins4 weeks
Bamboo30 mins2 weeks

Why not making them equal?

I would like to discuss/know the rationale behind these differences and if it is the case to align them all or leaving them unchanged or just make some changes.

Since the differences are big I was wondering why they are so different.

1 comment

An additional note that further confuses things, 2147483 is apparently the max (seconds) remember me timeout in JIRA, and anything above that value causes NullPointerExceptions. So setting consistent values across the different services is not intuitive.

Like Stefano Coletta likes this

2147483 seconds are about 3,5 weeks, that is why JIRA remember me is set to 2 weeks! From what you discovered, you can't set it to 4 weeks to align with Bitbucket for example... so maybe we can raise it to 3 weeks and lower down the Bitbucket one to 3 weeks also...


Log in or Sign up to comment