Merge branch 'NIKU-SINGH/gitlab-NIKU-SINGH-master-patch-05057' into 'master'

Update sorting issue boards docs (reapply community contribution)

See merge request gitlab-org/gitlab!72628

doc/user/project/issue_board.md

@@ -197,21 +197,22 @@ card includes:
 Users with the [Reporter and higher roles](../permissions.md) can use all the functionality of the
 issue board feature to create or delete lists. They can also drag issues from one list to another.
 
-## How GitLab orders issues in a list
-
-When visiting a board, issues appear ordered in any list. You're able to change
-that order by dragging the issues. The changed order is saved, so that anybody who visits the same
-board later sees the reordering, with some exceptions.
+## Ordering issues in a list
 
 When an issue is created, the system assigns a relative order value that is greater than the maximum value
 of that issue's project or root group. This means the issue will be at the bottom of any issue list that
 it appears in.
 
+When you visit a board, issues appear ordered in any list. You're able to change
+that order by dragging the issues. The changed order is saved, so that anybody who visits the same
+board later sees the reordering, with some exceptions.
+
 Any time you drag and reorder the issue, its relative order value changes accordingly.
 Then, any time that issue appears in any board, the ordering is done according to
 the updated relative order value. If a user in your GitLab instance
 drags issue `A` above issue `B`, the ordering is maintained when these two issues are subsequently
-loaded in any board in the same instance. This could be a different project board or a different group
+loaded in any board in the same instance.
+This could be a different project board or a different group
 board, for example.
 
 This ordering also affects [issue lists](issues/sorting_issue_lists.md).

doc/user/project/issues/sorting_issue_lists.md

@@ -23,7 +23,7 @@ The available sorting options can change based on the context of the list.
 For sorting by issue priority, see [Label Priority](../labels.md#label-priority).
 
 In group and project issue lists, it is also possible to order issues manually,
-similar to [issue boards](../issue_board.md#how-gitlab-orders-issues-in-a-list).
+similar to [issue boards](../issue_board.md#ordering-issues-in-a-list).
 
 ## Sorting by popularity
 
@@ -48,7 +48,7 @@ the updated relative order value is used for the ordering.
 So, if anyone drags issue `A` above issue `B` in your GitLab instance,
 this ordering is maintained whenever they appear together in any list.
 
-This ordering also affects [issue boards](../issue_board.md#how-gitlab-orders-issues-in-a-list).
+This ordering also affects [issue boards](../issue_board.md#ordering-issues-in-a-list).
 Changing the order in an issue list changes the ordering in an issue board,
 and vice versa.