we found the problem when the user get auto logoff timeout and you are in the job configuration screen.
- when you are being logged of, you will be redirected to login screen
- you need to login, ok
- but, your changes (if you did not save it before) in job configuration are lost and you are not able to continue with the modified data
Maybe you can improve that?
In the meaning to be able to continue in the job configuration?
- problem is worse than expected, we noticed, when you got login timeout and you will click o save button in the configuration page, got your job completely destroyed
(regarding this, changing to bug and priority to major)
(as the workaround works to increase the login timeout, but I think that should be changed)
Thanks in advance for any response.