Skip to content

Conversation

@lanseg
Copy link

@lanseg lanseg commented Dec 1, 2025

Issue #379

Screenshot 2025-11-27 at 15-24-34 Extract – Détails de la demande 12 - Test request 2 _ MO - Cadastre complet

Purpose: per-request user ownership, make it possible for one operator to make a single request visible to another operator, even if the second operator is not an owner of the parent process.

Behavior:

  1. Admin user sees all requests, no matter what users or groups are configured for the request or process
  2. User can see or modify request if any of this applies:
    1. User or user's group is added to a Request
    2. User or user's group is added to a parent Process of this request
  3. A request-owning User can modify request-owning users and groups.
  4. After the user removes themselves from the request owners list, per-process ownership rules apply.

* Working version: visibility for groups and users

* Added filtering for completed requests

* Added translations for the card title

* Fixed session errors in test

* Added basic test for the per-request ownership

* Move ownership-related parts into an external class

* Added db migrations, similar to existing ones
@benoitregamey
Copy link
Contributor

Thank you for the contribution, will look it next week.

@lanseg
Copy link
Author

lanseg commented Jan 7, 2026

Hi! Any progress on the pull request review?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants