I have projects where a large series (35-ish) of issues is recreated for each of a large number tasks (35-ish, just coincidentally) for a matrix of about 35^2 issues. Setting up one string of issues and all dependencies and then copying them seems like a very efficient way to create the issue matrix.
Unfortunately, the relational structure within one string of issues is broken into a "copy" structure on replication, which obfuscates the relations between the issues in the duplicated task strings.
Would it be possible to copy the relative issue structure if two or more related issues are copied simultaneously and make the "copy of" relation optional, add it to the copied relations, or skip it?
I have projects where a large series (35-ish) of issues is recreated for each of a large number tasks (35-ish, just coincidentally) for a matrix of about 35^2 issues. Setting up one string of issues and all dependencies and then copying them seems like a very efficient way to create the issue matrix.
Unfortunately, the relational structure within one string of issues is broken into a "copy" structure on replication, which obfuscates the relations between the issues in the duplicated task strings.
Would it be possible to copy the relative issue structure if two or more related issues are copied simultaneously and make the "copy of" relation optional, add it to the copied relations, or skip it?