Redmine

Agreed. This will help flexibility in naming trackers. For
code management projects makes no sense to have trackers talking
about progress of contracts, service calls, etc.

+1 I think it will be useful feature.

+1 from me too.

Done in r920.
Trackers can now be selected on project settings.
Note that if a tracker is unselected for a given project, existing
issues assigned to this tracker are not removed. They will still
appear on the issue list.

Hi,
On Issues page, when I pick Tracker filter, the trackers are
not filtered by the current project.

Thanks,
Nikolay

Yes, I didn't want to remove unused trackers from the filter
list because:
- there may be existing issues that are assigned to them and
it can be usefull to list them
- subprojects may use these trackers (and the issue list let
you show the subprojects issues)

But I'm open to any suggestion. What do you think ?

Well, maybe:
- when I unselect a tracker from project, the tracker seems
to be of no use any more for that project
- when unselecting a tracker from the project settings, there
should be a check if issues assigned to this tracker exist in
the project
- if so, Redmine should not allow this. The user would have
to manually move the issues to another tracker.

This is my understanding of the issue :)

P.S.: Or, you can implement the two ways and put a global setting
for Allowing existing issues assigned to tracker when unselecting
it.

Regards,
Nikolay