Mention completion should complete with people outside the organisation #1491

New Issue

GiteaMirror · 2025-11-02T04:02:18-06:00

GiteaMirror commented

2025-11-02 04:02:18 -06:00

Originally created by @kolaente on GitHub (Feb 1, 2018).

When mentioning someone, the mention completion only mentions people inside my own org (or only the owner, if I'm in a user repository). Thats probaly fine for private repos, but for public ones?

Ideally, it should autocomplete
a) everyone, if the current issue is in a public repo
b) only people with access to the repo, if its a private one. This would include team members of an organisation (I think actually everyone within an organisation who is in a team with read access + issuetracker/pr) and added members via settings (because user repos can also add members for collaboration).

\cc @harryxu

Originally created by @kolaente on GitHub (Feb 1, 2018). When mentioning someone, the mention completion only mentions people inside my own org (or only the owner, if I'm in a user repository). Thats probaly fine for private repos, but for public ones? Ideally, it should autocomplete a) everyone, if the current issue is in a public repo b) only people with access to the repo, if its a private one. This would include team members of an organisation (I think actually everyone within an organisation who is in a team with read access + issuetracker/pr) and added members via settings (because user repos can also add members for collaboration). \cc @harryxu

GiteaMirror added the issue/confirmed type/enhancement labels 2025-11-02 04:02:18 -06:00

GiteaMirror commented

2025-11-02 04:02:18 -06:00

@harryxu commented on GitHub (Feb 2, 2018):

In #3136 , I fetch people list from current org's Assignees.

May be we should add an api to fetch any people to Mention? But Im not good at go lang. Can anyone help to implement this api?

@harryxu commented on GitHub (Feb 2, 2018): In #3136 , I fetch people list from current org's Assignees. May be we should add an api to fetch any people to Mention? But Im not good at go lang. Can anyone help to implement this api?

GiteaMirror commented

2025-11-02 04:02:19 -06:00

@bkcsoft commented on GitHub (Feb 10, 2018):

You can sort the list by relevance. First people in the Issue/PR, then Project members, then Organization members, then Globally. WDYT?

EDIT: Forgot "participants" as first prio.

@bkcsoft commented on GitHub (Feb 10, 2018): You can sort the list by relevance. First people in the Issue/PR, then Project members, then Organization members, then Globally. WDYT? EDIT: Forgot "participants" as first prio.

GiteaMirror commented

2025-11-02 04:02:19 -06:00

@bkcsoft commented on GitHub (Feb 10, 2018):

Using participants as the first set can potentially save on AJAX-calls as well, since we already have the participant list loaded in the page ;)

@bkcsoft commented on GitHub (Feb 10, 2018): Using participants as the first set can potentially save on AJAX-calls as well, since we already have the participant list loaded in the page ;)

GiteaMirror commented

2025-11-02 04:02:19 -06:00

@stale[bot] commented on GitHub (Feb 8, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 8, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:02:19 -06:00

@worthy7 commented on GitHub (Sep 4, 2019):

Hey everyone,

Just started using Gitea a bit more, and wanted to reference my boss in a PR but couldn't.
It doesn't make sense to restrict it to teams, because what about individual repositories? Then there is literally no use for the mention feature because there will never be anyone.

Needs to just copy the github functionality, let the user decide who they want to mention without restrictions.
For massive companies, people with the same last name etc (or username) perhaps just add some kind of (Project/Organization/team) tags to the mention dropdown, so it's dead clear.

Cheers

@worthy7 commented on GitHub (Sep 4, 2019): Hey everyone, Just started using Gitea a bit more, and wanted to reference my boss in a PR but couldn't. It doesn't make sense to restrict it to teams, because what about individual repositories? Then there is literally no use for the mention feature because there will never be anyone. Needs to just copy the github functionality, let the user decide who they want to mention without restrictions. For massive companies, people with the same last name etc (or username) perhaps just add some kind of (Project/Organization/team) tags to the mention dropdown, so it's dead clear. Cheers

GiteaMirror commented

2025-11-02 04:02:19 -06:00

@worthy7 commented on GitHub (Sep 5, 2019):

I cannot even mention someone when I am the owner. This is really a bug and needs fixing please. This means that owners cannot ever mention anyone who isn't an owner - even if they are in another team too!

@harryxu Could you perhaps just change your code so that it includes all teams in the dropdown and make a quick PR?

@worthy7 commented on GitHub (Sep 5, 2019): ![image](https://user-images.githubusercontent.com/4762399/64307163-38868d00-cfd0-11e9-9955-ad20d2a5d690.png) I cannot even mention someone when I am the owner. This is really a bug and needs fixing please. This means that owners cannot ever mention anyone who isn't an owner - even if they are in another team too! @harryxu Could you perhaps just change your code so that it includes all teams in the dropdown and make a quick PR?

GiteaMirror commented

2025-11-02 04:02:20 -06:00

@lunny commented on GitHub (Sep 5, 2019):

I think maybe we could have an option to allow mention any people on that site on app.ini or not.

@lunny commented on GitHub (Sep 5, 2019): I think maybe we could have an option to allow mention any people on that site on app.ini or not.

GiteaMirror commented

2025-11-02 04:02:20 -06:00

@worthy7 commented on GitHub (Oct 5, 2019):

Looking at this again, assuming the system is not multi-tenant, then it should just work like Github, probably showing everyone, and proritizing based on... 1) The contexts participants (issue/PR), 2) Everyone in the Org (if applicable) and 3) everyone.

I don't see any reason why it needs to be limited to teams in the first place - it's not a secret who the other users are

@worthy7 commented on GitHub (Oct 5, 2019): Looking at this again, assuming the system is not multi-tenant, then it should just work like Github, probably showing everyone, and proritizing based on... 1) The contexts participants (issue/PR), 2) Everyone in the Org (if applicable) and 3) everyone. I don't see any reason why it needs to be limited to teams in the first place - it's not a secret who the other users are

GiteaMirror commented

2025-11-02 04:02:20 -06:00

@mdbergmann commented on GitHub (Aug 4, 2020):

This is also a problem in our company where we installed Gitea.
Would be great if this could be fixed.

@mdbergmann commented on GitHub (Aug 4, 2020): This is also a problem in our company where we installed Gitea. Would be great if this could be fixed.

GiteaMirror commented

2025-11-02 04:02:20 -06:00

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

I think we can do that according if the repository is a public one or a private one.

For public repository, you can mention anyone on this Gitea instance
For limit/private repositories, you can mention those who have the read permissions on this repository

@lunny commented on GitHub (Aug 13, 2020): I think we can do that according if the repository is a public one or a private one. - For public repository, you can mention anyone on this Gitea instance - For limit/private repositories, you can mention those who have the read permissions on this repository

GiteaMirror commented

2025-11-02 04:02:21 -06:00

@iarepandemonium commented on GitHub (Nov 20, 2020):

Adding on this, my team has people who review pull requests without exclusive access to the code, and it would be nice to mention anyone within the organization because I have people assigned as reviewers who only look at the code in the PR not in the whole repo.

@iarepandemonium commented on GitHub (Nov 20, 2020): Adding on this, my team has people who review pull requests without exclusive access to the code, and it would be nice to mention anyone within the organization because I have people assigned as reviewers who only look at the code in the PR not in the whole repo.

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#1491