"Tickets 2.0" configuration

The new ticket list "Tickets 2.0" works with a cache. This cache is rebuilt each time the Nexus service is started.

To do this, the secret key must be stored, which is used to secure communication between the web service and Nexus if user authentication has not yet taken place. This protected communication includes notifications, ticket caching, and other functions. These services cannot be performed without setting up this secret key.

You can find out exactly how to store this here: White paper – Secret Key

Settings in the ServiceBoard

The ticket cache can be set up under Settings -> General. The settings refer to closed tickets, as all open tickets are loaded into the cache by default.

In addition, closed tickets are then loaded until either the number of months or the set ticket limit is reached.