Feature #38048

Introduce permission to set a project public

Added by Felix Schäfer about 1 month ago. Updated 20 days ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Go MAEDA% Done:

0%

Category:Permissions and roles
Target version:5.1.0
Resolution:Fixed

Description

In certain situation it might be desirable for project creators or project managers to not be able to change the public attribute for projects.

38048.patch Magnifier (8.14 KB) Felix Schäfer, 2022-12-14 22:00

Related issues

Related to Redmine - Feature #9029: Disable public project creation on a role basis Closed 2011-08-10
Related to Redmine - Defect #38210: Incorrect DB migration version Closed

Associated revisions

Revision 22038
Added by Go MAEDA 20 days ago

Introduce permission to set a project public (#38048).

Patch by Felix Schäfer.

Revision 22039
Added by Go MAEDA 20 days ago

Update locales (#38048).

Revision 22074
Added by Go MAEDA 7 days ago

Fix the migration version of 20221214173537_add_select_project_publicity_permission.rb (#38048, #38210).

History

#1 Updated by Felix Schäfer about 1 month ago

The attached patch provides a possible implementation of this feature with a few tests.

#2 Updated by Go MAEDA about 1 month ago

  • Related to Feature #9029: Disable public project creation on a role basis added

#3 Updated by Go MAEDA about 1 month ago

  • Target version set to Candidate for next major release

#4 Updated by Go MAEDA 23 days ago

  • Target version changed from Candidate for next major release to 5.1.0

Setting the target version to 5.1.0.

#5 Updated by Go MAEDA 20 days ago

  • Status changed from New to Closed
  • Assignee set to Go MAEDA
  • Resolution set to Fixed

Committed the patch. Thank you for improving Redmine.

#6 Updated by Felix Schäfer 20 days ago

Thank you.

#7 Updated by Holger Just 8 days ago

Also available in: Atom PDF