@incident-io/sdk 2.23.0 → 2.24.0

package/dist/cjs/apis/IncidentsV2Api.d.ts

@@ -146,12 +146,12 @@ export declare class IncidentsV2Api extends runtime.BaseAPI {
      */
     incidentsV2ConnectExternalIssueRequestOpts(requestParameters: IncidentsV2ConnectExternalIssueRequest): Promise<runtime.RequestOpts>;
     /**
-     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
+     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This works whether or not automatic incident ticket creation is turned on. While it is off, no tickets are created for other incidents, and the incident\'s fields are not written into this issue until it is turned on.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
      * ConnectExternalIssue Incidents V2
      */
     incidentsV2ConnectExternalIssueRaw(requestParameters: IncidentsV2ConnectExternalIssueRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
     /**
-     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
+     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This works whether or not automatic incident ticket creation is turned on. While it is off, no tickets are created for other incidents, and the incident\'s fields are not written into this issue until it is turned on.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
      * ConnectExternalIssue Incidents V2
      */
     incidentsV2ConnectExternalIssue(requestParameters: IncidentsV2ConnectExternalIssueRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;

package/dist/cjs/apis/IncidentsV2Api.js

@@ -92,7 +92,7 @@ class IncidentsV2Api extends runtime.BaseAPI {
         };
     }
     /**
-     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
+     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This works whether or not automatic incident ticket creation is turned on. While it is off, no tickets are created for other incidents, and the incident\'s fields are not written into this issue until it is turned on.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
      * ConnectExternalIssue Incidents V2
      */
     async incidentsV2ConnectExternalIssueRaw(requestParameters, initOverrides) {
@@ -101,7 +101,7 @@ class IncidentsV2Api extends runtime.BaseAPI {
         return new runtime.VoidApiResponse(response);
     }
     /**
-     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
+     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This works whether or not automatic incident ticket creation is turned on. While it is off, no tickets are created for other incidents, and the incident\'s fields are not written into this issue until it is turned on.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
      * ConnectExternalIssue Incidents V2
      */
     async incidentsV2ConnectExternalIssue(requestParameters, initOverrides) {

package/dist/cjs/version.d.ts

@@ -1 +1 @@
-export declare const VERSION = "2.23.0";
+export declare const VERSION = "2.24.0";

package/dist/cjs/version.js

@@ -2,4 +2,4 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.VERSION = void 0;
 // Written by `make build` from package.json. Do not edit.
-exports.VERSION = "2.23.0";
+exports.VERSION = "2.24.0";

package/dist/esm/apis/IncidentsV2Api.d.ts

@@ -146,12 +146,12 @@ export declare class IncidentsV2Api extends runtime.BaseAPI {
      */
     incidentsV2ConnectExternalIssueRequestOpts(requestParameters: IncidentsV2ConnectExternalIssueRequest): Promise<runtime.RequestOpts>;
     /**
-     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
+     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This works whether or not automatic incident ticket creation is turned on. While it is off, no tickets are created for other incidents, and the incident\'s fields are not written into this issue until it is turned on.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
      * ConnectExternalIssue Incidents V2
      */
     incidentsV2ConnectExternalIssueRaw(requestParameters: IncidentsV2ConnectExternalIssueRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
     /**
-     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
+     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This works whether or not automatic incident ticket creation is turned on. While it is off, no tickets are created for other incidents, and the incident\'s fields are not written into this issue until it is turned on.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
      * ConnectExternalIssue Incidents V2
      */
     incidentsV2ConnectExternalIssue(requestParameters: IncidentsV2ConnectExternalIssueRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;

package/dist/esm/apis/IncidentsV2Api.js

@@ -56,7 +56,7 @@ export class IncidentsV2Api extends runtime.BaseAPI {
         };
     }
     /**
-     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
+     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This works whether or not automatic incident ticket creation is turned on. While it is off, no tickets are created for other incidents, and the incident\'s fields are not written into this issue until it is turned on.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
      * ConnectExternalIssue Incidents V2
      */
     async incidentsV2ConnectExternalIssueRaw(requestParameters, initOverrides) {
@@ -65,7 +65,7 @@ export class IncidentsV2Api extends runtime.BaseAPI {
         return new runtime.VoidApiResponse(response);
     }
     /**
-     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
+     * Connect an existing issue in an issue tracker to an incident, as its external issue.  The issue is synced using the given incident ticket template, as if incident.io had created it from that template. The next sync writes the incident\'s fields into the issue.  This works whether or not automatic incident ticket creation is turned on. While it is off, no tickets are created for other incidents, and the incident\'s fields are not written into this issue until it is turned on.  This needs the incidents.connect_external_issue scope, either across the organisation or from an incident role on this incident.  This fails if the incident already has a different external issue (unless replace is true), or if the issue is already linked to another incident or follow-up.  The ID supplied can be either the incident\'s full ID, or the numeric part of its reference.
      * ConnectExternalIssue Incidents V2
      */
     async incidentsV2ConnectExternalIssue(requestParameters, initOverrides) {

package/dist/esm/version.d.ts

@@ -1 +1 @@
-export declare const VERSION = "2.23.0";
+export declare const VERSION = "2.24.0";

package/dist/esm/version.js

@@ -1,2 +1,2 @@
 // Written by `make build` from package.json. Do not edit.
-export const VERSION = "2.23.0";
+export const VERSION = "2.24.0";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@incident-io/sdk",
-  "version": "2.23.0",
+  "version": "2.24.0",
   "description": "TypeScript SDK for the incident.io API",
   "license": "MIT",
   "author": "incident.io <support@incident.io>",