feature/adding ticket creation in Zendesk integration

.changeset/cuddly-teams-flash.md

@@ -0,0 +1,15 @@
+---
+'@o2s/integrations.contentful-cms': minor
+'@o2s/integrations.strapi-cms': minor
+'@o2s/blocks.ticket-details': minor
+'@o2s/blocks.ticket-recent': minor
+'@o2s/integrations.zendesk': minor
+'@o2s/integrations.mocked': minor
+'@o2s/blocks.ticket-list': minor
+'@o2s/modules.surveyjs': minor
+'@o2s/api-harmonization': minor
+'@o2s/framework': minor
+'@o2s/docs': minor
+---
+
+Added ticket creation functionality to the Zendesk integration. Users can now create tickets via POST /tickets with attachments and custom fields. Added custom field mapping from Survey.js format to Zendesk custom fields via new zendesk-field.mapper. Updated table columns on TicketList component to display: ticket type (topic), status, and last updated date. Added display of custom field values from ticket properties on TicketDetails. Updated mapper mocks in cms

.github/CI_CD_README.md

@@ -11,14 +11,17 @@ graph TD
     A[PR Opened/Synchronized] --> B[skip-duplicate-check]
     B --> C[changed-packages]
     B --> D[build]
+    C --> O{Requires Changeset?}
+    O -->|Yes| P[check-changeset]
+    O -->|No| I[End]
     C --> E{docs package changed?}
     C --> L{stories changed?}
     D --> F[lint]
     D --> G[test]
     F --> H[deploy-docs-preview]
     G --> H
     E -->|Yes| H
-    E -->|No| I[End]
+    E -->|No| I
     H --> J[Prepare Environment]
     J --> K[Deploy Docs to Vercel Preview]
 
@@ -162,6 +165,7 @@ Runs code quality checks on PRs and deploys preview environments.
 
 - `skip-duplicate-check`: Prevents duplicate workflow runs
 - `changed-packages`: Determines which packages/stories changed
+- `check-changeset`: Checks if a changeset exists when required packages are modified
 - `build`: Builds the project
 - `lint`: Lints the code
 - `test`: Runs tests
@@ -205,6 +209,7 @@ Determines which packages have changed using Turborepo and detects Storybook cha
 
 - `package_changed`: JSON string containing changed packages information
 - `stories_changed`: `true` if any `*.stories.tsx` or `.storybook/` files changed
+- `requires_changeset`: `true` if changes require a changeset (framework/integrations/modules/blocks)
 
 ### `deploy-vercel`
 

.github/actions/changed-packages/action.yaml

@@ -22,6 +22,9 @@ outputs:
     stories_changed:
         description: 'True if any storybook files or config changed'
         value: ${{ steps.storybook.outputs.stories_changed }}
+    requires_changeset:
+        description: 'True if changes require a changeset (framework/integrations/modules/blocks)'
+        value: ${{ steps.changeset-required.outputs.requires_changeset }}
 
 runs:
     using: 'composite'
@@ -69,3 +72,22 @@ runs:
                   echo "stories_changed=false" >> $GITHUB_OUTPUT
                   echo "No storybook changes detected."
               fi
+
+        - name: Determine if changeset is required
+          id: changeset-required
+          shell: bash
+          env:
+              TURBO_REF_FILTER: ${{ inputs.event-name == 'pull_request' && inputs.base-sha || 'HEAD^' }}
+          run: |
+              # Check if changes involve framework, integrations, modules, or blocks
+              CHANGESET_REQUIRED_FILES=$(git diff --name-only $TURBO_REF_FILTER | grep -E "^packages/(framework|integrations|modules|blocks)/" || true)
+
+              if [ -n "$CHANGESET_REQUIRED_FILES" ]; then
+                  echo "requires_changeset=true" >> $GITHUB_OUTPUT
+                  echo "### Changes requiring changeset detected ###"
+                  echo "$CHANGESET_REQUIRED_FILES"
+                  echo "############################################"
+              else
+                  echo "requires_changeset=false" >> $GITHUB_OUTPUT
+                  echo "No changes requiring changeset detected."
+              fi

.github/workflows/pull-request.yaml

