Patch #34654

Accounting for the closing date of the issue when calculating the overdue

Added by Stan Efremov 8 months ago. Updated 8 months ago.

Status:NewStart date:
Priority:NormalDue 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 Magnifier (2.45 KB) Stan Efremov, 2021-01-29 09:13

History

#1 Updated by Mischa The Evil 8 months 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 8 months 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 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.

#3 Updated by 丽 李 8 months ago

  • File 微信图片_20210201123844.jpg added

#4 Updated by 丽 李 8 months ago

  • File 0121 (1).xlsx added

#5 Updated by Go MAEDA 8 months ago

  • File deleted (微信图片_20210201123844.jpg)

#6 Updated by Go MAEDA 8 months ago

  • File deleted (0121 (1).xlsx)

Also available in: Atom PDF