Not all companies uses lots of small projects, they may group closely related projects under a single project in Jira for various reasons. In this case each component has a different team and each team may have separate release schedules, which may cause independent version numbers. In this case not every version is applicable to every component. We have an add-on which is specialized for managing components and versions in these kind of projects. You typically see these kind of projects in defence industry. Once we had a university as a customer and they had used course names as component and versions as semesters. Since each course is not available at every semester they were using our app to setup an association between them.
It can be useful to tell people who may not know that components have a relationship.
How it is useful is entirely up to you, it depends on the relationships you have defined in your data. Also how you might do it in Jira, as the core software does not have component to component version linkage.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.