By default, creating a connection is for 1 to 1 project mapping, can a single connection be used for a N to N project mapping "properly" ?
e.g. even in Script mode, the first question is about the source & target projects, and even remains when doing an "Exalate" operation on the connection (with a custom script for N projects): it asks which ticket from project A (first selected during creation) you want, even though it works with any other issue key.
=> Can a single script connection be used for a list of N projects to sync with N projects on target properly/reliably (especially in case of migrations) ?
It sure seems so with the "mapping" features in the project keys etc.
By default, creating a connection is for 1 to 1 project mapping, can a single connection be used for a N to N project mapping "properly" ?
e.g. even in Script mode, the first question is about the source & target projects, and even remains when doing an "Exalate" operation on the connection (with a custom script for N projects): it asks which ticket from project A (first selected during creation) you want, even though it works with any other issue key.
=> Can a single script connection be used for a list of N projects to sync with N projects on target properly/reliably (especially in case of migrations) ?
It sure seems so with the "mapping" features in the project keys etc.