Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#386 12 comentarios 1 reacción 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@hesa ya está trabajando en esto.

Desde el 18/6/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.

Lenguaje dominante
Python
Estrellas
52
Forks
30
Merge medio
4 h 57 min
PR fusionados (30 d)
21

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de aboutcode-org/dejacode

Todos los issues de aboutcode-org/dejacode

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.