Content
View differences
Updated by Carsten Klein over 9 years ago
Currently, I would need this for the wiki module as we want to, as discussed with Oliver, refactor the existing wiki and rework overall macro notation.
In addition, this would benefit the community as well as the maintainers since they can now easily identify to which subproject a given work package belongs to.
And, please, make these public.
E.g. alongside the existing structure, provide a
Modules
- Wiki
substructure.
Alternatively, we could add Epics for each module so that existing and new work packages can be added as children to these instead. However, and since the standard user is not able to manage work package relations, this will require more work on behalf of the OP team. TIA\!
In addition, this would benefit the community as well as the maintainers since they can now easily identify to which subproject a given work package belongs to.
And, please, make these public.
E.g. alongside the existing structure, provide a
Modules
- Wiki
substructure.
Alternatively, we could add Epics for each module so that existing and new work packages can be added as children to these instead. However, and since the standard user is not able to manage work package relations, this will require more work on behalf of the OP team.