ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
Optional start date on Versions (Feature #279)
Right now a Version's start date is determined by the earliest start date of an issue. This causes problems if an issue was "pushed" from a previous version. I propose having an optional start date on versions, so things like the Gantt can use the actual start date.
- Version "Old", represents 6 months of time - due 2010-05-01
- Version "New", represents the next 6 months of time - due 2010-12-01
- Issue 100 created 2010-01-01
When Issue 100 is assigned to Version Old, Version Old's date range is from 2010-01-01 to 2010-05-01. If Issue 100 is reassigned to Version New, Version Old's date range becomes 'nil' to 2010-05-01. Version New's date range is now 2010-01-01 to 2010-12-01, which includes the entire Version Old.
I've added an optional start date to Versions. I cleared the "field_effective_date" i18n key because that was using Date when it should have been Due date (though it's also called
effective_date in the code).
This should go into a major version because of the database change (e.g. 2.0.0)
Pull request: https://github.com/chiliproject/chiliproject/pull/24
- Status changed from Open to Ready for review