Internal Server Error when Splitting an Issue

Rebecca Hylek

We recently migrated to Jira Cloud from our data center.  Prior to the migration we were able to split issues with no issues.  Today, although the split does complete, we see an Internal Server error pop up.  This is confusing to everyone and causes delays.  How can we prevent seeing that error?

Steps to re-create: 

NOTE: My role is Site and Company Admin, this happens for everyone splitting a story.

Open Project > Backlog > Created issue (User story; 8 pts) > Right click on issue > Split issue > Enter relevant information > Split

Image 1 - Error Message

Image 2 - Split story created after closing the error message

Iain Powrie

Hi Rebecca, 

One of our product owners raised this exact same issue with me today, issue was like for like to how you described it. I reached out to Atlassian support who confirmed and advised it was due to the issue link missing attributes in the database. 

Off the back of my case a bug report has been created Bug JIRACLOUD-80140. 
Proposed Workaround in this Bug report:
"Please contact Atlassian Support to verify if the issue is caused due to the "Split issue" issue link type from the logs and make the required changes to resolve the issue."