Problem/Motivation

Not every resource issues tickets: a meeting room or an appointment does not. The ticket submodule currently generates a ticket for every confirmed booking.

Proposed resolution

Add a ticketing opt-in the ticket module injects on the resource type and the resource (resource overrides type; default off), mirroring how the payment submodule injects its settings. The builder and the Orchestra bridge generate tickets only for bookings whose resource has ticketing on.

Remaining tasks

  • ticketing_enabled property: resource type third-party setting plus resource base field, with a resolver.
  • Gate the ticket builder and the Orchestra bridge on it.
  • Tests, docs, translations.

Related to the placement generalization (#3612598). Independent and small.

Issue fork yoyaku-3612600

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

mably created an issue. See original summary.

mably opened merge request !77

mably’s picture

mably commented
Status: Active » Needs review

  • mably committed f8df017d on 1.x 
    feat: #3612600 yoyaku_ticket: per-resource ticketing opt-in (...
mably’s picture

mably commented
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.