Vote #76697
未完了Users' "Last connection" is not updated correctly.
0%
説明
In the User Profile, there are following two date fields.
- Registered on: 2015-01-01 (value is an example)
- Last connection: 2015-09-01 (value is an example)
For some users, "Last connection" is not correct. Although the user logs in Redmine, "Last connection" date is not updated.
In our system, for example, a user logged in on August 31, 2015. But "Last connection" date is still "August 22, 2015".
It is also true in the Administration=>Users listing.
We are using this field to determine if the user is active or not. So We hope this field is correct.
Thank you all, in advance.
- Reported version
Redmine 2.5.0.stable.
Details are as follows.
Environment: Redmine version 2.5.0.stable Ruby version 1.9.3-p484 (2013-11-22) [x86_64-linux] Rails version 3.2.17 Environment production Database adapter PostgreSQL
journals
kaz k wrote:
> It is also true in the Administratyion=>Users listing.
Sorry...typo.
"Administratyion"=>"Administration"
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
From #2820
# When a user logs in the User.last_login_on field is updated to the current time.
# When logging in via an autologin cookie the user's last_login_on be updated
How do you expect?
--------------------------------------------------------------------------------
Toshi MARUYAMA wrote:
> From #2820
>
> # When a user logs in the User.last_login_on field is updated to the current time.
> # When logging in via an autologin cookie the user's last_login_on be updated
>
> How do you expect?
My expectations are as follows.
# As the field says "Last connection", it is natural that "Last connection" is to be updated every time when a user logs in, regardless of the autologin cookie ( and its expiration).
** There is a time duration of user's activity from Log-in to Log-out. "Last Connection" is not clear if it points the log-in time or log-out time, and sometimes log-out time is not captured precisely (for example, when the connection is broken). This is why I think Last log-in time is appropriate.
** "Last connection" might be renamed as "Last Log in".
# From the administrator's view, he/she wants to know how long a user has not logged in to determine if the user seems inactive or not. It does not depend on the use of autologin cookie.
Kind regards,
--------------------------------------------------------------------------------
Attached is a screenshot of our Redmine user profile screen captured today. There are comments in it.
Hope this helps.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Found the same issue on version 2.6.1
--------------------------------------------------------------------------------
+1
My environment is:
<pre>
Environment:
Redmine version 2.6.2.stable
Ruby version 1.9.3-p551 (2014-11-13) [x86_64-linux]
Rails version 3.2.21
Environment production
Database adapter Mysql2
</pre>
--------------------------------------------------------------------------------
I have wrote a patch to fix this issue.
With this patch applied, "Last connection" is updated every time the application is accessed.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Go MAEDA wrote:
> I have wrote a patch to fix this issue.
> With this patch applied, "Last connection" is updated every time the application is accessed.
Great! This is how it should work.
--------------------------------------------------------------------------------
Go MAEDA wrote:
> I have wrote a patch to fix this issue.
> With this patch applied, "Last connection" is updated every time the application is accessed.
Thank you very much !
I think the description of "Last connection" is better to be replaced with "Last Activity".
Because user may keep login for a few days and keep making updates. In this case, "Last connection" is older than the current date. If the patch works as described, the field indicates last access.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
I'm running redmine with the following environment:
<pre>
Redmine version 3.2.0.stable
Ruby version 2.1.8-p440 (2015-12-16) [x86_64-linux-gnu]
Rails version 4.2.5
</pre>
but having the same issue... Will that patch be applied to 3.2.0 too?
--------------------------------------------------------------------------------
Ronald Heggenberger wrote:
> I'm running redmine with the following environment:
> [...]
> but having the same issue... Will that patch be applied to 3.2.0 too?
I also have the same issue in 3.2.1 version
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
related_issues
relates,Closed,28952,Update User#last_login_on only once per minute