Project

General

Profile

Actions

Defect #42066

closed

NoMethodError exception occurs in IssuePriority#high and #low when both default and active priorities are absent

Added by Go MAEDA 12 days ago. Updated about 7 hours ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Issues
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

A NoMethodError exception occurs when there is no default issue priority and all issue priorities are inactive, and IssuePriority#high or IssuePriority#low is called. his issue affects the process of generating the email notification recipients in Issue#notified_users. Consequently, the error can lead to an Internal Server Error being displayed in the user’s web browser during issue updates.

The attached patch updates IssuePriority#high and IssuePriority#low to return false when self.class.default_or_middle is nil, avoiding exceptions.


Files


Related issues

Related to Redmine - Defect #40860: Creating a new issue fails with an internal error if no issue priorities are definedClosedGo MAEDA

Actions
Actions #1

Updated by Go MAEDA 11 days ago

  • Related to Defect #40860: Creating a new issue fails with an internal error if no issue priorities are defined added
Actions #2

Updated by Go MAEDA 11 days ago

  • Target version set to 5.1.6

Setting the target version to 5.1.6.

Actions #3

Updated by Go MAEDA 11 days ago

  • Status changed from New to Resolved
  • Assignee set to Go MAEDA
  • Resolution set to Fixed

Committed the fix in r23431.

Actions #4

Updated by Go MAEDA about 7 hours ago

  • Status changed from Resolved to Closed

Merged the fix into stable branches in r23435 and r23436.

Actions

Also available in: Atom PDF