Meaning and context of Versions

Added by Robert Schneider about 14 years ago

For project management we have created an additional tracker called Task. In this we put our tickets that are not related to bugs or features. Now there are Versions that we assign the task to. But those versions are no real versions, rather they are just due-dates. And often they are not directly bound to a software product at all. In these cases the term 'Version' is not the best one.

Are there any suggestions to make it better or different?

Generally, I would be happy to be able to manage project tasks without the need of a software product, or without the need to think 'version does here mean due-date'.

Replies (2)

RE: Meaning and context of Versions - Added by Felix Schäfer about 14 years ago

We like to think of them as milestones, not versions. I can point you to the language file where you could change the name of the versions if you'd like to change the name, though it will change the name everywhere, not just in one project or just for your _task_s.

RE: Meaning and context of Versions - Added by Eric Voisard about 14 years ago

There is an interesting thread about the Versions vs Milestones question:

http://www.redmine.org/boards/1/topics/214

It should eventually lead to a plugin that redefines "version" and add Phases and Milestones management to Redmine.

Eric

(1-2/2)

Project

General

Profile

Redmine