# Bug AGILE-226 - Moving read-only work package between sprints triggers an error

Project: Stream agile
Status: closed
URL: https://community.openproject.org/work_packages/AGILE-226

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module | Modules and project features / Backlogs |
| Target versions | 17.7.0 |
| Observed in versions | 17.3.0 |
| Sprint | Sprint 7 |
| Backlog bucket |  |
| Bug found in version (deprecated) | 17.3.x |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Alexander Coles |
| Designer | Julia Racsko |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

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

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Effort (shirt size) |  |
| Work |  |
| Labor costs |  |

## Description

### Steps to reproduce

1.  Log in
    
2.  Go to a project/Backlogs
    
3.  Have at least two sprints
    
4.  In one of the sprints, have a read-only work package (for example, in Rejected status which is defined as read-only here [https://qa.openproject-stage.com/statuses/14/edit)](https://qa.openproject-stage.com/statuses/14/edit\))
    
5.  Move the work package from one sprint to another by drag and drop
    

### What is the buggy behavior?

*   The work package can be dragged and dropped but triggers an error message
    

<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/920749/content">

### What is the expected behavior?

Read-only statuses are an Enterprise feature, so this applies only where an Enterprise token is active. In Community, `Status#is_readonly` always returns false and nothing below changes.

A work package in a read-only status must not be offered a move the server would refuse. The server refuses every move that writes `sprint_id` or `backlog_bucket_id` — that is, every move between containers. Reordering within its own list writes neither, so it stays available:

1.  The card stays draggable, but only for reordering within its own list. It can be picked up and dropped at a new position in the same sprint, the same backlog bucket, or the inbox it already sits in.&nbsp;
    
2.  Other containers do not accept it: dragging it over a different sprint, bucket or the inbox offers no drop position, and releasing there leaves the card where it started. A red outline is shown around the other container as a visual cue (additional styling will be introduced in a future WP).
    
3.  Its action menu keeps the &quot;Move to position&quot; submenu — all within-list positional moves still work — but shows no cross-container actions: no &quot;Move to sprint&quot;, no &quot;Move to backlog bucket&quot;, no &quot;Move to backlog inbox&quot;.
    
4.  The rest of the card menu is unaffected: &quot;Open details view&quot;, &quot;Open fullscreen view&quot;, &quot;Copy URL to clipboard&quot; and &quot;Copy work package ID&quot; all still work, and the card stays focusable and openable by keyboard.
    
5.  Cards around it are unaffected. A movable card sharing the list keeps its drag and its full move menu, including cross-container moves and positional moves that place it above or below the read-only card.
    

### Notes

Movement is gated on two independent factors, and both must hold: the `manage_sprint_items` permission, which is resolved against the page&#x27;s project and so answers the same for every card on the page, and the work package&#x27;s own status. Only the second is new.

The UI offers exactly what the server accepts. Position is not a work package attribute — it is absent from the permitted params, the API schema and the journal, and it is written by `move_after` after contract validation has passed — so no contract rejects a within-list reorder, while every cross-container move writes `sprint_id` or `backlog_bucket_id` and is refused. The rule a user has to learn stays a single one: a read-only card is frozen in its container, not in its order.

An earlier revision of this ticket froze the card entirely (no drag, no positional moves). That assumption was revised on 2026-08-03: within-list reordering is now expected to keep working.

Read-only cards remain drop targets and still count as rows of their list. That is deliberate: without it, a movable card whose only neighbours are read-only would lose positional moves the server would have accepted.

### Environment information

**Core build**

[e39dca11c53104041037425b29ee8872207b4e2e](https://qa.openproject-stage.com/external_redirect?url=https%3A%2F%2Fgithub.com%2Fopf%2Fopenproject%2Fcommit%2Fe39dca11c53104041037425b29ee8872207b4e2e)

**Product version**

[2489872ee97cd37949deabe02e735629caf76783](https://qa.openproject-stage.com/external_redirect?url=https%3A%2F%2Fgithub.com%2Fopf%2Fsaas-openproject%2Fcommit%2F2489872ee97cd37949deabe02e735629caf76783)

**Core version**

OpenProject 17.4.0
