Redmine inclines to using dummy projects as project categories. This always seemed odd to me, as in this case we get false projects, mess of ones, that play roles of categories, and the real parent projects.
This plugin is a try to implement the real project categories for Redmine, which it calls “sections”. The primary goals of sections are: to categorize projects, group projects in the project lists and additionally describe projects (e.g., Redmine › Project Sections). The plugin also implements it in an unusual way: thus, sections are used to build project URLs, they support subsections, subsection with the same name (and identifier) can exist under different parent sections and so on.
Additionally, the plugin allows to have project, version and issue custom fields, which are available only for projects, that belong to the selected sections.
- License: GNU General Public License (GPL) v2.0
- External issue: #3174, #3224, #6319, #7091
- Redmine page: http://www.redmine.org/plugins/project_section
- Programming language: Ruby
- SVN Repository:
svn co http://svn.s-andy.com/project-sections project_section
- GitHub mirror: https://github.com/s-andy/project_section
- Latest version: 0.1.0 (almost 3 years ago)
- Redmine: 3.4.x, 3.3.x, 2.5.xd
Author: Andriy Lesyuk
Section specific custom fields and Redmine 3.x support
Here is version 0.1.0 of the Project Sections plugin, which supports Redmine 3.x, allows to have custom fields, which are available only for projects of selected sections, makes it possible to filter issues by section and includes Polish translation.
Project Sections 0.0.2 is now stable
The initial version of the Project Sections plugin has been downloaded 430 times. Some of its users even found and fixed a few bugs, what made it possible to release this non-beta version...