DefectTrackerConnectionHealth
Whether the integration's credential still works, and whether the customer has to act
type DefectTrackerConnectionHealth {
expiresAt: ISO8601DateTime
reason: String
reconnectRequired: Boolean!
status: DefectTrackerConnectionStatus!
}
Fields
DefectTrackerConnectionHealth.expiresAt ● ISO8601DateTime scalar
When the current credential expires, when the provider says so
DefectTrackerConnectionHealth.reason ● String scalar
Why the integration is in this state, for support rather than for the customer
DefectTrackerConnectionHealth.reconnectRequired ● Boolean! non-null scalar
True when the customer has to reconnect. False while the integration works, and false when the state is UNKNOWN — an outage on our side must not ask every customer to redo a working integration
DefectTrackerConnectionHealth.status ● DefectTrackerConnectionStatus! non-null enum
Current state of the credential
Member Of
AsanaIntegration object ● AzureBoardsIntegration object ● AzureDevopsIntegration object ● BitbucketIntegration object ● BusinessmapIntegration object ● CheckmarxsIntegration object ● ClickupIntegration object ● DependencyTrackIntegration object ● FortifyIntegration object ● FreshdeskIntegration object ● GithubIntegration object ● GitlabIntegration object ● GoogleChatIntegration object ● IntegrationInterface interface ● JiraRequirementsIntegration object ● JiraServerV2Integration object ● LinearIntegration object ● MicrosoftTeamsIntegration object ● SaltSecurityIntegration object ● Saml20Integration object ● ServicenowIntegration object ● SlackIntegration object ● SnykIntegration object ● SonarcloudIntegration object ● SonarqubeIntegration object ● SsoAdfsIntegration object ● SsoAzureIntegration object ● SsoGoogleIntegration object ● TenableIntegration object ● VeracodeIntegration object ● ZendeskIntegration object
Contribute to the Docs
Found something outdated or missing? Help us improve the documentation with a quick suggestion or edit.
How to contribute