Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

accepting or rejecting transfer to organization is disabled even when the user is the owner of repo and organization #26491

Closed
basilrabi opened this issue Aug 14, 2023 · 4 comments
Labels
issue/workaround it is or has a workaround type/bug

Comments

@basilrabi
Copy link

Description

I am the owner of a repository and at the same time, owner of an organization. When I transfer the ownership of the repository to the organization, the transfer is pending since it needs to be accepted first. However, the accept and reject buttons are greyed-out with a tool-tip showing "You do not have permission to Accept/Reject".

When I try this at https://try.gitea.io/, there is no confirmation needed and the transfer is done instantly.

Gitea Version

1.20.2

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Screenshot from 2023-08-14 20-03-35

Git Version

2.41.0

Operating System

Fedora 37

How are you running Gitea?

I used the binary version in the git release.

Database

PostgreSQL

@wxiaoguang
Copy link
Contributor

Could you try to create and join a team with this permissions?

image

@yp05327
Copy link
Contributor

yp05327 commented Aug 15, 2023

Did you update Gitea from the version before v1.11? And this org is created before you updated from 1.11.

@basilrabi
Copy link
Author

Could you try to create and join a team with this permissions?

image

Creating another team with this permission works. Thank you.

@basilrabi
Copy link
Author

Did you update Gitea from the version before v1.11? And this org is created before you updated from 1.11.

I came from version 1.19 but maybe the team was created prior to 1.11 but still, I'm the owner of the team and the owner of the repository so for me, creating another team is not needed. Anyway, the previous comment works.

@wxiaoguang wxiaoguang added the issue/workaround it is or has a workaround label Aug 20, 2023
wxiaoguang added a commit that referenced this issue Aug 29, 2023
Related to: #8312 #26491

In migration v109, we only added a new column `CanCreateOrgRepo` in Team
table, but not initial the value of it.
This may cause bug like #26491.

---------

Co-authored-by: wxiaoguang <[email protected]>
GiteaBot pushed a commit to GiteaBot/gitea that referenced this issue Aug 29, 2023
)

Related to: go-gitea#8312 go-gitea#26491

In migration v109, we only added a new column `CanCreateOrgRepo` in Team
table, but not initial the value of it.
This may cause bug like go-gitea#26491.

---------

Co-authored-by: wxiaoguang <[email protected]>
silverwind pushed a commit that referenced this issue Aug 29, 2023
…6791)

Backport #26683 by @yp05327

Related to: #8312 #26491

In migration v109, we only added a new column `CanCreateOrgRepo` in Team
table, but not initial the value of it.
This may cause bug like #26491.

Co-authored-by: yp05327 <[email protected]>
Co-authored-by: wxiaoguang <[email protected]>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/workaround it is or has a workaround type/bug
Projects
None yet
Development

No branches or pull requests

3 participants