Under Review
over 8 years ago

Add existing Archive Sets to a 'Release' CSR (improved process for Mass Migrations)

I would like to see the ability to manage approvals and migrations of a release based mass migration in a more controlled way.

  • 'Releases' are typically reviewed and approved by the 'important people' in a project/organization, they tend to have no idea what it is they are approving.. 
  • Providing them with a looooong list of CSRs will only confuse them, resulting in endless questions about things they don't understand..

Ideally I would be able to:

  • Create a separate CSR Type for 'Releases'
  • Define a separate Workflow for these 'Releases'
  • Define a separate Migration Path for these 'Releases'

So far, so good..

Now to make this work, I should be able to attach existing Archive Sets to this 'Release CSR':

  • Instead of creating a new Archive Set, click on the 'Release' button
  • Then select the SCR/Archive Sets you want to include in this new 'Release CSR'

This will also make hand-offs between parallel projects a lot easier, the deliverable of the project would become a 'Release'. The production support team will then be able to pick up that Release, attach it to a new CSR and have it follow the default migration process/path to production. 

 

 

Huub.Bouten
  • over 8 years ago

    @tom_shaw - agreed this should not change the current functionality, this should be an optional feature.

    This request is driven by our current reality in which for the next 5 years we will have multiple project teams creating massive amounts of changes to our production environment. All of those changes will be captured as individual CSRs and during the development cycle unit tests, peer reviews, migrations between project environments, etc. will be captured on those CSRs. (nothing new up to this point)

    The key difference is that those project related changes will be tested and approved as a whole based on a UAT/Regression Test efforts within those projects. We can model the grouping of the actual objects within Stat by making them part of a release, however at this point I cannot model the convergence of the testing effort within Stat.

  • over 8 years ago

    We as long time Stat EBS users would not like for this request to replace any functionality that is currently in place now.  CSRs are individually approved/disapproved in a CSR by CSR basis by the CSR Workflow we use.  When a CSR is approved to be included in our Releases, a Stat Final Archive set is created and the Final Archive is assigned to a "Release" in Archive Set screen and migrated to our Production EBS instance using Stat Mass Migration by Release.