Owen Fellows - 24/Feb/04 02:17 AM Is it not possible for you to seperate your Components into seperate projects if they are released seperately?

John Neale - 25/Feb/04 04:46 AM It is possible to do this. I guess it depends on your view of the world. Our customers view our product as a single entity but internally we view it as many components and they can and are released seperately. For customers to use JIRA they need to see a single product and record bugs against that. Internally, we need to track each component's version seperately so we know what we are talking about.

Scott Farquhar [Atlassian] - 25/Feb/04 05:04 PM Can you create a project for your customers, and then link any internal issues to that bug? Then you can also have a project per-component?

Andrew Michalec - 13/Apr/05 03:54 AM Problem raised in many places, see duplicates.

Bernard Durfee - 21/Dec/05 09:32 AM Our product is in the form of a portal, which of course has many components and sub-components that can all be developed against seperately. We can break everything up into seperate projects, lot's of seperate projects. But at some point it would be nice to have the ability to version components. It just makes more sense than the project category approach.

Stefan Stern - 14/Mar/06 02:44 AM /voted. We have already a a great lot of projects, which have even more components. As projects are currently the highest useful hierarchy level, we want to avoid using them to differ parts too detailed. If a component is "promoted" to a project, we loose the differenciation into components, because that project was originally a component within another project. IT would require an increased detail level - or some fantasy - to introduce new components into the new component-project. Therefore we do not only spoil the highest hierarchy into way too fine granularity, but flatten hierarchy itself in the process, having a lot more projects instead of components. Best regards, Stefan Stern

Chris Mountford [Atlassian] - 28/Mar/06 07:55 PM Another view on this is to have Components that are Projects. The version specific dependencies would need to be managed and the release notes would ideally be composite.

Derek MacKie - 18/Oct/07 02:48 PM My specific case is that we have a ton of architecture related projects in jira that we want to consolidate under one uber architecture project. To do this we need to basically treat each component within the architecture project as its own project - but not as top level projects - nested projects. Giving components versions would be the minimum first step but I think nested sub projects is the way to go.

Tom Miller - 05/Nov/07 11:11 AM When you a portal / component development model, you could have 50 - 100 components and separating them into individual projects would be very difficult to manage. Please add this capability!!!!