JIRA makes me sad. Our project always silently expires sessions at the worst possible time.
I would expect that if my session has expired, it should prompt me to re-authenticate as soon as a view the page, rather than when I perform an action.
Other examples:
The handling around expired session generally feels wonky, sometimes the page will error ungracefully, other times you'll be prompted to re-authenticate.
Is it possible that our admin has misconfigured some settings for this project that are contradictory and cause the sessions to behave unexpectedly? Or is this a bug in JIRA Cloud's session management that others experience as well.
Hi Dave - My session never expire. So yes, your instance has something configured for that.
Take a look at this: https://support.atlassian.com/jira-cloud-administration/docs/configure-session-timeout/
This is based on the configuration of the policy you are in within the administrative settings of your instance.
Contact the overall administrator of the Atlassian instance to present your point.
Here in community, most of us are Atlassian users like yourself, not (necessarily) employees of Atlassian. We don't have access to your environment.
See documentation; security-and-access-policies - update-idle-session-duration
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.