Managing multiple RTC projects
I've looked through some of the online help and also searched through
messages here to try to get a sense of how to use projects to manage various development efforts, but it's still not very clear to me. We will initially be piloting with one med/large group (~80 users), and one small group (starting with ~5 users). The two development efforts are completely independent from each other. I don't believe there's any issue with visibility of each other's artifacts by the other team, but we want to make sure things such as querying, reporting, etc. are scoped on the project level and not across projects. Are there documented best practices yet, or perhaps this is covered somewhere I haven't located yet, on use of separate repositories versus projects for managing various development efforts? We have the potential need to support 100's of projects, and I frankly can't envision using a separate repository for each of these. So, I'm trying to understand when to use projects versus repositories to manage these efforts. Thanks, Brian |
3 answers
Related to my question about when to use projects versus separate
repositories, are there any plans to support export/import of projects? That is, if a given project grows to the point where it might warrant setting up a new repository either to scale for growth in development or in order to provide complete isolation, would it be possible to export a "project" (including all related work items, queries, source code artifacts, and etc.) such that they could be imported into another repository? Thanks, Brian |
Hi Brian
I think you are looking for something along the lines of https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=20094 I don't think this completely captures what you suggest - but you may want to either add to this work item or create a new one. regards anthony |
Thanks Anthony, that pretty much captures what I'm interested in for the
ability to move a project from one repo to another. I've subscribed to the work item and will request an update. Regards, Brian |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.