Feature #43895
open
Disable "Use current date as start date for new issues" by default for new installations
Description
Currently, the "Use current date as start date for new issues" setting is enabled by default, so a new issue gets today's date as its initial start date.
This is useful in some cases, such as bug fixing or support work, where the creation date and the actual start date are often the same.
However, Redmine is often used to plan and track work before it actually starts. In many such cases, the creation date and the actual start date are different. Using the creation date as the initial start date does not reflect the actual schedule, and can lead to misleading information in gantt charts and project tracking.
The attached patch changes this default for new installations. Existing installations keep the current behavior.
Files
Related issues
Updated by Go MAEDA 2 months ago
- Related to Feature #2269: Default issue start date should become configurable. added
Updated by Go MAEDA about 2 months ago
- Status changed from New to Closed
- Assignee set to Go MAEDA
- Resolution set to Fixed
Committed the patch in r24564.
Updated by Go MAEDA about 3 hours ago
- File 0001-Persist-default-default_issue_start_date_to_creation.patch 0001-Persist-default-default_issue_start_date_to_creation.patch added
- Status changed from Closed to Reopened
The change committed in r24564 does not work as expected: even in new installations, "Use current date as start date for new issues" is not disabled.
This is because the default value for Setting.default_issue_start_date_to_creation_date is not stored by an earlier migration for new installations. As a result, the migration source:trunk/db/migrate/20260320090000_ensure_default_issue_start_date_to_creation_date_is_stored_in_db.rb added in r24564 to preserve the setting value for existing installations always sets Setting.default_issue_start_date_to_creation_date to "1" even in new installations, because no record exists yet.
The attached patch fixes this by storing the new default value early for new installations, as is done for other settings whose default values were changed later.
Normally, this code would be added to source:trunk/db/migrate/017_create_settings.rb. However, at that point, settings.name is limited to 30 characters. Since default_issue_start_date_to_creation_date is longer than that, the code is added to source:trunk/db/migrate/20090318181151_extend_settings_name.rb, after the limit is increased.