S-360 Documentation

Page tree

Versions Compared

Old Version 1

changes.mady.by.user perr

Saved on

compared with

New Version Current

changes.mady.by.user perr

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

With this new feature developed on

Jira
serverSecuTix JIRA Tracking System
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIddb7e2039-f715-3f84-b1ed-ba058a819c06
keySTX-131822
, it is possible to inject tickets into a different organization where tickets have been sold. This is possible when 

...

If in the Ticket external Printing (Injection) we filter the event, it will take into account just the organization that is being used at that moment, if not, it will take all tickets from the whole institution, no matter the organization.

Test Scenario:

  1. Event created on Org A
  2. Tickets for the event are sold on Org B ( The catalog has been exported previously so that product can be sold on this organization) 
  3. Injection of tickets in Organization A (Sales Channels of Origin: All) --> Tickets injected successfully