Support for Multiple Ticket Forms with Conditional Fields & Validation

Hello Periskope Team,
I would like to request a feature enhancement to the ticketing system to support conditional ticket forms and dynamic mandatory fields. Currently, when we create custom properties or sections for tickets, all properties appear in every ticket, regardless of the ticket type or use case. This makes it impossible to have different forms such as an onboarding form and an issue/support form, each with its own relevant properties and mandatory requirements. We need the ability to configure different ticket forms where specific properties are shown or hidden based on ticket category, ticket type, or labels (for example, L1 or L2), and where mandatory fields can be enforced conditionally at the time of ticket creation. For instance, a data discrepancy ticket may not require comments, while a product feedback ticket should mandate them; similarly, L1 tickets may require a specific set of fields while L2 tickets require a different set, and tickets without labels should only show a basic form. Today, Periskope only supports all-or-nothing mandatory fields with no conditional validation, no section-wise enforcement, and no prevention at ticket creation. Suggested workarounds using automation rules or auto-closing tickets do not solve this, as they bypass validations, require external webhooks, introduce workflow failures, and address issues only after ticket creation. Adding support for multiple forms, conditional property visibility, and label- or category-based mandatory validation at ticket creation would significantly improve data quality, user experience, and scalability for complex operational workflows.