# Feature NEX-171 - UX: Improving relevance of suggested work packages when linking

Project: Stream Nextcloud app "OpenProject Integration"
Status: closed
URL: https://community.openproject.org/work_packages/NEX-171

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Nextcloud Integration 2.2.0 |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

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

## Estimates and progress

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

## Description

*   When searching for a work package in order to link it to a file
*   And there are multiple hits (work packages suggested)


*   [ ] Then I want to see those hits first that got updated last as those are most likely the most relevant candidates to link to.
*   [ ] Same applies to the global search in Nextcloud when the search integration with OpenProject is activated.
*   [ ] Also the already linked work packages for a file should (after a full page reload) ordered by updated\_at descending.