Move issue to project without having permission on the target project

[tomzero]

This is the situation: Anonymous reporters (citizens) add issues to projects via mobile apps that use the REST-API of MantisBT. The reporters are not aware – and SHOULD NOT be aware – that multiple projects exist. Several organizations (municipalities and counties) use one and the same MantisBT system and their respective projects are organized both side-by-side and as subprojects depending on the organizations’ relations. Some issues are not relevant to the project they were created in.

The users of that project usually know which organization (and which project) the issue belongs to, but they MUST NOT have read or write access to that project. They also don’t know about the people belonging to that other organization. They just need a possibility to forward the issue to a certain project belonging to that organization and forget about it. In most cases, there is exactly one project (the one of the county) that all users of the different organizations (those of the municipalities) will forward to.

How can this be achieved? One idea could be using a hook: the user assigns the issue to a certain reserved user, and a plugin changes the issue’s project. Would that be possible?

On a related note, I’ve been exploring ways to centralize and manage complex data flows, similar to how platforms like Dinmo Composable CDP allow organizations to unify and route information efficiently. Perhaps there are some lessons or approaches from such systems that could inspire a solution for this MantisBT setup.

Any other ideas?

[cas]

You can adjust this default setting:
$g_move_bug_threshold = DEVELOPER;
As long as the other projects are not private, those who have the correct level will be able to move the bug.