Syensqo IS - Customer Support

Page tree

Info coming soon - planning available in Release Calendar 2026


Scope of the Minor releases

Respect of the scope is under the responsibility of the PO and tech leads of the squads


User Story requests to RM

For user story for Prod,  ensure that:

  • The type of the jira ticket is User Story
  • You have assigned the "minor/" fixversion according to the minor release fixVersion process (e.g.: minor/dd_mm_yyyy : minor/01_05_2026)
  • You have set the correct component CORE or iCARe
  • The status is "Ready for UAT" or "Ready for Production"
  • It's assigned to the RM


Minor Release fixVersion process

When creating a Story as part of a Minor Release for PROD deployment:

  1. If you already know the intended PROD deployment date (based on expected development timelines), set the Fix Version using the format minor/dd_mm_yyyy and assign it to the Story.
  2. If the PROD deployment date is not yet known, assign the Story to the minor-placeholder Fix Version (available across all projects). Once the deployment date is confirmed, update the Fix Version to minor/dd_mm_yyyy as described above.
  3. If the Story will not be deployed on the planned date, update the Fix Version immediately in the JIRA Story.
  4. No Story should keep an outdated or unattended Fix Version when deployment is postponed or cancelled. Fix Version must always reflect the actual planned deployment.


Sandbox to use

Developments need to be done on MinorDev (both Orgs: iCARe & CORE) sandbox then it needs to be sent to UAT (both Orgs: iCARe & CORE). RM team will push the changes to UAT (both Orgs: iCARe & CORE ).


Calendar of activities

The purpose of the Minor Release process is to provide clear visibility and predictable planning for deployments to UAT and Production, ensuring all changes follow defined timelines and approvals.

Key points

  • Minor release deployments to PROD are planned for Monday, Tuesday, Wednesday, and Thursday, and must follow these rules:
    • All changes must be deployed to and tested in UAT first, in line with the deployment calendar.
    • Example: if a Story is planned for Tuesday PROD deployment, it must be tested in UAT before Monday 12:00 PM.
      • After 12:00 PM on Monday (i.e., one day before the planned deployment date / Fix Version), the RM (Change Coordinator) will consolidate the related Helix CRs and send them to the Change Manager for approval.
      • A developer must be available to support the Release Manager during UAT validation, if fixes are required.
      • After PROD deployment, the PO or developer can perform validation in PROD.
  • There are no Friday PROD deployments, due to other RM related activities. If there is an urgent need, contact the Release Managers via the "Email" with proper explanation about urgency.  
  • If the CR related to Jira story is not approved at least 1 day before the planned deployment date, the Story will not be deployed to PROD.


The best way to get IT support is to use the new Service One Platform.