Project maintenance best practices
As of now, we have reviewed the functionality that is available for projects in Redmine. However, in my opinion, it's not enough to learn what functionality is available. It's much more important to learn how to use it properly. So now, I would like to share some of my experience of what should be done and what should be avoided. In other words, in this section, I would like to list some best practices for better project maintenance. So let's go:
Always specify the target version when you close an issue, as it is used for the roadmap.
Have a future version added to the version list. If you are unsure what version name or number this will be then name it, for example, Next version. You can always change the name later. If no future version is available, a developer won't be able to select a value for the Target version field.
Note
Redmine developers use the following version names for future versions: Candidate for next major release and Candidate for next minor...
