incident_io_api 2.22.0 → 2.23.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7c17f2227b4d29663755fb7e211d871e0b7641a5ec4747c2f679db8fbf83f9a0
-  data.tar.gz: 1a91bb901241bcc337d0f7c0896de115171c9feb7a7648b8017062d9c9d6e6d5
+  metadata.gz: 3c11fe241a77504154d7122ebfc330fade678ade0ec21fd62a105b104abb9dd3
+  data.tar.gz: df8da2aa6995fe8afa18ca6961891afc6ff45a11d31eb813924e7ce599b5b005
 SHA512:
-  metadata.gz: 8f78bc27dd6a66d618902d2e38dcb2bc1008b17394f7da78106898076984abb6f84e5c0e1ed7ca6d31f2675ac53ba6b66fe8f40b7829c988c87f517910604091
-  data.tar.gz: 30fdd4e5135712f5e52c50bbff7454b24f5b51f4cf8ba00f92520ad565764f74a953c8fb1e8e3a9d1c820d4d52478dcd32f10f071243ca62a7ac01671f25e46d
+  metadata.gz: 0e038699f484bca48c61d1d3ec78e6443d62893b9c40452e5ed8362ef41708c202b7f8a2f4b50b4df4b2f7bc37962b00d1cddb3928be1d343217cc3ccb272406
+  data.tar.gz: 66e74980778818746989c627ef4fbef0df5a2f75798ab79d9ab92482fe76dba686b7e3251097f782c7d19408b854f4bde991e8733104e01d30e927b244cb5488

data/lib/incident_io/api/incidents_v2_api.rb

@@ -20,7 +20,7 @@ module IncidentIo
       @api_client = api_client
     end
     # ConnectExternalIssue Incidents V2
-    # 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.
     # @param id [String] The unique identifier of the incident
     # @param incidents_connect_external_issue_payload_v2 [IncidentsConnectExternalIssuePayloadV2] 
     # @param [Hash] opts the optional parameters
@@ -31,7 +31,7 @@ module IncidentIo
     end
 
     # ConnectExternalIssue Incidents V2
-    # 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.
     # @param id [String] The unique identifier of the incident
     # @param incidents_connect_external_issue_payload_v2 [IncidentsConnectExternalIssuePayloadV2] 
     # @param [Hash] opts the optional parameters

data/lib/incident_io/version.rb

@@ -4,5 +4,5 @@ module IncidentIo
   # The release workflow sets this before building, so it tracks whatever we
   # last published. Listed in .openapi-generator-ignore so regeneration can't
   # reset it.
-  VERSION = "2.22.0"
+  VERSION = "2.23.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: incident_io_api
 version: !ruby/object:Gem::Version
-  version: 2.22.0
+  version: 2.23.0
 platform: ruby
 authors:
 - incident.io