Feature #27731

Allow users to view and comment on their own issues, even if moved into a project where they don't have access.

Added by Michel Albert 9 days ago. Updated 8 days ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues permissions
Target version:-
Resolution:

Description

In the Administration section you can say that "Non-Members" have the permission to view issues in projects they are not member of.

But this works only for public projects. In our case we can't make all projects completely "public" as it would expose them too much. But adding each user as "reporter" to each project would cause a lot of noise on each user's projects page. They would see a ton of projects while they are probably only directly concerned with one or two.

Now if an issue they created is moved to a project where they don't have explicit access, they effectively lose all access to that issue.

I think it would always make sense to let a user see his/her own issues. No matter where they are located. Optionally, this could be made a setting in the permissions page?


Related issues

Related to Redmine - Feature #8488: Create an 'Involve' mechanism to private issues New
Related to Redmine - Feature #18640: Projects accessible by members and authenticated users only New

History

#1 Updated by Mischa The Evil 8 days ago

  • Related to Feature #8488: Create an 'Involve' mechanism to private issues added

#2 Updated by Mischa The Evil 8 days ago

  • Related to Feature #18640: Projects accessible by members and authenticated users only added

#3 Updated by Richard Hector 8 days ago

Would it be possible to link an issue to multiple projects instead?
That way you could link the issue to the relevant project while leaving it in the Public project.

Also available in: Atom PDF