Updated Articles

  1. Working with the JSON

    Introduction It is necessary to have an understanding of JSON before deploying Issuetrak with the IDU. This article is intended to provide you with the necessary knowledge to read, edit, understand, and fill out a JSON for Issuetrak. This...
  2. API v2 Overview

    The purpose of this article is to assist you with getting started using API v2 specifically from the server side of things, which includes deployment, logging, rate limiting, and troubleshooting.
  3. Test Site Creation

    It is desirable in most server environments to experiment with new software well before it is deployed in Production. This allows your IT team to determine whether the environment meets the application's System Requirements , find and take note o...
  4. About Locations and Regions

    Locations and Regions reflect physical user, issue, and asset locations. Regions generally define a larger area, while Locations are smaller entities within a Region. A Region might be defined as a state and a corresponding Location within that ...
  5. About Organizations

    Any organizational unit – such as a company or a subsidiary – interacting directly or indirectly with your Issuetrak system is an Organization . Organizations are the largest and most important of all Entities within Issuetrak. Organizations...
  6. Network Share for Attachments

    This article illustrates how to set up a network share to be used for attachments. T
  7. Additional Requirements

    Incoming Email Applications – POP3, Secure POP3, IMAP, or Microsoft Exchange 2013 or newer Outgoing Email / Notifications Applications – SMTP-based outgoing email server DPAPI Encryptio...
  8. Azure Requirements

    Issuetrak 17.6 introduced support for deployments in the Azure hosting environment. The requirements and peculiarities specific to deploying Issuetrak in an Azure hosting environment are provided here. Please note that these requirements are in add...
  9. High Availability Requirements

    Overview Issuetrak 17.6 introduced support for high availability (HA) environments. This page provides the requirements for deploying Issuetrak in an HA environment. Please note that these requirements are in addition to the other requirements...
  10. Subprocessors Used by Issuetrak

    Issuetrak utilizes a variety of services and organizations for the purpose of delivering and enhancing customer experiences, marketing, and issue tracking. These services and organizations are defined as Subprocessors under the EU's General Data P...