Can you please add functionality to have multiple target versions for ticket (or even everywhere)?

What do you mean ?
I don't understand the need.
An item is treated and / or delivered on one only version.
It there should be multiple target versions for an item, then the item should be split.

If you have component then target versions can be multiple because component need to be tested with different versions/products, so we need to have ability to add projects for which this is pertinent

I'm not sure it is the good way to manage this.
In fact, when updating some component concerned by several versions, then you have to "merge" changes between branches. My advise is to copy the ticket with new ticket type => Merge (and set origin ticket as Origin).
This way you will really follow up merges, and when they are done, not just what should be done...

This is not merge between branches. Let's say bug found in version 2.5. But after test it been confirmed that version 2.6 have it as well. We have customers on both versions, so it need to be fixed in both versions, sometimes even in 3 versions.

Hi Ekolossov,

I see your point. From my pov, you might have two Tickets "Fix bug in V2.5" and "Fix bug in V2.6". You could simple open a Ticket for each task.

We have nearly same situation: Different versions on different enviroments in different countries. May be a core module has an bug and has to be deployed, we simplyfied things, we writing a runbook and attach this to the ticket.

But to be honest, I try to harmonize my enviroments and version. This is better solution on the long run.

Klaus

I can add that the ticket genereted by our CRM system automatically, so it is not possible to create multiple tickets

What's about the nice copy feature of Projector? You can refer / link the Tickets and it's done.

It will break thie process and will produce 4times more tickets