It appears to me that cloned issues do not receive the source issue's security level.

[Brian Bishop]

Is that expected behavior, and can it be changed (either via configuration or patch)?

[Brian Bishop]

Yep, that was it. I've since resorted to creating my own custom script, which is better in the long run because I have a lot of things I'll need to do to the new issue, cloning aside. Adding a boilerplate comment, setting some custom fields, etc. BTW, I had to wait 24 hours to post this - how do I earn 25 points please?

[JamieA]

there was an issue with cloning the security level which was fixed, but not sure if the fix is in 3.1.3. Is that the reason you want the sourceIssue?

[Brian Bishop]

Ah, sorry - I had forgotten about my original comment on the old post. In that moment, I was looking at the problem form the perspective of: how can I get access to the newly created issue (so as to have more control over it)? In this instance, I had abandoned the idea of using 'additional actions' to modify the newly created issue, and instead was relying on the clone feature's ability to copy everything about the source issue. I'm using 3.0.16....another sorry, I see there is an update to 3.1.3 which I will now get and try.

[JamieA]

It's hard to respond when you add a similar comment to multiple question. What version of the plugin are you using?