Transfering ownership of repo with issues in a project board to another org breaks project board columns #13224

New Issue

GiteaMirror · 2025-11-02T10:35:27-06:00

GiteaMirror commented

2025-11-02 10:35:27 -06:00

Originally created by @gira0 on GitHub (Jul 2, 2024).

Description

Hello everyone, I've noticed that when I move repositories that currently has issues in the project board to another organization, the project board still has the issues from the moved repo which now kinda break the columns they are in. Sometimes other issues can't be moved in or out of the bugged columns. The only solution I currently have is to go to the moved repositories and edit the issues so they don't have the project board referenced there.

I think a solution would be that if you transfer ownership to another organization that all issues in that repo get their project board reference removed and that this would be mentioned in the warning.

I've replicated the issue on the demo instance, you can find my bugged project board here: https://gitea.com/aurora-testorg1/-/projects/3256

If you need any further information of testing from my side, please let me know!

Gitea Version

1.22.0

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

(When my mouse goes to the top left I'm reloading the website)

Git Version

2.43.5

Operating System

RedHat 8.10

How are you running Gitea?

I've replicated this on my local instance (release downloaded from github) and on demo.gitea.com

Database

PostgreSQL

Originally created by @gira0 on GitHub (Jul 2, 2024). ### Description Hello everyone, I've noticed that when I move repositories that currently has issues in the project board to another organization, the project board still has the issues from the moved repo which now kinda break the columns they are in. Sometimes other issues can't be moved in or out of the bugged columns. The only solution I currently have is to go to the moved repositories and edit the issues so they don't have the project board referenced there. I think a solution would be that if you transfer ownership to another organization that all issues in that repo get their project board reference removed and that this would be mentioned in the warning. I've replicated the issue on the demo instance, you can find my bugged project board here: https://gitea.com/aurora-testorg1/-/projects/3256 If you need any further information of testing from my side, please let me know! ### Gitea Version 1.22.0 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots ![ezgif-4-387a0728e5](https://github.com/go-gitea/gitea/assets/19488367/5c9efbdb-b9b8-4a15-9a1c-81428c543999) (When my mouse goes to the top left I'm reloading the website) ### Git Version 2.43.5 ### Operating System RedHat 8.10 ### How are you running Gitea? I've replicated this on my local instance (release downloaded from github) and on demo.gitea.com ### Database PostgreSQL

GiteaMirror added the type/bug label 2025-11-02 10:35:27 -06:00

GiteaMirror closed this issue

2025-11-02 10:35:27 -06:00

GiteaMirror commented

2025-11-02 10:35:28 -06:00

@lunny commented on GitHub (Aug 13, 2024):

Fixed by #31770

@lunny commented on GitHub (Aug 13, 2024): Fixed by #31770

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#13224