Inherited Version in projects
Posted: 26 Mar 2024, 20:57
I have several projects that are sub-projects of a "main" project. The purpose was to share versions and categories across the sub-projects, and enforce a bit more consistency in the sub-projects. That has worked but is a bit wonky here and there. For example, I cannot mark a Version as "released" in a sub-project; that must be done in the main project.
Is project inheritance a feature in good standing? That is, will be maintained and improved in the future?
Is there another approach that could work?
What I would like is an easy way to add version and milestones for certain kinds of project. One example is on-going customer support. We track those issues by month submitted and month closed, like 2024-Q1, then using those in Product Version, Target Version and Fixed In version for the RoadMap view.
Is project inheritance a feature in good standing? That is, will be maintained and improved in the future?
Is there another approach that could work?
What I would like is an easy way to add version and milestones for certain kinds of project. One example is on-going customer support. We track those issues by month submitted and month closed, like 2024-Q1, then using those in Product Version, Target Version and Fixed In version for the RoadMap view.