# Feature OP-2489 - Decouple loading of activities from loading of work packages

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | High |
| Target versions | 5.0.4 |
| Sprint |  |
| Backlog bucket |  |
| 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 |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

Currently, a work package’s activities are loaded together with the work package. This applies to the front-end as well as the back end. But loading all of this at once, especially since loading the activities is slow and the complexity for doing it is O (n), we need to decouple the two.

**Acceptance criteria**

  - APIv3 work\_packages\#show no longer embeds the activities
  - The `work_packages/:id/activity` (and `project/:project_id/work_packages/details/:id/overview`) displays the work package overview information (the work package’s primary information) first. It then loads the activities in a separate request. There should be some indicator of progress (e.g. spinner) at the place where the activities will be rendered.
  - The separation also works on work package creation and update.
