Feature #724

change "versions" to "milestones"

Added by chris mcharg about 9 years ago. Updated 10 months ago.

Status:NewStart date:2008-02-22
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:Candidate for next major release
Resolution:

Description

Redmine can be used for tracking in many different types of projects, but grouping tickets by "version" does not make sense in many situations. I feel that the term milestone is a lot more inclusive, allowing for more flexibility. Its easy to have a version/release as a milestone, but the opposite doesn't really make sense.

I think it would be great if "versions" could be renamed to "milestones."

"Versions" could be added as a separate item, but I guess it might not be needed as Redmine has custom fields.

This would help with #723 too.


Related issues

Related to Redmine - Feature #374: Support for milestones/iterations as part of projects New
Related to Redmine - Feature #13387: Improving Redmine's version model (not just milestones) New
Related to Redmine - Feature #17907: Give 'version' another meaning New
Duplicated by Redmine - Feature #4178: Optimize Redmine for any project, not just software dev (... Closed 2009-11-06

History

#1 Updated by Nikolay Solakov about 9 years ago

Hi,
I think you're right. But on the other side, Redmine is translatable, mean that you can change .yml files as you like.
If I want something like you, I change the .yml file. Thus everybody is pleased. :)

Regards,
Nikolay

#2 Updated by chris mcharg about 9 years ago

Thanks for the respsose Nikolay.

I know what you mean about it being translatable, but shouldn't we aim for the best out of the box...?

#3 Updated by Nikolay Solakov about 9 years ago

I totally agree with you.
But "out of the box" is different for every user of Redmine.
There will be always people who don't like this or that label somewhere :)

Regards,
Nikolay

#4 Updated by Henrique Bastos almost 9 years ago

I made that translation, and the user experience is fine.
But, IMHO the Version in redmine works semantically as Milestones, so why don't just "fix it"? An enumerator custom field for Version works great.
Then it would be great if Sprints could extends Milestones. The difference is that Sprints can group issues from all projects or issues from a specific project tree (Base Proj, Sub Proj 1, Sub Proj 2...)

#5 Updated by Ве Fio about 8 years ago

Nikolay Solakov wrote:

I totally agree with you.
But "out of the box" is different for every user of Redmine.
There will be always people who don't like this or that label somewhere :)

Redmine is good for all kinds of projects. A version is a kind of milestone. A software developer knows this. But not all milestones are versions. I set up a project in a clumsy way because I ignored "Versions".

Trac has "Milestones" and "Versions". Redmine "Versions" are like Trac "Milestones". It can be confusing. Redmine sometimes talks about "milestones" too.

#6 Updated by Eric Voisard over 7 years ago

I'm all for the differentiation between Versions and Milestones. Version really is software development specific, and the difference between Redmine and all other FOSS PMS is that it is more generic and more open to non-software projects. That's in my POW what make its power (and that's why we chose it).

Maybe versions and milestones are semantically the same things in software development, but version has no meaning in many other kinds of projects. A milestone is a place on a timeline (there's is a chronology). A version well is a version of something. There can be Version 1 and Version 2, but there can also be Version Lite and Version Premium...

Versions can be worked on in parallel while at some point you shouldn't change the early initiation phase of a project once you've reached its closing phase.

We use Redmine for software and non-software projects. Translating Version to Milestone wouldn't fit well with software projects, and Version doesn't fit well with non-software projects. To me, they really are different things...

Maybe I'm missing something about the usage of Versions in Redmine, but practically, I don't see how to properly handle the Milestones of a project with this functionality, and I don't think it's just a matter of naming...

There is an interesting discussion about that in the forum:
"Versions vs Milestones" http://www.redmine.org/boards/1/topics/214

Redmine is great anyway! Thanks!
Eric

#7 Updated by Daniel Felix over 4 years ago

Hi,

well I don't think that versions or milestones mutually exclude each others.

In my opinion, those are parallel or hierarchical items, which could extend each other quite good.

Some renaming could be done in each installation itself in your locals.

#8 Updated by Matthew Houston over 4 years ago

I see there are a couple of feature requests / threads relating to this particular functionality. I would also like to request it. The version functionality kind of fulfils what is required, though we don't use Redmine for software development at all the terminology really throws non-technical users.

#9 Updated by Joshua DeClercq about 4 years ago

Since I'm evangelizing it elsewhere, I'll do it here too: I'm proposing a major expansion of version functionality in Redmine that would address all the needs described in all of these different change requests, and then some. Have a look and let me know if it hits all the right spots! #13387

#10 Updated by Mischa The Evil about 2 years ago

#11 Updated by Ebrahim Mohammadi almost 2 years ago

I wonder why such an obvious improvement hasn't been considered and applied yet.

#12 Updated by Robert Schneider almost 2 years ago

Ebrahim Mohammadi wrote:

I wonder why such an obvious improvement hasn't been considered and applied yet.

True. Unfortunately, only few people know what happens behind the scenes...

#13 Updated by Go MAEDA 11 months ago

  • Target version set to Candidate for next major release

#14 Updated by shakib a 10 months ago

Hi,

Please notice that milestone is a method of measuring the distance passed not the distance to be passed in a planed road map. Please refer to Wikipedia for more info.

Also available in: Atom PDF