As of now we have reviewed the functionality which is available for projects in Redmine. But, 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 the main thing that I would like to share with you in this chapter is my experience of what should be done and what should be avoided. Earlier, while reviewing different available functions, I was trying to give you some hints and advices. In this topic, I would like to list some best practices for better projectmaintenance. So let's get started:
You should not expect your users to learn all the issue filter functionality and to configure it to their needs on their own. Where possible you should ensure that they feel comfortable while browsing your issue lists. This is not only about your customers but also, and especially, about your project members.
Let's review some examples of custom queries. Some of them, possibly, will be useful for you, others, I hope, will give you an idea about custom queries you may need:
Name |
Filters | |
---|---|---|
Field/Option |
Condition/Value | |
My open issues |
Status |
|
Assigned to |
| |
My open issues in the next version |
Status |
|
Assigned to |
| |
Target version |
" | |
Issues watched by me |
Status |
|
Watcher |
| |
Unassigned issues |
Status |
|
Assignee |
none | |
New features in the next version |
Tracker |
|
Target version |
| |
Changelog for current stable version |
Target version |
|
Sort |
| |
Roadmap |
Status |
|
Group results by |
| |
Issues grouped by assignees and sorted by priority |
Status |
|
Group results by |
| |
Sort |
| |
Issues by trackers sorted by status |
Group results by |
|
|