11-01-2012 02:20 PM
What is the current amount of time at which the user session will timeout? Is this user configurable?
Just asking... it seems a little on the short-side. I'm having the issue identified in:
so, when it times out, I have to completely shutdown my browser/restart it to get back into AM.
11-06-2012 02:22 AM
Session timeout is 60 minutes and the motivation is to protect access to user's data in case of public / shared computers.
In case session has expired user is redirected to login page .
In your case the thrown exception is unexpected behavior that doesn't happen on our environment.
I send you email to collect exact details from your environment.
11-11-2012 02:35 AM
I have a theory I am trying to validate and I need more information about how you are using the application.
Can you please say how frequently you login the Community (the page we communicate through) and how do you open it?
Are you using the same browser for both?
Thanks in advance,
11-13-2012 12:09 PM
I typically have the AM community page up and within the same browser.
I think you are suggesting that their might be session corruption going on between the two? That had crossed my mind... as I log in to the community site only when I want/need to update/submit content.
As a test... With AM Saas up... I logged into this community site. Behold... my AM session threw a session logout dialog window up on my next activity.
So, I think you are correct that there might be there.
03-13-2013 10:45 AM
60 minutes is too short for a productivity tool to be used in a professional enterprise. If Outlook or our developers SDK timed out in 60 minutes there would be a revolution.
Leave the security to the enterprise to manage. Don't embed your assumptions for the lowest common case of a public computer.
03-16-2013 01:35 PM
Thank you for your feedback.
Today we use the "one hour of incactivity expriaction", which is the standard in the inducstry.
Still, I agree with you that it's too short, and the best way is to leave the decision in your hands.
I will surly take it forward here in R&D.
04-11-2013 01:47 PM
I whole-heartedly agree. The current timeout is far too short.
When I used Rally, this was not a problem. The session timeout is user-selectable, from 30 minutes to 10 hours. And, it was easy to set it up so it my browser could auto-login.
To really use this tool for my Agile tasks, I want to stay logged in all day. With tasks that are often only one or a few hours long, it should be extremely easy to go back to Agile Manager and update my task board. Having to re-login is a major pain and is one more barrier to having the tool reflect reality.
Having a "remember me" or "stay logged in on this computer" feature would help. The comment about "industry standard" practice doesn't match my experience. These features are common, especially for tools that are providing a "work environment" kind of functionality.
06-05-2013 12:40 PM
I would agree that the current timeout needs to be enhanced. If it must stay global, at least increase the amount of time. Obviously the preference would be some type of configuration, either at sign in time, or by account, or whatever. Basically the current timeout is too short and causes frustration with Agile Manager.
06-17-2013 08:22 AM
I subscribe to the feedback provided above. We really need a different approach on the session timeout feature, either a) simply increase it to a reasonable timeframe (8-10 hours to cover a business working day), or b) implement "Remember me" like feature, or c) have the session timeout configurable on user profile, rather than site setting. Or any other idea that makes usage of AGM more efficient?
In any case, is there any update to this from AGM team? Thanks.
06-26-2013 02:21 PM
First of all, I leave AGM open in one of my browser tabs. It is corprate policy for me to lock my computer when I am not at my desk, so nobody has access to my applications. If they do gain access it is because I am not following policy.
Secondly, I am constantly losing infomation with this timeout functionality. In part because 60 minute timeout is too short, but also in part that the application doesnt actually sign me out on my browser like a banking application would. I constantly go to the tab in my browser and the application appears to be open. I enter a long winded description of a defect and hit the save button. BUT WAIT, its been more than 60 minutes and the sign on page appears. I just lost all my data.
07-09-2013 12:26 AM
This should be a simple choice to be made by the user. If the user wants to increase the time or even disable it they should be able to.
I also have been loosing information as well because of this crazy security setting. If you don't want to remove it at least make it a user choice.
07-10-2013 04:41 AM
We really appreciate all your feedback regarding the session timeout.
We are planning to improve this user experience in one of our upcoming releases.
What we plan to do is the following:
- Renew the session as long as user clicks on the keyboard before the session has expired.
- Notify the user that session is about to expire, with ability to renew the session in one click.
- In case of session timeout, the user will be ask to enter password and he will be able to continue from the point session was expired (no data loss). There will be no redirection to the portal and no application reload
In the meantime we are considering to increase the session timeout. Please stay tuned.