Issue transitions between multiple release

[NSantagostino]

Hi there,

I would like to clone issues that are still open when a release cycle ends from a board to another by keeeping the tickets IDs and ensuring that the status transitions that may occur in the late one won't be reflected back to first board. 

Ideally we would like to have this conditions covered: 

1. One Project space for the Product
2. Multiple Kanban board for each major release
3. Each Kanban board should be "freezed" at the end of the cycle and:
   1. Opened Issues should show up in the next board
   2. The issue status should not change any more in former board, for example if the issue was in progress in release 3.0, it should not change status if in release 4.0 will be set to close. 
4. The IDs should stay the same or automatically linked to original issue.

Any suggestion would be really appreciated, thank you.