Automatically Linked References to gitea teams are not working as expected #14639

New Issue

GiteaMirror · 2025-11-02T11:18:35-06:00

GiteaMirror commented

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

Originally created by @mrcrsr on GitHub (Jun 24, 2025).

Description

I tested the creation of automatic linked references on our self hosted instance and found out, that the references to the project's teams are not working as described in the documentation.
I can reproduce the behaviour on the official demo.gitea.com instance.

Please see: https://demo.gitea.com/EXAMPLEorga/examplerepo#test-of-automatically-linked-references

Official documentation:

User, Team and Organization Mentions

When a text in the form @username is found and username matches the name of an existing user, a mention reference is created. This will be shown by changing the text into a link to said user's profile, an

Example:

@John, can you give this a look?

This is also valid for teams and organizations:

@Documenters, we need to plan for this. @CoolCompanyInc, this issue concerns us all!

Teams will receive mail notifications when appropriate, but whole organizations won't.

Commit messages do not produce user notifications.

I tried different things.

The spelling (case sensivity) for references to users and organizations seems not to matter.
But references to a team behave different:

references to a team must be prefixed with the organization and the spelling (of the organization) matters, and
it seems that the referenced teams must have access to the repository from where they get referenced

Please see the attached screenshot from the official Gitea test instance.

Gitea Version

1.24.0, Windows Server 2022, self hosted

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

Git Version

2.47.1.windows.2

Operating System

Windows Server 2022

How are you running Gitea?

Downloaded official Release, self hosted on Windows Server 2022
But reproducable on the official Gitea test instance: https://demo.gitea.com/EXAMPLEorga/examplerepo#test-of-automatically-linked-references

Database

MySQL/MariaDB

Originally created by @mrcrsr on GitHub (Jun 24, 2025). ### Description I tested the creation of automatic linked references on our self hosted instance and found out, that the references to the project's teams are not working as described in the [documentation](https://docs.gitea.com/usage/automatically-linked-references). [I can reproduce the behaviour on the official demo.gitea.com instance](https://demo.gitea.com/EXAMPLEorga/examplerepo#test-of-automatically-linked-references). Please see: [https://demo.gitea.com/EXAMPLEorga/examplerepo#test-of-automatically-linked-references](https://demo.gitea.com/EXAMPLEorga/examplerepo#test-of-automatically-linked-references) --- [Official documentation](https://docs.gitea.com/usage/automatically-linked-references): >## User, Team and Organization Mentions > >When a text in the form @username is found and username matches the name of an existing user, a mention reference is created. This will be shown by changing the text into a link to said user's profile, an > >Example: > >> @<wbr>John, can you give this a look? > >This is also valid for teams and organizations: > >> __@<wbr>Documenters__, we need to plan for this. @<wbr>CoolCompanyInc, this issue concerns us all! > >Teams will receive mail notifications when appropriate, but whole organizations won't. > >Commit messages do not produce user notifications. --- I tried different things. The spelling (case sensivity) for references to _users_ and _organizations_ seems not to matter. But references to a _team_ behave different: - references to a team must be _prefixed with the organization_ and the _spelling (of the organization) matters_, and - it seems that the referenced teams must have access to the repository from where they get referenced Please see the attached screenshot from the official Gitea test instance. ### Gitea Version 1.24.0, Windows Server 2022, self hosted ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots ![Image](https://github.com/user-attachments/assets/c4faa3c4-6567-4364-824e-f087d72b7cfc) ### Git Version 2.47.1.windows.2 ### Operating System Windows Server 2022 ### How are you running Gitea? Downloaded official Release, self hosted on Windows Server 2022 But reproducable on the official Gitea test instance: [https://demo.gitea.com/EXAMPLEorga/examplerepo#test-of-automatically-linked-references](https://demo.gitea.com/EXAMPLEorga/examplerepo#test-of-automatically-linked-references) ### Database MySQL/MariaDB

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

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