Missing information about "Split Issue" functionality on DC documentation

Issue Summary

DC documentation on the page below doesn't mention the Split Issue functionality:

https://confluence.atlassian.com/jirasoftwareserver/using-your-scrum-backlog-938845361.html

On Cloud documentation we have this:

Right-click an issue and select Split issue. You can split an issue in the Backlog or sprint sections, including any future sprints and any active sprint.

Splitting an issue is useful when an issue is so big that it's better to divide it into two or more issues to make work more manageable.

What happens when I split an issue?

• If you split an issue in the Scrum backlog, the new issue will be sent to the Backlog section.

• If you split an issue in one of the sprints (future or active), you can choose to send the new issue to either the Backlog, or a future or active sprint.

What happens to the issue details?

• The new issue will be of the same issue type as the original issue. For example, if you split a story into two or more issues, the new issues will also be stories.

• The new issue will have most of the same details stored in the original issue, including priority, component, and label.

• The issue details that won't be copied over include work log, comments, issue history, and issue links, though the original issue will be linked to the new issue.

• The new issue will have the summary that you entered upon splitting the issue.

• If the original issue has estimates, you'll be able to enter estimates for the new issues as well. You can also update the estimate of the original issue as necessary.

• The issue status also returns to the first step of the corresponding workflow, and the resolutions are cleared.

Cloud documentation (https://support.atlassian.com/jira-software-cloud/docs/use-your-scrum-backlog/) 

Steps to Reproduce

Not needed

Expected Results

Split Issue functionality properly documented.

Actual Results

We fail to mention it on https://confluence.atlassian.com/jirasoftwareserver/using-your-scrum-backlog-938845361.html

Workaround

The functionality is the same as Cloud as of Dec 2023 hence the Cloud docs can be used as reference.