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

Guest / tester issue reporting #2684

Closed
hubyhuby opened this issue Oct 10, 2017 · 7 comments
Closed

Guest / tester issue reporting #2684

hubyhuby opened this issue Oct 10, 2017 · 7 comments
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@hubyhuby
Copy link

hubyhuby commented Oct 10, 2017

I am in a use case scenario, where I want the testers to test my software but not to download my code. Imagine a company making games, doesn t want its tester to download the source code.

In Gitlab I can set a guest user on a specific project. (maybe the equivalent of Collaborators.)
The Guest user has only the right to post Bugs and issues. But cannot see the files / code on the repository.

So I tried all kind of configuration, such as colaborator and team (in private projects).
But in the end I cannot get to have a user who can only post issues.

With this team configuration I thought it would work. If you can t see the code but write , then you should be able to post issues.right? ;) But it doesn t work. In this case there is no "New issue" button, and when I click on an issue I get a 404 error

screenshot at 2017-10-10 15-59-23

PS: tried with gogs no luck aswell (less functionalities aswell)

Gitea 1.2RC3

@hubyhuby
Copy link
Author

Guest view in Gitlab for example:

screenshot at 2017-10-10 18-43-59

@hubyhuby hubyhuby changed the title Guest issue reporting Guest / tester issue reporting Oct 10, 2017
@Morlinest
Copy link
Member

Morlinest commented Oct 11, 2017

What version are you using? I've tried it on try.gitea.io just now. Public org, private repo, team only with issues and wiki enabled for read:
image

@Morlinest
Copy link
Member

Also working with your setup (write access, everything except Code enabled)

image

@hubyhuby
Copy link
Author

hubyhuby commented Oct 11, 2017

Hi @Morlinest , thanks for your answer. That s exactly what I would like to get ;) Better looking than 404 :D
What I basically do then is try to connect with a user of the team defined, but I only got 404. That s the reason I thought the feature didn t exist. Now I have hope !!!
I am trying and trying again...but no sucess from that side of the internet...

What do you mean by "Public org," and "team only", where do you find those aprameters ?
I have a "customer team" with the previous parameters set,

bug

Finally I cannot get in the admin of "try.gitea.io" to try it out....

@Morlinest
Copy link
Member

Morlinest commented Oct 11, 2017

@hubyhuby I see your problem from screenshot. You have to add repositories to your team. Now there is bug when you see every repository (in repository list, dashboard, ...) in organization even you shouldn't as you don't have rights to do anything with repo (mentioned in few issues, #2689 should fix it).

I was talking about my setup, nothing important now.

@jonasfranz
Copy link
Member

Bes sure that you are using the latest release or the latest master build since there was a bug which enabled issues only useres to fork the repository and gain access to the code.

@hubyhuby
Copy link
Author

hubyhuby commented Oct 11, 2017

Yeah ! got it to work. Thanks a lot
So now maybe one little comment:

  • The way you display "0 repository" is a link, which is counter intuitive. Because the behavior of such link every where else is to bring you to another page... Which in this case means AWAY from the team configuration page. Samething for "1 users"
    Therefore when you arrive on this page, you think there is only one parameter to a team, which is "members"'

guiteam

@lunny lunny added the type/question Issue needs no code to be fixed, only a description on how to fix it yourself. label Oct 12, 2017
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

4 participants