Default session time out was changed to 120 minutes

Vladimir Cech
Vladimir Cech Member Posts: 181
in Peer-to-Peer Support Forum

Hello other Jama Customers,

Do you know that Jama has changes the setting of a default session timeout to 120 and it's not possible to customize it? See Jama Connect® User Session Timeout

We used customized timeout set to 20 minutes, that is now in fact 40 minutes (I've tested it repeatedly) although Jama states that it is 120 minutes.

I'm trying to get any explanation from Jama but support repeatedly points to above mentioned article only.

We used shorter timeout to free up Create float license sooner to allow other users to login (when user does not close/logout from the Jama app) and also for security reasons.

Missing ability to customize it and also default value set to 120 minutes seems to weird to me and not customer satisfaction oriented.

What do you think?

Vlada

Vlada

Comments

  • Alessandro Valli
    Alessandro Valli Member, Data Exchange, Jama Connect Interchange™ (JCI) Posts: 789

    Hi Vlada,

    I have exactly the same approach and I share your thoughts 🤨

    I am going to ask …

    Alessandro

    Alessandro
    Systems Engineer
    SICK AG
  • Alessandro Valli
    Alessandro Valli Member, Data Exchange, Jama Connect Interchange™ (JCI) Posts: 789

    just got answer: it applies only to cloud instances.

    Alessandro
    Systems Engineer
    SICK AG
  • Dimitrios Pananakis
    Dimitrios Pananakis Member, Jama Validation Kit (JVK) + Functional Safety Kit (FSK) Posts: 57

    The support page mentions this: Timeout sessions cannot be modified as part of our efforts to improve user experience and security. The timeout value is set to provide the best user experience and includes time for writing complex requirements without worrying about a ticking clock.

    If anything, this worsens the user experience and does not cater for security. On the contrary.
    For one, I am not expecting someone to be taking up a license to use Jama interactively in order to write a complex requirement. Besides this, if the user is actively using Jama to write a complex requirement, the timeout is reset with every UI interaction. So the argument presented by the support about providing enough time to author such a requirement is in fact invalid.

    I would like it to be user defined for cloud instances or in general. As Vlada mentioned, each organization has its own needs.

  • Jason Barton
    Jason Barton Member, Jama Connect Interchange™ (JCI), Jama Validation Kit (JVK) + Functional Safety Kit (FSK) Posts: 16
    edited September 11

    https://community.jamasoftware.com/discussion/26577/allow-users-to-set-the-session-time-out-variable

    Vote it up :)

Categories