Feature #4528


Add Projected Date field to Version

Added by Eric Hollering over 13 years ago. Updated over 13 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


Add a "Projected Date" field to the version, to allow the differentiation between when a version is due and when it is expected to be delivered.

Currently versions only have a Due Date field, so if a project falls behind schedule (or gets ahead of schedule, if that is even possible) users do not know when to anticipate the release of the version. Managers are always asking for a revised schedule, and yet changing due dates to reflect the new schedule would cause the user to lose visibility of performance compared to the initial project schedule.

If a "Projected Date" field were added, it could be displayed on the Roadmap in addition to the Due Date, which could then serve as a deliverable for a revised schedule, and still preserve the visibility against the initial schedule.

Another, perhaps more work intensive, use of this field would be to give the user a combo box that would allow them to choose either the Due Dates or Projected Dates when displaying the Gantt chart.

Actions #1

Updated by Eric Hollering over 13 years ago

Upon further consideration, perhaps a better name might be "Release Date" or "Delivery Date", so that it is still relevant post-release.

Actions #2

Updated by Jean-Philippe Lang over 13 years ago

FWIW, you will be able to add custom fields to versions in 0.9.

Actions #3

Updated by Eric Hollering over 13 years ago

That's great news! I was already planning an upgrade because of the ABSOLUTELY PRICELESS value of infinitely nestable projects. Keep up the great work! This is such a great tool! Perhaps one of these days I'll be able to contribute more to the effort.

Actions #4

Updated by Eric Davis over 13 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Closing, adding a custom date field is the best solution.

Actions #5

Updated by Eric Hollering over 13 years ago

I would like to respectfully disagree with the resolution in this particular case, because of the uses I indicated in the initial issue description (with the change I mentioned in the first comment).

I think adding the field as a permanent and official resident would vastly enhance the reporting opportunities for future development.


Also available in: Atom PDF