Adding a user to an organization's team forces him/her to watch all repositories in the team repository list #3156

Closed
opened 2025-11-02 05:02:16 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @CrustyApplesniffer on GitHub (Apr 8, 2019).

  • Gitea version (or commit ref): 1.7.1
  • Git version: 2.10.2.windows.1
  • Operating system: Windows 2008R2 Server
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

  • Create an organization called Organization_Test

  • Create, in this organization, a team called Contributors that has write acces to issues

  • Create the repository repo1 in this organization and add it to the Contributors repository list
    image

  • Add the user pagaltier2 to the organization and to the Contributors team

  • Sign out and sign-in as pagaltier2

The repository repo1 is under watching and, as pagaltier2, I'll receive all new issues notification
image

I think there should be an option to subscribe (or not) new users to repositories they have write access.

Originally created by @CrustyApplesniffer on GitHub (Apr 8, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.7.1 - Git version: 2.10.2.windows.1 - Operating system: Windows 2008R2 Server - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [X] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] Not relevant - Log gist: ## Description * Create an organization called ```Organization_Test``` * Create, in this organization, a team called ```Contributors``` that has write acces to issues * Create the repository ```repo1``` in this organization and add it to the ```Contributors``` repository list ![image](https://user-images.githubusercontent.com/37656975/55729450-77f78000-5a16-11e9-9c7b-28c3a8f9587a.png) * Add the user ```pagaltier2``` to the organization and to the ```Contributors``` team * Sign out and sign-in as pagaltier2 The repository ```repo1``` is under watching and, as pagaltier2, I'll receive all new issues notification ![image](https://user-images.githubusercontent.com/37656975/55729782-171c7780-5a17-11e9-9f06-99f590450318.png) I think there should be an option to subscribe (or not) new users to repositories they have write access.
Author
Owner

@lafriks commented on GitHub (Apr 8, 2019):

Yes currently that is expected behavior

@lafriks commented on GitHub (Apr 8, 2019): Yes currently that is expected behavior
Author
Owner

@sebastian-sauer commented on GitHub (Apr 9, 2019):

For 1.8 there is a config option to disable the behaviour:

https://github.com/go-gitea/gitea/pull/5852

@sebastian-sauer commented on GitHub (Apr 9, 2019): For 1.8 there is a config option to disable the behaviour: https://github.com/go-gitea/gitea/pull/5852
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3156