Hello!
We have an enterprise infrastructure backend product that is developed on several levels/layers.
The core platform is continously developed using Agile/Kanban and deliver continous improvements as well as the core plumbing into the customer projects.
On top of this, we then have customer projects, including customer adaptation teams, that deliver and manage the visible customer facing functionality and issues.
We need to have internal release notes and bug tracking tied to each project in the platform, and each project's issues many times have links to customer issue tracking systems.
Each customer project may then have many overlapping releases (kanban mode) and releases into test environments must be tracked on all levels, while release content is consolidated into larger releases as the subreleases gets promoted towards a production release. We must also maintain traceability between the external releases and each internal continous release.
This leads to a huge amount of administration and manual handling of (overlapping) versions on each individual issue in the system.
Are there any best practices on how to set this hierarky up?
We have Greenhopper, Structure and Gantt as well.
