Support

 View Only
Expand all | Collapse all

Managing Multiple Release: Main with branch for release vs New Project for each release

  • 1.  Managing Multiple Release: Main with branch for release vs New Project for each release

    Posted 12-06-2021 09:45
    Hello,
    I am interested in how people manage multiple releases in Jama. We see too many challenges trying to manage multiple major releases within one project (parallel development being one of the main issues).  I see two main options:
    1. Use one project as the  "Main" and create copies for projects once they are about to release and/or once a team needs to start making significant changes for the next release. We keep the initial project as the "Main"
    2. Create a copy for every release. Instead of having a main, we create a copy for the next release as soon as we are done or ready to start writing new requirements.
    We have integrations with Jira as well as Unity and running into issues trying to manage these linkages. Curious what other do to manage multiple releases in Jama

    ------------------------------
    Jason Barton
    VMS
    Palo Alto CA
    6504246216
    ------------------------------


  • 2.  RE: Managing Multiple Release: Main with branch for release vs New Project for each release

    Posted 12-06-2021 22:56
    Hi Jason,

    we faced a similar challenge as well and have tried different approaches. The approach we finally ended up with, is the following: Our release cycles are that way, that we release version A of a product and then version A goes into maintenance, meaning that we will release patches A.1, A.2 and so forth. But in parallel we start developing version B of the same product. What worked the best for us was to define a suitable point in time before releasing A, where we copy the project (no sync, just plain copy, with a dedicated relationship to the old project, so that we know where the item originally came from). We will end up with a certain time frame where we need to maintain the items in both projects, but this is something we were able to handle. This way we have all activities in the project they belong to, no messed-up syncs going accidentally into wrong direction, and so on.
    We also have an integration with Jira, which we established with Tasktop. Out setup in Jira is, that we only have one project per product, so we maintain the different project versions within Jira. So we actually sync one Jira project to mulitple Jama project, where Jiras Affected Version acts as the "routing identifier" into which Jama project the items flow.

    To sum it up: We use your second approach and its works well when integrating Jira and Jama with Tasktop.

    Best,
    Anna


    ------------------------------
    Anna Henke
    MeVis BreastCare GmbH & Co. KG
    ------------------------------