After entry of 1st issue - go to login screen
After I enter my first issue for the session, I get thrown back to the login screen instead of the Issue List.
To avoid this I have to go to My Profile (before entering a new Issue), make a change to My Profile, ie: set the # of issues displayed from 20 to 21, select Update and it seems to be ok after that. This is not convenient to have to do this at the start of every session.
|
memr
· 1 |
|
| Monday, January 23, 2006, 7:50:25 PM | |
0
|
Hi,
Which version of Gemini are you using? Does it happen every time you log in? Can you please test to see if you get the same on http://beta.countersoft.com?
|
||||
|
|||||
0
|
Running version 2.0.2 Yes it happens all the time. Once I have logged in and enter an Issue it returns me to the login screen. After the 1st issue it does not happen again - after that it returns me to the Issues List (which is where I expect to go). I entered a new issue (on countersoft) and did not seem to have the same problem. Another consideration - in my office we have 4 users entering Issues, 2 of the users have the problem and 2 do not. It would appear to be a configuration issue for 2 of the users. Thanks |
||||
|
|||||
0
|
I have seen this issue to, also using 2.0.2 It seems fine on my machine (using firefox) and my colleague just got kicked off after entering the issue, he was using IE (may have some bearing on it?) |
||||
|
|||||
0
|
It could be authentication / cookie related. FireFox OK? |
||||
|
|||||
0
|
We have just upgarded to v2.0.2 and have a similar issue - where when we select to view an issue from list in the Issues form we are logged out and taken back to the home screen). The second time this is attempted (selecting to view an issue on the Issues form) the Issues form is returned with "No issues found" (as if we're logged out). It's strange because for some issues we can view them fine and other issues exhibit the above behaviour. Any ideas? |
||||
|
|||||
0
|
All, We will ship v2.0.3 beta w/c 6 FEB. We have made improvements around authentication. It may fix the symptoms documented herein. |
||||
|
|||||
0
|
False Alarm! During the upgrade we neglected to change one of the parameters in the web config from the test instance of our database to the production instance. Woops Tim |
||||
|
|||||




