You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes for unreachable project issues when transfer repository from organization (go-gitea#31770)
When transferring repositories that have issues linked to a project
board to another organization, the issues remain associated with the
original project board. This causes the columns in the project board to
become bugged, making it difficult to move other issues in or out of the
affected columns. As a solution, I removed the issue relations since the
other organization does not have this project table.
Fix for go-gitea#31538
Co-authored-by: Jason Song <[email protected]>
Copy file name to clipboardExpand all lines: options/locale/locale_en-US.ini
+1
Original file line number
Diff line number
Diff line change
@@ -2173,6 +2173,7 @@ settings.transfer_in_progress = There is currently an ongoing transfer. Please c
2173
2173
settings.transfer_notices_1 = - You will lose access to the repository if you transfer it to an individual user.
2174
2174
settings.transfer_notices_2 = - You will keep access to the repository if you transfer it to an organization that you (co-)own.
2175
2175
settings.transfer_notices_3 = - If the repository is private and is transferred to an individual user, this action makes sure that the user does have at least read permission (and changes permissions if necessary).
2176
+
settings.transfer_notices_4 = - If the repository belongs to an organization, and you transfer it to another organization or individual, you will lose the links between the repository's issues and the organization's project board.
2176
2177
settings.transfer_owner = New Owner
2177
2178
settings.transfer_perform = Perform Transfer
2178
2179
settings.transfer_started = This repository has been marked for transfer and awaits confirmation from "%s"
0 commit comments