Future

https://solvayagile.atlassian.net/jira/software/c/projects/CCCME/boards/873/backlog?assignee=712020%3A4c7b99fa-3fd6-4a56-9245-e917f32858ff

Item

Status

Priority

Business Value

Approx. Delivery
(by sprint end)

Copado - “Deploy” quick action
(Part of Volvo suggestions)

DONE

1

Simplify the deployment process to developers, reducing the number of clicks and required thinking, making it faster overall.


Therefore also reduce the support required by release managers


Oct 18, 2024

Copado - Estabilization of Jira <-> Copado Integration (1 remaining bug)

DONE

1

Reduce interruptions of work to developers due to integration issues. There is currently one known issue.

Nov 1, 2024

Gitlab Scheduled Apex Tests execution

DONE

1

Save RM time from having to run the apex tests manually in each of the orgs and create a report to follow-up with the TLs to fix it. This is all automated in this action and only requires follow up by the RM


Gitlab - Running basic validation upon Gitlab Pull Request Creation (Code review process) - Part 1 & Part 2

DONE

1

Prevent merge of user stories for which the deployment won’t work, therefore saving time to developers resolving these as soon as possible.

Nov 15, 2024

Copado - Reduce complexity on profiles deployments

DONE (Strategy in place)

2

Reduce time required by developers and release managers to ensure correct profiles deployment

Reduced number of bugs in UAT or PRODUCTION created due to hacks or incorrect conflict resolution (due to the previous point).

Nov 15, 2024

Copado - Optimize Git Repository Performance
(Part of Volvo suggestions)

DONE

2

Faster Copado performance, both for developers during the build process and for release managers during release activitie.

Nov 15, 2024

Copado - Provide templates for existing manual tasks automation (during deployment)

DONE

2

Reduce time required by release managers in releases to perform manual tasks (by automating these). Reduce error-prone activities to release managers.

Nov 1, 2024

COPADO - Enable devs to run INT and UAT Dec 2, 2024 validations

DONE2

Wins:

  • This will be a time saver to release managers as it will allow teams to anticipate int/uat validation without the need of release manager from the beginning.
  • This will allow developers to validate from bugfix without requiring release manager

Important

  • Deployment to INT & UAT will still be blocked to devs

Copado - Code review as a Quality Gate before deployment (implementation)

DONE

3

By performing a code review of the changes before deployment, we reduce the number of bugs delivered from the beginning and therefore
1) save time from QA of testing something that may not be correct
2) save time from developers from a late-detection
3) avoid delivering bugs in production that would maybe not be detected in the UAT orgs

Nov 29, 2024

Generic - Approval process to grant “Admin” privileges for INT, UAT and PROD orgs (icare and core)

UAT TESTING

3

Streamline the process to request Admin privileges in the important orgs.


By automating it, we reduce the time required for the request, but more importantly the automation takes care of removing the given permissions after certain time.

Nov 29, 2024

Copado - Investigation of User Story Bundle functionality

DONE

3

As output of this investigation we would understand how much time we would save from release manager / developers using this functionality, and/or other benefits.

Dec 13, 2024

Copado - Investigation of Rollback functionality

DONE

3

As output of this investigation we would understand how much time we would save from release manager / developers using this functionality, and/or other benefits.

Dec 13, 2024

Copado - Automate comments in Jira on deployments

DONE

3

Reduce the time required by the release manager after deployments to INT, UAT or PROD, where the release manager is currently posting comments for every Jira ticket.

Dec 13, 2025

Copado - Setup Static code analysis monitoring, create reports of the existing situation

TODO

4

Reduce the technical debt, which directly influences the time required by developers to modify/create logic in the application, being more efficient/faster.

Dec 27, 2024

Copado - Investigation of Copado Next-Gen solution

TODO

4

As output of this investigation we would understand how much time we would save from release manager / developers using this functionality, and/or other benefits.

Jan 10, 2025

Ongoing 


Conversations with Copado

Activation of Manual Sync of Manual Tasks, bugs around this functionality were raised and fixed

COPADO: "Deploy" Quick Action

-------------------------------------------------------------------------------------------------------------

October

ICARE - Perform Samosa Retrofit to missing dev sandboxes

New projects into copado: CM Leads & SP26 (Both ICare)


-------------------------------------------------------------------------------------------------------------

September - Main improvements

TECHNICAL - COPADO & JIRA Integration: Automate Manual Tasks sync into Copado

iCARe Retrofit Samosa to Monthly Dev 2 (required by Yash for CM Leads project)

-------------------------------------------------------------------------------------------------------------

August - Main improvements

TECHNICAL - COPADO: Documentation on Profiles and Permission set changes - Way to proceed

TECHNICAL - COPADO: Scheduled back-promotions

iCARe TECHNICAL - COPADO: Include Jira Key in copado commit (Gowtham request)

TECHNICAL - COPADO: Centralize projects to avoid promotion complexities [feedback from Bart]

-------------------------------------------------------------------------------------------------------------

July - Overall improvements

TECHNICAL - COPADO: Remove “Add Metadata” quick action button from User Story

iCARe TECHNICAL - COPADO: Avoid changing the Copado Credential in a user story from a higher environment to a

iCARe Update Copado Admin / System access

Apex Tests as deployment quality gate

New Release Management procedure

Centralizing and creating Documentation about Copado Way of Working and the new release management procedureCRM - Technical Release Management

Avoid changing the Copado Credential in a user story from a higher environment to a lower environment

-------------------------------------------------------------------------------------------------------------

June

Jira ↔ Copado Enhancements

-------------------------------------------------------------------------------------------------------------

May

TECHNICAL - COPADO & JIRA Integration: Build Jira automated reports for Release preparation (Jalapeño release)

Updated Copado Deployer and Copado Connect to the last version

Schedule Apex tests Execution & Report

Automate Code Coverage Check

Default credentials fixes

Avoid creation of user stories in Copado