@@ -42,6 +42,7 @@ jobs:
         outputs:
             package_changed: ${{ steps.determine-changes.outputs.package_changed }}
             stories_changed: ${{ steps.determine-changes.outputs.stories_changed }}
+            requires_changeset: ${{ steps.determine-changes.outputs.requires_changeset }}
         steps:
             - name: Checkout repository
               uses: actions/checkout@v6
@@ -57,6 +58,35 @@ jobs:
                   base-sha: ${{ github.event.pull_request.base.sha }}
                   fetch-depth: '0'
 
+    check-changeset:
+        needs: [skip-duplicate-check, changed-packages]
+        if: |
+            needs.skip-duplicate-check.outputs.should_skip != 'true' &&
+            needs.changed-packages.outputs.requires_changeset == 'true'
+        runs-on: ubuntu-latest
+        steps:
+            - name: Checkout repository
+              uses: actions/checkout@v6
+              with:
+                  fetch-depth: 0
+
+            - name: Check for changeset
+              shell: bash
+              env:
+                  BASE_SHA: ${{ github.event.pull_request.base.sha }}
+              run: |
+                  # Check if any .md file in .changeset (excluding README.md) has been modified/added in this PR
+                  CHANGESET_DIFF=$(git diff --name-only $BASE_SHA | grep -E "^\.changeset/.*\.md$" | grep -v "README.md" || true)
+
+                  if [ -z "$CHANGESET_DIFF" ]; then
+                      echo "::error::No changeset found in this PR! You modified packages in framework, integrations, modules, or blocks."
+                      echo "::error::Please run 'npm run changeset' to add a changeset describing your changes."
+                      exit 1
+                  else
+                      echo "Changeset found in PR:"
+                      echo "$CHANGESET_DIFF"
+                  fi
+
     build:
         needs: skip-duplicate-check
         if: needs.skip-duplicate-check.outputs.should_skip != 'true'

apps/api-harmonization/package.json

@@ -104,6 +104,7 @@
         "@types/express": "^5.0.6",
         "@types/jest": "^30.0.0",
         "@types/jsonwebtoken": "^9.0.10",
+        "@types/multer": "^2.0.0",
         "@types/node": "^24.10.9",
         "@types/string-template": "^1.0.7",
         "@types/supertest": "^6.0.3",
@@ -123,4 +124,4 @@
         "tsconfig-paths": "^4.2.0",
         "typescript": "^5.9.3"
     }
-}
+}

apps/api-harmonization/turbo.json

@@ -36,8 +36,34 @@
                 "CF_PREVIEW_TOKEN",
                 "CF_SPACE_ID",
                 "CF_ENV",
-                "CF_MANAGEMENT_TOKEN"
+                "CF_MANAGEMENT_TOKEN",
+                "ZENDESK_API_URL",
+                "ZENDESK_API_TOKEN",
+                "ZENDESK_CONTACT_FORM_ID",
+                "ZENDESK_COMPLAINT_FORM_ID",
+                "ZENDESK_REQUEST_DEVICE_MAINTENANCE_FORM_ID",
+                "ZENDESK_TOPIC_FIELD_ID",
+                "ZENDESK_DEVICE_NAME_FIELD_ID",
+                "ZENDESK_SERIAL_NUMBER_FIELD_ID",
+                "ZENDESK_MAINTENANCE_TYPE_FIELD_ID",
+                "ZENDESK_MAINTENANCE_PREFERRED_DATE_FIELD_ID",
+                "ZENDESK_ADDITIONAL_NOTES_FIELD_ID",
+                "ZENDESK_CONTACT_FIELD_ID",
+                "ZENDESK_ISSUE_DATE_FIELD_ID",
+                "ZENDESK_COMPANY_NAME_FIELD_ID",
+                "ZENDESK_FIRST_NAME_FIELD_ID",
+                "ZENDESK_LAST_NAME_FIELD_ID",
+                "ZENDESK_EMAIL_FIELD_ID",
+                "ZENDESK_PHONE_FIELD_ID",
+                "ZENDESK_INVOICE_NUMBER_FIELD_ID",
+                "ZENDESK_ADDRESS_FIELD_ID",
+                "ZENDESK_INQUIRY_TYPE_FIELD_ID",
+                "ZENDESK_PRODUCT_CATEGORY_FIELD_ID",
+                "ZENDESK_PREFERRED_CONTACT_METHOD_FIELD_ID",
+                "ZENDESK_TERMS_ACCEPTANCE_FIELD_ID",
+                "ZENDESK_NEWSLETTER_CONSENT_FIELD_ID",
+                "ZENDESK_MARKETING_CONSENT_FIELD_ID"
             ]
         }
     }
