# Bug OP-11144 - Different search result order in global search and work packages relations search

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-11144

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module |  |
| Target versions | 12.3.2 |
| Observed in versions |  |
| Sprint | 12.3.2 |
| Backlog bucket |  |
| Bug found in version (deprecated) |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

### Steps to reproduce

1.  In the global search the found work packages are sorted by `updatedAt`
2.  In the other work packages searches the found work packages are sorted by ID.

### What is the buggy behavior?

*   The different work packages searches have a different order.
*   It is very hard to find the correct work package if it is ordered by ID.

### What is the expected behavior?

1.  All work package searchers sort by `updatedAt`
    *   [ ] Setting relations
    *   [ ] Setting the parent
    *   [ ] Setting children
    *   [ ] Linking work packages in rich text field using the # and ## syntax