Ideas on how to handle Projects and Applications in RM
We use Redmine for tracking IT development projects as well handling bugs and smaller day-to-day fixes on existing applications.
After some years we've now ended up in having Redmine projects for both projects (a team dedicated to delivering one or more software components or adding features to existing ones, within a given timeframe) and applications (one RM project per application).
The problem is now that "application history" (expressed in user requirements, tasks and changes) is scattered between these RM projects, dependant on if they were conceived in project or operations mode.
Any ideas on how to properly organize this in RM?
RE: Ideas on how to handle Projects and Applications in RM - Added by Bernhard Rohloff over 1 year ago
You could make a top project for your release management. Your are then able to share your target versions with the subprojects (customer, internal). In the top project you also have access to all issues of the subprojects together. So you can keep track of both projects at the same time.