Feature #28413

Project Visibility class

Added by Sho HASHIMOTO 3 months ago. Updated 12 days ago.

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

0%

Category:UI
Target version:4.1.0
Resolution:

Description

Currently, I can't find information whether redmine projects is public or private.

At least, I want to a.project.public or a.project.private. on /projects.

This patch is added both a.project class.

redmine_project_visibility_class.patch Magnifier (1.41 KB) Sho HASHIMOTO, 2018-03-24 05:33

History

#1 Updated by Go MAEDA 3 months ago

  • Target version set to Candidate for next major release

+1
The patch is useful for theme developers.

#2 Updated by Go MAEDA 2 months ago

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

Setting target version to 4.1.0.

#3 Updated by Go MAEDA 12 days ago

IMHO, we don't have to add "private" class for private projects, adding .public for public projects is enough. The reasons are as follows:

  • You can select by private projects by using :not (e.g. a.project:not(.pubblic))
  • Private issues have .private class but public issues don't have oppisite class .public
  • If users really want .private class, we can support it in later versions. But if we implement .private class now, It will be difficult to delete it in the future due to compatibility.

Feedbacks welcome.

Also available in: Atom PDF