Release notes week 7 (2021)

Welcome to this first blog post on our website. Our idea is to use a post on this site to keep you, the customer, informed about the progress and changes in our software. This will let you know exactly what to expect for the upcoming release.

In addition to this blog, you can of course consult the changelog within your installation. This can be found by clicking on 'About' at the bottom (footer) and then on the 'Changelog' tab.

What has changed?

1. From now on, it is possible to send an e-mail to the registrant directly from the ticket. The configured e-mail address (support can set this up for you) is used for this. The content of the e-mail is also logged in the timeline of the ticket.
2. We have separated 'Groups' and 'Teams' (tickets) in terms of management. From now on, they can be managed separately through management. Also, authorisations can no longer be set on a team.
   Please note that this entails new authorisations. This means that you may no longer be able to manage teams. You should explicitly authorise yourself or other administrators to manage teams. You will find the necessary authorisations under the heading 'Tickets' > 'Manage'.
3. The blog posts can be accessed from a widget. To do this, add the widget 'Neo4Z blog' to your dashboard.
4. Inactive list values were shown in the select boxes. This is, of course, illogical. From now on, only active values will be shown.
5. The 'Tickets per team' widget now also shows the total number of all tickets within your teams. The mentioned line is only shown if there is more than one team.
6. It is now possible to enter a supplier and the corresponding ticket number using a template. This allows you to link a supplier directly to a template.
7. The input field for the 6-digit (two-step verification) code is now of the type 'numeric'. This, among other things, makes it work more pleasantly on a smartphone.
8. A log entry is written when two-step verification is activated.
9. Several smaller bugs within datasets and tickets have been fixed.

We also had a penetration test performed on Neo4Z last week, by an independent party. We have incorporated the points from this into the software. Naturally, we cannot mention these points here for security reasons. If you are interested, support can provide you with more information on this.