Future
Item | Priority | Business Value | Approx. Delivery |
Copado - “Deploy” quick action | 1 | Simplify the deployment process to developers, reducing the number of clicks and required thinking, making it faster overall.
| Oct 18, 2024 |
Copado - Estabilization of Jira <-> Copado Integration (1 remaining bug) | 1 | Reduce interruptions of work to developers due to integration issues. There is currently one known issue. | Nov 1, 2024 |
Copado - Provide templates for existing manual tasks automation (during deployment) | 1 | 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 |
Gitlab - Running basic validation upon Gitlab Pull Request Creation (Code review process) - Part 1 & Part 2 | 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 |
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 | 2 | Faster Copado performance, both for developers during the build process and for release managers during release activitie. | Nov 15, 2024 |
Copado - Code review as a Quality Gate before deployment (implementation) | 3 | By performing a code review of the changes before deployment, we reduce the number of bugs delivered from the beginning and therefore | Nov 29, 2024 |
Generic - Approval process to grant “Admin” privileges for INT, UAT and PROD orgs (icare and core) | 3 | Streamline the process to request Admin privileges in the important orgs.
| Nov 29, 2024 |
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, 2024 | |
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 | |
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 - Setup Static code analysis monitoring, create reports of the existing situation | 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 |
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
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 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 procedure → CRM - Technical Release Management
-------------------------------------------------------------------------------------------------------------
June
Jira ↔ Copado Enhancements
- Fixes:
- Subtasks are synchronized to Copado User stories
- User stories can now have any priority and sync will happen (previously there was a problem with "Major" "Minor" and "Priority 1" among others.
- Sprints and releases are synchronized to copado
- Status is bidirectionally synchronized, and upon deployments to INT, UAT and PROD the status will automatically update in Jira
- Mohan account is no longer used for the integration in Jira, instead a service account is used
- Configure Syensqo.ai project
- Created Jira <-> Copado Integration
-------------------------------------------------------------------------------------------------------------
May
Updated Copado Deployer and Copado Connect to the last version
Schedule Apex tests Execution & Report
Avoid creation of user stories in Copado
The best way to get IT support is to use the new
Service One Platform.