[#JRA-14392] Notification Fails Because of Invalid Custom Field

JIRA

Notification Fails Because of Invalid Custom Field

Created: 03/Feb/08 08:21 PM Updated: 10/Feb/08 11:01 PM

Component/s:

Events / Listeners, Custom Fields

Affects Version/s:

3.12.1

Fix Version/s:

3.12.3

Time Tracking:

Original Estimate:

Not Specified

Remaining Estimate:

0 minutes

Time Spent:

4 hours

Participants:	Andreas Knecht [Atlassian], Anton Mazkovoi [Atlassian] and Timothy Chin [Atlassian]
Since last comment:	22 weeks, 6 days ago
Resolution Date:	10/Feb/08 10:58 PM
Labels:

Description

« Hide

The notification email will fail (partly) to send if there is a custom field (i.e. user or group picker) which has already been deleted from the system.

* Current Assignee  (Delete)
* Reporter (Delete)
* All Watchers (Delete)
* User Custom Field Value (Multi User pIcker) (Delete)
* Single Email Address (tchin@atlassian.com) (Delete)
* Single User (admin) (Delete)

If the notifications for an event is set up like the above and if "Multi User pIcker" is removed from JIRA, the notification email number 4 and 5 will fail.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 04/Feb/08 01:05 AM

This might be fixed already for 4.0, see ~~JRA-12449~~. We need to check.

[ Permlink | « Hide ]

Andreas Knecht [Atlassian] - 10/Feb/08 11:01 PM

This bug should only occur with old data as removing a custom field already clears notifications just fine (this has been the case for a long time). I've fixed this now such that the User & Group CF getRecipients methods will be able to handle exceptions when the custom field no longer exists. A warning will be output to the logs, and all remaining notifications will be sent just fine.