Patch #34654
Accounting for the closing date of the issue when calculating the overdue
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Issues planning | |||
| Target version: | - |
Description
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
fix_overdue.patch 
(2.45 KB)
Related issues
History
#1
Updated by Mischa The Evil about 2 years ago
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.
#2
Updated by Stan Efremov about 2 years ago
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 returntruein case an issue is closed (due to the '&& !closed?' condition).Furthermore, the plain use of
Date.currentmight cause problems due to (user) timezone settings.
Issue does not stop being overdue after it is closed.
#3
Updated by 丽 李 about 2 years ago
- File 微信图片_20210201123844.jpg added
#4
Updated by 丽 李 about 2 years ago
- File 0121 (1).xlsx added
#5
Updated by Go MAEDA about 2 years ago
- File deleted (
微信图片_20210201123844.jpg)
#6
Updated by Go MAEDA about 2 years ago
- File deleted (
0121 (1).xlsx)
#7
Updated by Mischa The Evil over 1 year ago
- Duplicated by Patch #35919: Illumination of overdue closed issues added