Project

General

Profile

Actions

Feature #42886

open

Ability to bypass due date in the past for MailHandler

Added by Tom Misilo 7 days ago. Updated 6 days ago.

Status:
Needs feedback
Priority:
Normal
Assignee:
-
Category:
Email receiving
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

Currently when a due date is set for the past (because of someone replying to an original email that got sent to the ticketing system) every new reply gets rejected.

MailHandler: Validation failed: Due date must be greater than start date

Is there a way to override this with the mail_handler endpoint? If not, can a flag be added?

Thank you!

Actions #1

Updated by Holger Just 6 days ago

  • Status changed from New to Needs feedback

This should not happen with default Redmine.

The error you are receiving is a generic issue validation for when you try to update an issue and set either its due date or its start date to an invalid value (i.e. the start date after the due date). However, the start date is only automatically set on newly created issues based in the global setting in Administration -> Settings -> Issues -> Use current date as start date for new issues. For existing issues, Redmine does not automatically set a start date. For existing issues or when not changing either the due date or the start date, this is also not checked. Note that the same validations are also applied when updating an issue by other means, e.g. via your web browser or the API.

Thus, what may happen here is that something tries to set an invalid start date and/or due date. This could be because of a customization in your Redmine or because you are trying to set an explicit date from your mail (e.g. in the mail body or via a mail handler option). In any case, the cause of this issue is likely within your configuration and you should fix this.

Without further details, it is however difficult to actually pinpoint the root cause of this. To be able to further look into this, we need more details about your specific issue and the mail as well as your issue settings. A full log entry from your log/production.log is also helpful.

Actions

Also available in: Atom PDF