allow subtasks in subprojects
when an issue is created in a higher-hierarchy project it's natural to create/delegate subtasks in subprojects, which the reporter doesn't even need to know the exist or have access to them but are needed to resolve the issue, reflecting the internal structure of that higher-hierarchy project, with different software and not-software components, and different teams or assignee.
#1 Updated by Rodrigo Carvalho over 11 years ago
About a year ago we start to use Redmine in my team. We're now in version 0.9.6. Everybody love the tool, its organization, the plugins, etc. We found the plugin 'subtasks' and it gave to us exactly what was missing in the Redmine. Then, the new version bring the feature 'subtasks' into the core. Excelent! But some things are missing from the features of the original plugin. One of them is exactly what Alejandro Mery describes. Because of this my team can't migrate for the newest version of Redmine and we're losing all the new implemented features e bug corrections. Please, take a look at this task. It's very important to maintain the same options that the plugin had offered and continue with the consistence of the excelent work the Redmine team has done. Thank you.