Redmine

Etienne Massip wrote:

I don't understand your need, please be more descriptive.

If I had to guess, I'd say he uses a lot of trackers and wants to structure them so the initial tracker list isn't overwhelmingly long. Pick one tracker, and a separate drop-down refreshes with that tracker's children to choose from.

This resembles some other feature requests for custom fields that have different values depending on the values of other fields. If you think of a tracker as essentially a template (all it really is, anyway), this could let you relate several templates under a single parent, and then filter issues to view all trackers included in that family.

It'd be an interesting feature to see implemented, but for now it might be better to take advantage of subprojects. Let each subproject represent a parent tracker, and you can still have the same sorting/filtering control at the root project level (just filtering on Project instead of Tracker). I'd rather see this exact feature request overlooked in favor of the aforementioned interactive custom fields.