Redmine

Why not just copy the issue and assign it to another milestone? The issues can be related to each other. After all, applying a patch to a separate version really is a separate issue to be tackled. Would that solve your problem?

I also second this feature. Mainly for custom fields. Our management team would like us to assign multiple values for a given field. They would also like the ability to select multiple catagories for example.

Another item similar to this would be related projects. So for example if we create a ticket under our main project. They would like us to associate the sub projects that the ticket applies. Basically the same concept as relating a ticket, but allowing related projects so they they can group together. For example if there is a bug in 1 project, that bug may affect other projects and they would like to have that association so that they know which projects are affected by that bug.

IMHO It's not good idea. Issue should be assigned only to one version/milestone at the time. Otherwise it will mess up time estimates and other statisics. If you set estimated time for a shared issue for example to 40 hours and asign it to two versions/milestones, you will see you need 2x 40 hours of homanwork to fix it, which is nonsense. The better idea IMHO is to create just second issue and link t to the original issue, so you can trac issue in both versions/milestones at the same time. Also, sometimes you see that issue can't be finished in time to be included in version/milestone, so you simply reassign it to the second version/milestone, and all times are autimaticaly recalculated, ok?

That's understandable from that perspective. But in our case we have custom fields that we need to be able to select multiple values for. I'm not worried about time management. This is mainly so we can assign various things that management wants us to group together.