SIT-14449: Copy Ticket Configuration

How to Use This Feature

Feature Summary

Feature Name

Remove logic to check for hold/sale/reservation when copying or adding price codes

Description

This feature removes the need to check for existing price codes when copying or adding new price codes. When a price code is copied from one event to another, it will apply the configuration from the source event to the target event.

Behavior

  • Copying ticket configuration to an existing ticket with the same price code:
  • + The ticket configuration from the source event will be applied to the existing ticket in the target event.

    + A history log will be created in the target event within the version history section.

  • Logging multiple field updates in a single save:
  • + A single change-log row will be created for each save action, including the timestamp, BO operator name, and action description.

    + The change-log row will contain an expandable section listing the changed fields.

  • No changes made:
  • + No change-log row will be created when the BO operator clicks Save without modifying any fields.

  • Copying price code from one event to another:
  • + Logs will be created if the price code exists in the target event.

    Acceptance Criteria

    The feature meets the following acceptance criteria:

  • A single history row is created per save action
  • The change-log row contains an expandable section listing changed fields
  • No change-log row is created when no changes are made
  • Logs are created if the price code exists in the target event
  • Additional Information

    Status: Pending UAT Deployment
    Assigned to: Giocondo Grotti Galileu Moura Brasil
    🏠 Home View in Jira