Feature #23285

Version to have history

Added by Dipan Mehta about 6 years ago. Updated over 5 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


While each work item in software is reflected in issues - version typically have significant critical role in the overall development process.

As indicated under #13387 - the version should be treated as a first class citizen in redmine.

Version should have the history - which provides for
  1. Changes in the custom fields,
  2. Allow for adding notes
  3. Register when specific issues were moved in and out under the given version.
  1. Also, many a times scope and reviews about specific done under meetings - so there should be some representation of capturing minutes-of-meeting (with timeline) under the version page.
  2. Release notes, User documents, Testing documents etc. can be added specifically for each version.

This help version to be a able to capture the complete and more comprehensive (than issues) outline that will capture the development processes.

Related issues

Related to Redmine - Feature #13387: Improving Redmine's version model (not just milestones) New


#1 Updated by Toshi MARUYAMA about 6 years ago

  • Related to Feature #13387: Improving Redmine's version model (not just milestones) added

#2 Updated by Steve Légaré over 5 years ago

+1 Version to have history (tracking field modification, linked issues, etc).

Also available in: Atom PDF