Our current situation: we have one big project with several development paths.

e.g. project A has a main development path and some variants (branches) A1, A2.
every branch has patches (=versions), e.g. A1.1, A1.2

graphical view:

A2 (=variant path)
 \
  \   | 

A2.1 * | A1 (=variant path)
\ | /
| /

• • A1.1 (=patch)	/	/

    A (=main dev. path)

the variant paths are our releases and will be published whereas the central path (A) is our internal development path.

ok, to speak in words of mantis:

• "A" would be a mantis project
• "A1", "A2" would be mantis sub projects (or just another project)
• "A1.1" would be a (target) version

so: we develop a feature (or fix a bug) in A and create an issue 123.
now we also want to apply this change to A1 and A2 and put it on the roadmap of A1.1 and A2.1. the sw change is the same and will just be merged into those releases, therefore we only need 1 central issue.

the problem is that we currently have to clone the issue to assign it to two projects to display it in both roadmaps (roadmap A1, roadmap A2).

it would be great to just assign 1 issue to more project/versions to avoid redundancy (duplicate issues by cloning, double maintenance work, etc...).