Vote #81246
未完了Accounting for the closing date of the issue when calculating the overdue
0%
説明
When calculating the overdue for issues, the closing date of the issues is not taken into account, despite the availability of relevant information. An overdue issue remains overdue even after it is closed.
Environment:
Redmine version 4.0.4.stable
Ruby version 2.6.5-p114 (2019-10-01) [x86_64-linux]
Rails version 5.2.3
Environment test
Database adapter PostgreSQL
Mailer queue ActiveJob::QueueAdapters::InlineAdapter
Mailer delivery test\nSCM:
Subversion 1.9.7
Git 2.17.1
Filesystem
Redmine plugins: no plugin installed
journals
Stan Efremov wrote:
> An overdue issue remains overdue even after it is closed.
This is not true. @Issue#overdue?@ will not return @true@ in case an issue is closed (due to the '@&& !closed?@' condition).
Furthermore, the plain use of @Date.current@ might cause problems due to (user) timezone settings.
--------------------------------------------------------------------------------
Mischa The Evil wrote:
> Stan Efremov wrote:
> > An overdue issue remains overdue even after it is closed.
>
> This is not true. @Issue#overdue?@ will not return @true@ in case an issue is closed (due to the '@&& !closed?@' condition).
>
> Furthermore, the plain use of @Date.current@ might cause problems due to (user) timezone settings.
Issue does not stop being overdue after it is closed.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
related_issues
duplicates,New,35919,Illumination of overdue closed issues