-}
+}

apps/docs/docs/integrations/forms/surveyjs/features.md

@@ -21,7 +21,7 @@ This document provides an overview of features supported by the SurveyJS integra
 | [Localization](#localization)                           | ✅     | Multi-language support via locale prop                     |
 | [Custom UI Components](#custom-ui-components)           | ✅     | Custom React components for question types                 |
 | [Block Integration](#block-integration)                 | ✅     | Integration with `@o2s/blocks.surveyjs-form` block         |
-| [Ticket System Integration](#ticket-system-integration) | 📋     | Planned feature for ticket submission forms                |
+| [Ticket System Integration](#ticket-system-integration) | ✅     | Submit surveys as tickets to ticket systems                |
 
 ## Feature details
 
@@ -87,8 +87,10 @@ Each question type has custom React components for consistent UI styling.
 
 Flexible submission handling:
 
-- **Current target**: Currently, the only submission target is the SurveyJS backend service
-- **Extensible architecture**: The submission system can be extended to support multiple destinations:
+- **Submission destinations**: Forms can be submitted to multiple destinations configured via the `submitDestination` setting:
+    - **SurveyJS backend service**: Default submission target for standard survey responses
+    - **Ticket systems**: When `submitDestination` includes `'tickets'`, submissions are routed to the framework's Tickets service (e.g., Zendesk integration)
+- **Extensible architecture**: The submission system can be extended to support additional destinations:
     - Backend APIs (REST, GraphQL)
     - Message brokers (e.g., RabbitMQ)
     - Workflow tools (e.g., N8n)
@@ -155,13 +157,11 @@ Integration with the `@o2s/blocks.surveyjs-form` block:
 
 ### Ticket System Integration {#ticket-system-integration}
 
-:::info Planned
-This is a planned feature and is not yet implemented.
-:::
+The SurveyJS module supports ticket submission through the `submitDestination` configuration:
 
-The SurveyJS module is planned to support ticket submission:
+- **Ticket forms**: Create dynamic ticket submission forms using SurveyJS schemas
+- **Form validation**: Automatic validation of required fields (`description`, `ticketFormId`)
+- **Integration**: Works with ticket systems implementing the framework's Tickets service (e.g., Zendesk)
+- **Custom workflows**: Configure submission destinations in CMS via `submitDestination: ['tickets']`
 
-- **Ticket forms**: Create dynamic ticket submission forms
-- **Form validation**: Validate ticket data before submission
-- **Integration**: Can be integrated with ticket systems (e.g., Zendesk)
-- **Custom workflows**: Configure custom submission workflows
+Required survey fields for ticket submission: `description` (string) and `ticketFormId` (number).

apps/docs/docs/integrations/forms/surveyjs/usage.md

@@ -43,7 +43,7 @@ First, create a survey entry in your CMS (e.g., Strapi) with the following requi
 - **surveyId** - SurveyJS survey ID from your SurveyJS service
 - **postId** - SurveyJS post ID for submissions
 - **surveyType** - Type of survey (typically `"survey"`)
-- **submitDestination** - Array of destinations (e.g., `["surveyjs"]`)
+- **submitDestination** - Array of destinations: `["surveyjs"]` for SurveyJS backend, `["tickets"]` for ticket system
 - **requiredRoles** - Array of required roles (can be empty `[]` for public surveys)
 
 ### Step 3: Add block to page in CMS
@@ -68,6 +68,8 @@ The block automatically handles everything:
 
 No frontend code changes are needed - the form will be automatically rendered on the page.
 
+**Ticket submission:** To submit surveys as tickets, set `submitDestination: ["tickets"]` and ensure your survey includes `description` (string) and `ticketFormId` (number) fields.
+
 ## Direct component usage (advanced)
 
 If you need to use the survey component directly without the CMS block system: