Bug management

This section describes how the bugs reported by our Customers, the Konverso QA, or any other party involved in the product, are tracked and managed: .

The issues reported by the Customer or directly linked to a particular Customer project are tracked in a dedicated ticket, in one of the following portals:

...

Note there is no rule on the deployment timeline. This may vary from as low as 10mn to several months, depending on the severity, impact, and complexity of the bug.

Infrastructure Changes

All infrastructure changes, typically on our Azure IAAS environment are done through a change request in the form of a ticket in our dedicated Jira project (DO). The tickets in this project have a clear definition of the target Azure resources, a list of reviewers and approvers, and some target delivery dates.

The changes made to the infrastructure are documented on the related ticket.

The scope of Infrastructure Changes includes:

• Network and associated firewall.

• VM resources and associated specifications (size)

• Service objects such as Microsoft Bot Service, OAuth2 end points as Applications, etc.