Skip to content

[FEAT] Allow moving a work item to another project #171

Description

@martian56

Type / Priority

Feature / Medium

Summary

A work item is permanently bound to the project it was created in; it cannot be moved to another project.

Current state (evidence)

  • api/internal/store/issue.go has no move method, service/issue.go Update never changes project_id, no move route exists in router.go, and issueService.ts has no move call.

Proposed scope

Add a service method that re-parents the issue to another project in the same workspace, allocates a new sequence_id, and resets/maps project-scoped references (state/labels/assignees that don't exist in the target). Expose POST .../issues/:pk/move/ and a "Move to project" UI action.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions