Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Enhancement request: Introduce ability to ignore (bypass) Product Object Permissions

Offen
  • Stimmt etwas nicht?
#386 12 Kommentare 1 Reaktion 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@hesa arbeitet bereits daran.

Seit 18.6.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

design needed enhancement

Is your enhancement request related to a problem? Please describe.
Currently, when a product gets created only its creator has access to it, apart from superusers. The user that created the product cannot control who has access to it. If creation is done via a technical user form a CI pipeline, nobody except the superusers gets to see it. Superusers then have to manually assign all users or roles for the individual product version. This has to happen every time a new version is created.

It would be beneficial to have some form of team concept in the permission model.

What are the benefits of the requested enhancement?
The benefit of the proposed feature is that teams working with frequent releases do not have to ask the administrators to change the visibility of yet another version everytime they create a new one. The current situation would cause delays in the work of the development team, as they cannot see their products, and also keeps the administrators away from other tasks. Administrators would currently either have to perform the assignment manually or build custom script that uses webscraping techniques to automate the assignment, as there is no API for it and IDs for users, products, and roles need to be found.

Describe the solution you would like
The concept of teams could be introduced. For instance, teams could create a mapping between users and product names. Users are given "view_product", "change_product", and/or "delete_product" permissions within the team and associated products. Permissions do not have to be assigned for individual version of products, instead all versions for a given name are included. Management of team membership could be done by superusers, but ideally there would also be a new role that allows for self-management of team membership for users that are already part of a team (e.g. the team lead).

Additional notes
n.a.

Vorherrschende Sprache
Python
Sterne
52
Forks
30
Ø Merge
4 Std. 57 Min.
Gemergte PRs (30 T.)
21

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus aboutcode-org/dejacode

Alle Issues in aboutcode-org/dejacode

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.