Feature #23285
Version to have history
Status: | New | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Roadmap | |||
Target version: | - | |||
Resolution: |
Description
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- Changes in the custom fields,
- Allow for adding notes
- Register when specific issues were moved in and out under the given version.
- 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.
- 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
History
#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).