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?
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!