Note
We've packed up and moved from Confluence to Discourse to bring you a better, more interactive space. Out of courtesy we didn't migrate your user account so - you will have to signup again
The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
When an issue (Story or Bug) is added to an epic in Jira Cloud, the issue became a sub-task on the remote Jira server. This happens only recently, perhaps since start of 2022.
Epic.send() & Epic.receive() is used in the connection scripts for Jira Cloud while
Epic.sendEpicFirst() & Epic.receive() is used in the connection scripts for Jira server (with Epic.groovy script added to the server).
Why did the issue type change from Story/Bug to sub-task when it's added to an epic?
Thanks!