The CData Sync App provides a straightforward way to continuously pipeline your Backlog data to any database, data lake, or data warehouse, making it easily available for Analytics, Reporting, AI, and Machine Learning.
The Backlog connector can be used from the CData Sync application to pull data from Backlog and move it to any of the supported destinations.
The Sync App leverages the Backlog API to enable bidirectional access to Backlog.
For required properties, see the Settings tab.
For connection properties that are not typically required, see the Advanced tab.
Authentication methods available include APIKey and OAuth.
Set AuthScheme to APIToken.
To obtain the ApiKey:
Option 1: Obtain and Exchange a Verifier Code
To obtain a verifier code, you must authenticate at the OAuth authorization URL.
Follow the steps below to authenticate from the machine with an internet browser and obtain the OAuthVerifier connection property.
On the headless machine, set the following connection properties to obtain the OAuth authentication values:
After the OAuth settings file is generated, you need to re-set the following properties to connect:
Option 2: Transfer OAuth Settings
Prior to connecting on a headless machine, you need to create and install a connection with the driver on a device that supports an internet browser. Set the connection properties as described in "Desktop Applications" above.
After completing the instructions in "Desktop Applications", the resulting authentication values are encrypted and written to the location specified by OAuthSettingsLocation. The default filename is OAuthSettings.txt.
After you have successfully tested the connection, copy the OAuth settings file to your headless machine.
On the headless machine, set the following connection properties to connect to data:
This section details a selection of advanced features of the Backlog Sync App.
The Sync App supports the use of user defined views, virtual tables whose contents are decided by a pre-configured user defined query. These views are useful when you cannot directly control queries being issued to the drivers. For an overview of creating and configuring custom views, see User Defined Views .
Use SSL Configuration to adjust how Sync App handles TLS/SSL certificate negotiations. You can choose from various certificate formats;. For further information, see the SSLServerCert property under "Connection String Options" .
Configure the Sync App for compliance with Firewall and Proxy, including Windows proxies and HTTP proxies. You can also set up tunnel connections.
For further information, see Query Processing.
By default, the Sync App attempts to negotiate TLS with the server. The server certificate is validated against the default system trusted certificate store. You can override how the certificate gets validated using the SSLServerCert connection property.
To specify another certificate, see the SSLServerCert connection property.
To authenticate to an HTTP proxy, set the following:
Set the following properties:
This section shows the available API objects and provides more information on executing SQL to Backlog APIs.
Views describes the available views. Views are statically defined to model Teams, Users, TeamMembers, etc.
Tables describes the available tables. Tables are statically defined to model Projects, Issues, WikiPages, etc.
Stored Procedures are function-like interfaces to Backlog. Stored procedures allow you to execute operations to Backlog, including downloading documents and moving envelopes.
The Sync App models the data in Backlog as a list of tables in a relational database that can be queried using standard SQL statements.
| Name | Description |
| IssueAttachments | Returns data from issue attachments table. |
| IssueComments | Returns data from issue comments table. |
| IssueLinkedSharedFiles | Returns data from issue linked shared files table. |
| Issues | Returns data from issues table. |
| ProjectAdministrators | Returns data from project administrators table. |
| ProjectCategories | Returns data from project categories table. |
| ProjectCustomFieldItems | Returns data from project custom field items table. |
| ProjectCustomFields | Returns data from project custom fields table. |
| ProjectIssueTypes | Returns data from project issue types table. |
| Projects | Returns data from projects table. |
| ProjectStatuses | Returns data from project statuses table. |
| ProjectTeams | Returns data from project teams table. |
| ProjectUsers | Returns data from project users table. |
| ProjectVersionMilestones | Returns data from project version milestones table. |
| PullRequestAttachments | Returns data from pull request attachments table. |
| PullRequestComments | Returns data from pull request comments table. |
| PullRequests | Returns data from project pull requests table. |
| Watchings | Returns data from watchings table. |
| WikiPageAttachments | Gets list of files attached to Wiki. |
| WikiPages | Returns data from wiki pages table. |
Returns data from issue attachments table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM IssueAttachments WHERE IssueId = 6840954
INSERT is not supported for this table.
UPDATE is not supported for this table.
Delete can be executed by providing the IssueId AND ID.
DELETE FROM IssueAttachments WHERE IssueId = 6840954 AND Id = 3470553
| Name | Type | ReadOnly | Description |
| IssueId [KEY] | Int | False | |
| Id [KEY] | Int | False | |
| Name | String | False | |
| Size | Int | False | |
| Created | Datetime | False | |
| CreatedById | Int | False | |
| CreatedByUserId | String | False | |
| CreatedByName | String | False | |
| CreatedByKeyword | String | False | |
| CreatedByRoleType | Int | False | |
| CreatedByLanguage | String | False | |
| CreatedByMailAddress | String | False | |
| CreatedByNulabAccountName | String | False | |
| CreatedByNulabId | String | False | |
| CreatedByNulabAccountUniqueId | String | False |
Returns data from issue comments table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM IssueComments WHERE IssueId = 6840954 SELECT * FROM IssueComments WHERE IssueId = 6840954 AND Id = 39040604
Insert can be executed by specifying the IssueId and Content.
INSERT INTO IssueComments (IssueId, Content) VALUES ('6840954', 'Sample Comment')
UPDATE IssueComments SET Content = 'Third' WHERE IssueId = 6840954 AND Id = 39042035"
Delete can be executed by specifying the IssueId AND ID.
DELETE FROM IssueComments WHERE IssueId = 6840954 AND Id = 39042338
| Name | Type | ReadOnly | Description |
| IssueId [KEY] | Int | False | |
| Id [KEY] | Int | False | |
| Content | String | False | |
| Created | Datetime | False | |
| Updated | Datetime | False | |
| CreatedById | Int | False | |
| CreatedByUserId | String | False | |
| CreatedByName | String | False | |
| CreatedByRoleType | Int | False | |
| CreatedByLanguage | String | False | |
| CreatedByMailAddress | String | False | |
| CreatedByNulabAccountName | String | False | |
| CreatedByNulabId | String | False | |
| CreatedByNulabAccountUniqueId | String | False |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| NotifiedUserId | String | |
| AttachmentId | String |
Returns data from issues table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM Issues WHERE ID = 6840954 SELECT * FROM Issues WHERE ID IN (6840954, 6840954) SELECT * FROM Issues WHERE ProjectId = 112873 SELECT * FROM Issues WHERE ProjectId IN (112873, 6840954) SELECT * FROM Issues WHERE StatusId = 1 SELECT * FROM Issues WHERE StatusId IN (112873, 6840954) SELECT * FROM Issues WHERE ResolutionId = 0 SELECT * FROM Issues WHERE ResolutionId IN (0, 3)
Insert can be executed by specifying the ProjectId, Summary, PriorityId and IssueTypeId.
INSERT INTO Issues (ProjectId, Summary, PriorityId, IssueTypeId) VALUES (114706, 'Summary', 3, 530959)
UPDATE Issues SET Summary = 'UPDATED_KEY23', ParentIssueId = '6700745', Comment = 'test' WHERE Id = 6700474
Delete can be executed by specifying the IssueId AND ID.
DELETE FROM Issues WHERE IssueId = 6840954 AND Id = 3470553
| Name | Type | ReadOnly | Description |
| Id [KEY] | Int | False | |
| ProjectId | Int | False | |
| IssueKey | String | False | |
| KeyId | Int | False | |
| ParentIssueId | Int | False | |
| Summary | String | False | |
| Description | String | False | |
| CustomAttributes | String | False | |
| StartDate | Date | False | |
| DueDate | Date | False | |
| ActualHours | Decimal | False | |
| EstimatedHours | Decimal | False | |
| Created | Datetime | False | |
| CreatedByUserName | String | False | |
| CreatedByUserId | String | False | |
| Updated | Datetime | False | |
| UpdatedByUserName | String | False | |
| UpdatedByUserId | String | False | |
| ResolutionId | Int | False | |
| ResolutionName | String | False | |
| PriorityId | Int | False | |
| PriorityName | String | False | |
| IssueTypeId | Int | False | |
| IssueTypeName | String | False | |
| IssueTypeProjectId | Int | False | |
| IssueTypeColor | String | False | |
| IssueTypeDisplayOrder | Int | False | |
| StatusId | Int | False | |
| StatusProjectId | Int | False | |
| StatusName | String | False | |
| StatusColor | String | False | |
| StatusDisplayOrder | Int | False | |
| AssigneeId | Int | False | |
| AssigneeName | String | False | |
| AssigneeRoleType | Int | False | |
| AssigneeLanguage | String | False | |
| AssigneeMailAddress | String | False |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| Category | String | |
| Version | String | |
| Milestone | String | |
| ParentChild | Int |
The allowed values are 0, 1, 2, 3, 4. |
| Attachment | Boolean | |
| SharedFile | Boolean | |
| CreatedSince | String | |
| CreatedUntil | String | |
| UpdatedSince | String | |
| UpdatedUntil | String | |
| StartDateSince | String | |
| StartDateUntil | String | |
| DueDateSince | String | |
| DueDateUntil | String | |
| Keyword | String | |
| Comment | String |
Returns data from project administrators table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM ProjectAdministrators WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId and UserId.
INSERT INTO ProjectAdministrators (ProjectId, UserId) VALUES ('114706', '280728')
UPDATE is not supported for this table.
Delete can be executed by specifying the ProjectId AND UserId.
DELETE FROM ProjectAdministrators WHERE ProjectId = 114706 AND UserId = 280728
| Name | Type | ReadOnly | Description |
| ProjectId [KEY] | Int | False | |
| UserId [KEY] | Int | False | |
| UserCode | String | False | |
| Name | String | False | |
| Keyword | String | False | |
| NulabAccountName | String | False | |
| NulabId | String | False | |
| NulabAccountUniqueId | String | False | |
| RoleType | Int | False | |
| Language | String | False | |
| MailAddress | String | False |
Returns data from project categories table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM ProjectCategories WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId and Name.
INSERT INTO ProjectCategories (ProjectId, Name) VALUES ('114706', 'cat4')
UPDATE ProjectCategories SET Name = 'Sample' WHERE ProjectId = 114706 AND Id = 205625
Delete can be executed by specifying the IssueId AND ID.
DELETE FROM ProjectCategories WHERE ProjectId = 114706 AND Id = 205622
| Name | Type | ReadOnly | Description |
| ProjectId [KEY] | Int | False | |
| Id [KEY] | Int | False | |
| Name | String | False | |
| DisplayOrder | Int | False |
Returns data from project custom field items table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM ProjectCustomFieldItems WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId, CustomFieldId and Name.
INSERT INTO ProjectCustomFieldItems (ProjectId, CustomFieldId, Name) VALUES ('114706', '44072', 'Fourth')
UPDATE ProjectCustomFieldItems SET Name = 'Fourth4' WHERE ProjectId = 114706 AND CustomFieldId = 44072 AND ItemId = 4
Delete can be executed by specifying the IssueId AND ID.
DELETE FROM ProjectCustomFieldItems WHERE ProjectId = 114706 AND CustomFieldId = 44072 AND ItemId = 5
| Name | Type | ReadOnly | Description |
| ProjectId [KEY] | Int | False | |
| Id [KEY] | Int | False | |
| DisplayOrder | String | True | |
| Name | String | False | |
| ItemId [KEY] | Int | False | |
| ItemName | String | False | |
| ItemDisplayOrder | String | True |
Returns data from project custom fields table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM ProjectCustomFields WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId, typeId and Name.
INSERT INTO ProjectCustomFields (ProjectId, Name, typeId) VALUES ('114706', 'Milestone4', 1)
UPDATE ProjectCustomFields SET Name = 'Third' WHERE ProjectId = 114706 AND Id = 44203
Delete can be executed by specifying the IssueId AND ID.
DELETE FROM ProjectCustomFields WHERE ProjectId = 114706 AND Id = 44204
| Name | Type | ReadOnly | Description |
| ProjectId [KEY] | Int | False | |
| Id [KEY] | Int | False | |
| TypeId | String | False | |
| Name | String | False | |
| Description | String | False | |
| Required | Booelan | False | |
| AllowAddItem | Booelan | False | |
| UseIssueType | Booelan | False | |
| ApplicableIssueTypes | String | False | |
| DisplayOrder | String | False |
Returns data from project issue types table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM ProjectIssueTypes WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId, Color and Name.
INSERT INTO ProjectIssueTypes (ProjectId, Name, Color) VALUES ('114706', 'Sample', '#ff9200')
UPDATE ProjectIssueTypes SET Name = 'ytryet43' WHERE ProjectId = 114706 AND Id = 532089
| Name | Type | ReadOnly | Description |
| ProjectId [KEY] | Int | False | |
| Id [KEY] | Int | False | |
| Name | String | False | |
| Color | String | False | |
| DisplayOrder | Int | True | |
| TemplateSummary | String | False | |
| TemplateDescription | String | False |
Returns data from projects table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM Projects WHERE Id = 114706 SELECT * FROM Projects WHERE ProjectKey = 'SAMPLE_KEY' SELECT * FROM Projects WHERE All = true SELECT * FROM Projects WHERE Archived = false
Insert can be executed by specifying the Name, ProjectKey, chartEnabled, projectLeaderCanEditProjectLeader, subtaskingEnabled, textFormattingRule, ProjectLeaderCanEditProjectLeader, UseDevAttributes and UseWikiTreeView.
INSERT INTO Projects (Name, ProjectKey, chartEnabled, projectLeaderCanEditProjectLeader, subtaskingEnabled, textFormattingRule, ProjectLeaderCanEditProjectLeader, UseDevAttributes, UseWikiTreeView) VALUES ('InsertedName', 'INSERTED_KEY_3', false, true, true, markdown, true, false, false)
UPDATE Projects SET ProjectKey = 'UPDATED_KEY2', Name = 'UpdatedName2' WHERE Id = 112873
Delete can be executed by specifying ID.
DELETE FROM Projects WHERE Id = 113332
| Name | Type | ReadOnly | Description |
| Id [KEY] | Int | False | |
| ProjectKey | String | False | |
| Name | String | False | |
| DisplayOrder | Int | False | |
| ChartEnabled | Boolean | False | |
| SubtaskingEnabled | Boolean | False | |
| ProjectLeaderCanEditProjectLeader | Boolean | False | |
| UseDevAttributes | Boolean | False | |
| UseWikiTreeView | Boolean | False | |
| TextFormattingRule | String | False | |
| Archived | Boolean | False | |
| useResolvedForChart | Boolean | False | |
| useWiki | Boolean | False | |
| useFileSharing | Boolean | False | |
| useOriginalImageSizeAtWiki | Boolean | False |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| All | Boolean |
Returns data from project statuses table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM ProjectStatuses WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId, Name and Color.
Possible values for Color column are #ea2c00 ,#e87758 ,#e07b9a ,#868cb7 ,#3b9dbd ,#4caf93 ,#b0be3c ,#eda62a ,#f42858, #393939.
INSERT INTO ProjectStatuses (ProjectId, Name, Color) VALUES ('117182', 'Sample', '#3b9dbd')
UPDATE ProjectStatuses SET Name = 'Sample', color = '#ea2c00' WHERE ProjectId = 114706 AND Id = 18504
| Name | Type | ReadOnly | Description |
| Id [KEY] | Int | False | |
| ProjectId [KEY] | Int | False | |
| Name | String | False | |
| Color | String | False | |
| DisplayOrder | Int | True |
Returns data from project teams table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM ProjectTeams WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId and TeamId.
INSERT INTO ProjectTeams (ProjectId, TeamId) VALUES ('114706', '55083')
UPDATE is not supported for this table.
Delete can be executed by specifying the IssueId AND ID.
DELETE FROM ProjectTeams WHERE ProjectId = 114706 AND TeamId = 55082
| Name | Type | ReadOnly | Description |
| ProjectId [KEY] | Int | False | |
| TeamId [KEY] | Int | False | |
| Name | String | True | |
| DisplayOrder | Int | True | |
| Created | Datetime | True | |
| CreatedById | Int | True | |
| CreatedByUserId | String | True | |
| CreatedByName | String | True | |
| CreatedByRoleType | Int | True | |
| CreatedByLang | String | True | |
| CreatedByMailAddress | String | True | |
| Updated | Datetime | True | |
| UpdatedById | Int | True | |
| UpdatedByUserId | String | True | |
| UpdatedByName | String | True | |
| UpdatedByRoleType | Int | True | |
| UpdatedByLang | String | True | |
| UpdatedByMailAddress | String | True |
Returns data from project users table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM ProjectUsers WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId and UserId.
INSERT INTO ProjectUsers (ProjectId, UserId) VALUES ('114706', '280728')
UPDATE is not supported for this table.
Delete can be executed by specifying the ProjectId AND UserId.
DELETE FROM ProjectUsers WHERE ProjectId = 114706 AND UserId = 280728
| Name | Type | ReadOnly | Description |
| ProjectId [KEY] | Int | False | |
| UserId [KEY] | Int | False | |
| UserCode | String | False | |
| Name | String | False | |
| Keyword | String | False | |
| NulabAccountName | String | False | |
| NulabId | String | False | |
| NulabAccountUniqueId | String | False | |
| RoleType | Int | False | |
| Language | String | False | |
| MailAddress | String | False |
Returns data from project version milestones table.
projectversionmilestones
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM ProjectVersionMilestones WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId and Name.
INSERT INTO ProjectVersionMilestones (ProjectId, Name) VALUES ('114706', 'Milestone4')
UPDATE ProjectVersionMilestones SET Name = 'Sample' WHERE ProjectId = 114706 AND Id = 138889
Delete can be executed by specifying the ProjectId AND ID.
DELETE FROM ProjectVersionMilestones WHERE ProjectId = 114706 AND Id = 138890
| Name | Type | ReadOnly | Description |
| ProjectId [KEY] | Int | False | |
| Id [KEY] | Int | False | |
| Name | String | False | |
| Description | String | False | |
| DisplayOrder | Int | True | |
| StartDate | Date | False | |
| ReleaseDueDate | Date | False | |
| Archived | Boolean | True |
Returns data from pull request attachments table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId, RepositoryId and PullRequestNumber are required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM PullRequestAttachments WHERE ProjectId = '94706' AND RepositoryId = 21949 AND PullRequestNumber = 2
INSERT is not supported for this table.
UPDATE is not supported for this table.
Delete can be executed by specifying the ProjectId, RepositoryId, PullRequestNumber AND ID.
DELETE FROM PullRequestAttachments WHERE ProjectId = 39470 AND RepositoryId = 21949 AND PullRequestNumber = 2 AND ID = 3
| Name | Type | ReadOnly | Description |
| ProjectId [KEY] | Int | True | |
| RepositoryId [KEY] | Int | True | |
| PullRequestNumber [KEY] | Int | True | |
| Id [KEY] | Int | True | |
| Name | String | True | |
| Size | Int | True | |
| Created | Datetime | True | |
| CreatedById | Int | True | |
| CreatedByUserId | String | True | |
| CreatedByName | String | True | |
| CreatedByKeyword | String | True | |
| CreatedByRoleType | Int | True | |
| CreatedByLanguage | String | True | |
| CreatedByMailAddress | String | True | |
| CreatedByNulabAccountName | String | True | |
| CreatedByNulabId | String | True | |
| CreatedByNulabAccountUniqueId | String | True |
Returns data from pull request comments table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId, RepositoryId and PullRequestNumber are required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM PullRequestComments WHERE ProjectId = 114706 AND RepositoryId = 22462 AND PullRequestNumber = 2
Insert can be executed by specifying the ProjectId, RepositoryId, PullRequestNumber and Content.
INSERT INTO PullRequestComments (ProjectId, RepositoryId, PullRequestNumber, Content) VALUES ('114706', '22462', '2', 'FirstComment')
UPDATE PullRequestComments SET Content = 'Third' WHERE ProjectId = 114706 AND RepositoryId = 22462 AND PullRequestNumber = 2 AND ID = 3
Delete is not supported for this table.
| Name | Type | ReadOnly | Description |
| ProjectId | Int | False | |
| RepositoryId | Int | False | |
| PullRequestNumber | Int | False | |
| Id [KEY] | Int | False | |
| Content | String | False | |
| Created | Datetime | True | |
| Updated | Datetime | True | |
| CreatedById | Int | True | |
| CreatedByUserId | String | True | |
| CreatedByName | String | True | |
| CreatedByRoleType | Int | True | |
| CreatedByLanguage | String | True | |
| CreatedByMailAddress | String | True | |
| CreatedByNulabAccountName | String | True | |
| CreatedByNulabId | String | True | |
| CreatedByNulabAccountUniqueId | String | True |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| NotifiedUserId | String |
Returns data from project pull requests table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId and RepositoryId are required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM PullRequests WHERE ProjectId = '114706' AND RepositoryId = 22462" SELECT * FROM PullRequests WHERE ProjectId = '114706' AND RepositoryId = 22462 AND Number = 2
Insert can be executed by specifying the ProjectId, RepositoryId, Summary, description, base and branch.
INSERT INTO PullRequests (ProjectId, RepositoryId, Summary, description, base, branch) VALUES ('114706', '22462', 'First', 'FirstPullReq', 'main', 'sample')
UPDATE PullRequests SET Summary = 'Third' WHERE ProjectId = 114706 AND RepositoryId = 22462 AND Number = 44203
Delete is not supported for this table.
| Name | Type | ReadOnly | Description |
| ProjectId [KEY] | Int | False | |
| RepositoryId [KEY] | Int | False | |
| Id [KEY] | Int | False | |
| Number | Int | False | |
| Summary | String | False | |
| Description | String | False | |
| Base | String | False | |
| Branch | String | False | |
| BaseCommit | String | True | |
| BranchCommit | String | True | |
| CloseAt | Datetime | True | |
| MergeAt | Datetime | True | |
| StatusId | Int | True | |
| StatusName | String | True | |
| IssueId | Int | False | |
| AssigneeId | Int | False | |
| AssigneeName | String | True | |
| AssigneeRoleType | Int | True | |
| AssigneeLanguage | String | True | |
| AssigneeMailAddress | String | True | |
| Created | Datetime | True | |
| CreatedById | Int | True | |
| CreatedByUserId | String | True | |
| CreatedByName | String | True | |
| CreatedByKeyword | String | True | |
| CreatedByRoleType | Int | True | |
| CreatedByLanguage | String | True | |
| CreatedByMailAddress | String | True | |
| CreatedByNulabAccountName | String | True | |
| CreatedByNulabId | String | True | |
| CreatedByNulabAccountUniqueId | String | True | |
| Updated | Datetime | True | |
| UpdatedById | Int | True | |
| UpdatedByUserId | String | True | |
| UpdatedByName | String | True | |
| UpdatedByKeyword | String | True | |
| UpdatedByRoleType | Int | True | |
| UpdatedByLanguage | String | True | |
| UpdatedByMailAddress | String | True | |
| UpdatedByNulabAccountName | String | True | |
| UpdatedByNulabId | String | True | |
| UpdatedByNulabAccountUniqueId | String | True |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| NotifiedUserId | String | |
| AttachmentId | String |
Returns data from watchings table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The UserId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM Watchings WHERE UserId = '280688' SELECT * FROM Watchings WHERE Id = '145169'
Insert can be executed by specifying the IssueId and Note.
INSERT INTO Watchings (IssueId, Note) VALUES ('6868643', 'Sample')
UPDATE Watchings SET Note = 'Third' WHERE Id = 145171
Delete can be executed by specifying ID.
DELETE FROM Watchings WHERE Id = 145170
| Name | Type | ReadOnly | Description |
| UserId | Int | False | |
| Id [KEY] | Int | False | |
| Note | String | False | |
| Type | String | True | |
| IssueId | String | True | |
| ResourceAlreadyRead | Boolean | True | |
| LastContentUpdated | Datetime | True | |
| Created | Datetime | True | |
| Updated | Datetime | True |
Gets list of files attached to Wiki.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The WikiPageId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM WikiPageAttachments WHERE WikiPageId = '639459'
INSERT is not supported for this table.
UPDATE is not supported for this table.
Delete can be executed by specifying the IssueId AND ID.
DELETE FROM WikiPageAttachments WHERE WikiPageId = 639459 AND Id = 188522
| Name | Type | ReadOnly | Description |
| WikiPageId [KEY] | Int | False | |
| Id [KEY] | Int | False | |
| Name | String | False | |
| Size | Int | False | |
| Created | Datetime | False | |
| CreatedById | Int | False | |
| CreatedByUserId | String | False | |
| CreatedByName | String | False | |
| CreatedByKeyword | String | False | |
| CreatedByRoleType | Int | False | |
| CreatedByLanguage | String | False | |
| CreatedByMailAddress | String | False | |
| CreatedByNulabAccountName | String | False | |
| CreatedByNulabId | String | False | |
| CreatedByNulabAccountUniqueId | String | False |
Returns data from wiki pages table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM WikiPages WHERE ProjectId = '114706' SELECT * FROM WikiPages WHERE Id = 639460
Insert can be executed by specifying the ProjectId, Content and Name.
INSERT INTO WikiPages (ProjectId, Name, Content) VALUES ('114706', 'FirstWiki3', 'Sample Comment')
UPDATE WikiPages SET Name = 'UPDATED', Content = 'UPDATED' WHERE Id = 639460
Delete can be executed by specifying ID.
DELETE FROM WikiPages WHERE Id = 639461
| Name | Type | ReadOnly | Description |
| ProjectId | Int | False | |
| Id [KEY] | Int | False | |
| Name | String | False | |
| Content | String | False | |
| Created | Datetime | True | |
| CreatedById | Int | True | |
| CreatedByUserId | String | True | |
| CreatedByName | String | True | |
| CreatedByKeyword | String | True | |
| CreatedByRoleType | Int | True | |
| CreatedByLanguage | String | True | |
| CreatedByMailAddress | String | True | |
| CreatedByNulabAccountName | String | True | |
| CreatedByNulabId | String | True | |
| CreatedByNulabAccountUniqueId | String | True | |
| Updated | Datetime | True | |
| UpdatedById | Int | True | |
| UpdatedByUserId | String | True | |
| UpdatedByName | String | True | |
| UpdatedByKeyword | String | True | |
| UpdatedByRoleType | Int | True | |
| UpdatedByLanguage | String | True | |
| UpdatedByMailAddress | String | True | |
| UpdatedByNulabAccountName | String | True | |
| UpdatedByNulabId | String | True | |
| UpdatedByNulabAccountUniqueId | String | True |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| MailNotify | Boolean |
Views are similar to tables in the way that data is represented; however, views are read-only.
Queries can be executed against a view as if it were a normal table.
| Name | Description |
| IssueCategories | Returns data from issue categories table. |
| IssueCommentChangeLog | Returns data from issue comment change log table. |
| IssueCommentNotifications | Returns data from issue comment notifications table. |
| IssueCommentStars | Returns data from issue comment starts table. |
| IssueMilestones | Returns data from issue milestones table. |
| IssueParticipants | Returns list of participants of an issue. |
| IssueVersions | Returns data from issue versions table. |
| Licenses | Returns licence. |
| Notifications | Returns own notifications. |
| Priorities | Returns data from priorities table. |
| ProjectRecentUpdates | Returns recent update in the project. |
| ProjectSharedFiles | Gets list of Project Shared Files |
| ProjectTeamMembers | Returns data from project team members table. |
| PullRequestCommentChangeLog | Returns data from pull request comment changelog table. |
| PullRequestCommentNotifications | Returns data from pull request comment notifications table. |
| PullRequestCommentStars | Returns data from pull request comment starts table. |
| Repositories | Returns data from project repositories table. |
| Resolutions | Returns data from resolutions table. |
| Space | Returns information about your space. |
| SpaceDiskUsage | Returns information about space disk usage. |
| SpaceDiskUsageDetails | Returns information about space disk details usage. |
| SpaceNotifications | Returns space notification. |
| SpaceUpdates | Returns recent updates in your space. |
| TeamMembers | Returns data from team members table. |
| Teams | Returns data from teams table. |
| UserReceivedStars | Returns the list of stars that user received. |
| UserRecentlyViewedIssues | Returns list of issues which the user viewed recently. |
| UserRecentlyViewedProjects | Returns list of projects which the user viewed recently. |
| UserRecentlyViewedWikiPages | Returns list of Wikis which the user viewed recently. |
| UserRecentUpdates | Returns user recent updates. |
| Users | Returns data from users table. |
| WikiPageHistory | Returns history of Wiki page. |
| WikiPageLinkedSharedFiles | Returns data from wiki page linked shred files table. |
| WikiPageStars | Returns list of stars received on the Wiki page. |
| WikiPageTags | Returns list of tags that are used in the project. |
Returns data from issue categories table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM IssueCategories WHERE IssueId = 6840954
| Name | Type | Description |
| IssueId | String | |
| Id [KEY] | Int | |
| Name | String | |
| DisplayOrder | String |
Returns data from issue comment change log table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM IssueCommentChangeLog WHERE IssueId = 6840954
| Name | Type | Description |
| IssueId | Int | |
| CommentId | Int | |
| AttachmentInfo | String | |
| AttributeInfo | String | |
| Field | String | |
| NewValue | String | |
| NotificationInfo | String | |
| OriginalValue | String |
Returns data from issue comment notifications table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM IssueCommentNotifications WHERE IssueId = 6840954
| Name | Type | Description |
| IssueId | Int | |
| CommentId | Int | |
| NotificationId [KEY] | Int | |
| Reason | String | |
| AlreadyRead | Boolean | |
| ResourceAlreadyRead | Boolean | |
| CreatedById | Int | |
| CreatedByUserId | String | |
| CreatedByName | String | |
| CreatedByKeyword | String | |
| CreatedByRoleType | Int | |
| CreatedByLanguage | String | |
| CreatedByMailAddress | String | |
| CreatedByNulabAccountName | String | |
| CreatedByNulabId | String | |
| CreatedByNulabAccountUniqueId | String |
Returns data from issue comment starts table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM IssueCommentStars WHERE IssueId = 6840954
| Name | Type | Description |
| IssueId | Int | |
| CommentId | Int | |
| StarId [KEY] | Int | |
| Comment | String | |
| Title | String | |
| Url | String | |
| Created | Datetime | |
| PresenterId | Int | |
| PresenterUserId | String | |
| PresenterName | String | |
| PresenterKeyword | String | |
| PresenterRoleType | Int | |
| PresenterLanguage | String | |
| PresenterMailAddress | String | |
| PresenterNulabAccountName | String | |
| PresenterNulabId | String | |
| PresenterNulabAccountUniqueId | String |
Returns data from issue milestones table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM IssueMilestones WHERE IssueId = 6868745
| Name | Type | Description |
| IssueId | String | |
| Id [KEY] | Int | |
| Name | String | |
| Description | String | |
| Archived | Boolean | |
| ProjectId | Int | |
| ReleaseDueDate | Date | |
| StartDate | Date | |
| DisplayOrder | String |
Returns list of participants of an issue.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM IssueParticipants WHERE IssueId = '6840954'
| Name | Type | Description |
| IssueId | Int | |
| Id [KEY] | Int | |
| UserId | String | |
| Name | String | |
| Keyword | String | |
| NulabAccountName | String | |
| NulabId | String | |
| NulabAccountUniqueId | String | |
| RoleType | Int | |
| Language | String | |
| MailAddress | String |
Returns data from issue versions table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM IssueVersions WHERE IssueId = 6868745
| Name | Type | Description |
| IssueId | String | |
| Id [KEY] | Int | |
| Name | String | |
| Description | String | |
| Archived | Boolean | |
| ProjectId | Int | |
| ReleaseDueDate | Date | |
| StartDate | Date | |
| DisplayOrder | String |
Returns licence.
Backlog does not support any column for filtering this table. All filters will be executed client side.
| Name | Type | Description |
| Active | Boolean | |
| AttachmentLimit | Int | |
| AttachmentLimitPerFile | Int | |
| AttachmentNumLimit | Int | |
| Attribute | Boolean | |
| AttributeLimit | Int | |
| Burndown | Boolean | |
| CommentLimit | Int | |
| ComponentLimit | Int | |
| FileSharing | Boolean | |
| Gantt | Boolean | |
| Git | Boolean | |
| IssueLimit | Int | |
| LicenceTypeId | Int | |
| LimitDate | Date | |
| NulabAccount | Boolean | |
| ParentChildIssue | Boolean | |
| PostIssueByMail | Boolean | |
| ProjectGroup | Boolean | |
| ProjectLimit | Int | |
| PullRequestAttachmentLimitPerFile | Int | |
| PullRequestAttachmentNumLimit | Int | |
| RemoteAddress | Boolean | |
| RemoteAddressLimit | Int | |
| StartedOn | Datetime | |
| StorageLimit | Int | |
| Subversion | Boolean | |
| SubversionExternal | Boolean | |
| UserLimit | Int | |
| VersionLimit | Int | |
| WikiAttachment | Boolean | |
| WikiAttachmentLimitPerFile | Int | |
| WikiAttachmentNumLimit | Int |
Returns own notifications.
Backlog does not support any column for filtering this table. All filters will be executed client side.
| Name | Type | Description |
| Id [KEY] | Int | |
| AlreadyRead | Boolean | |
| Reason | Int | |
| ResourceAlreadyRead | Int | |
| Created | Int | |
| ProjectId | Int | |
| ProjectKey | String | |
| ProjectName | String | |
| ProjectDisplayOrder | Int | |
| ProjectChartEnabled | Boolean | |
| ProjectSubtaskingEnabled | Boolean | |
| ProjectProjectLeaderCanEditProjectLeader | Boolean | |
| ProjectUseDevAttributes | Boolean | |
| ProjectUseWikiTreeView | Boolean | |
| ProjectTextFormattingRule | String | |
| ProjectArchived | Boolean | |
| IssueId | Int | |
| IssueProjectId | Int | |
| IssueKey | String | |
| IssueKeyId | Int | |
| IssueTypeId | Int | |
| IssueTypeName | String | |
| IssueTypeColor | String | |
| IssueTypeProjectId | Int | |
| IssueTypeDisplayOrder | Int | |
| IssueSummary | String | |
| IssueDescription | String | |
| IssueResolutions | String | |
| IssuePriorityId | Int | |
| IssuePriorityName | String | |
| IssueStatusId | Int | |
| IssueStatusName | String | |
| IssueStatusColor | String | |
| IssueStatusProjectId | Int | |
| IssueStatusDisplayOrder | Int | |
| IssueAssigneeId | Int | |
| IssueAssigneeName | String | |
| IssueAssigneeRoleType | Int | |
| IssueAssigneeLanguage | String | |
| IssueAssigneeMailAddress | String | |
| IssueCategories | String | |
| IssueVersions | String | |
| IssueMilestones | String | |
| IssueCustomFields | String | |
| IssueAttachments | String | |
| IssueSharedFiles | String | |
| IssueStars | String | |
| IssueStartDate | Date | |
| IssueDueDate | Date | |
| IssueEstimatedHours | Decimal | |
| IssueActualHours | Decimal | |
| IssueParentIssueId | Int | |
| IssueCreated | Datetime | |
| IssueCreatedById | Int | |
| IssueCreatedByUserId | String | |
| IssueCreatedByName | String | |
| IssueCreatedByKeyword | String | |
| IssueCreatedByNulabAccountName | String | |
| IssueCreatedByNulabId | String | |
| IssueCreatedByNulabAccountUniqueId | String | |
| IssueCreatedByRoleType | Int | |
| IssueCreatedByLanguage | String | |
| IssueCreatedByMailAddress | String | |
| IssueUpdated | Datetime | |
| IssueUpdatedById | Int | |
| IssueUpdatedByUserId | String | |
| IssueUpdatedByName | String | |
| IssueUpdatedByKeyword | String | |
| IssueUpdatedByNulabAccountName | String | |
| IssueUpdatedByNulabId | String | |
| IssueUpdatedByNulabAccountUniqueId | String | |
| IssueUpdatedByRoleType | Int | |
| IssueUpdatedByLanguage | String | |
| IssueUpdatedByMailAddress | String | |
| CommentId | Int | |
| CommentContent | String | |
| CommentCreated | String | |
| SentById | Int | |
| SentByUserId | String | |
| SentByName | String | |
| SentByKeyword | String | |
| SentByNulabAccountName | String | |
| SentByNulabId | String | |
| SentByNulabAccountUniqueId | String | |
| SentByRoleType | Int | |
| SentByLanguage | String | |
| SentByMailAddress | String |
Returns data from priorities table.
Backlog does not support any column for filtering this table. All filters will be executed client side.
| Name | Type | Description |
| Id [KEY] | Int | |
| Name | String |
Returns recent update in the project.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM ProjectRecentUpdates WHERE ProjectId = 114706
| Name | Type | Description |
| Id [KEY] | Int | |
| Created | Datetime | |
| Type | String | |
| ContentId | Int | |
| Content | String | |
| ContentDiff | String | |
| ContentKeyId | String | |
| ContentDescription | String | |
| ContentSummary | String | |
| ContentRepository | String | |
| ContentAttachments | String | |
| ContentSharedFiles | String | |
| ContentComments | String | |
| ContentChanges | String | |
| ContentParties | String | |
| ProjectId | Int | |
| ProjectKey | String | |
| ProjectName | String | |
| ProjectDisplayOrder | Int | |
| ProjectChartEnabled | Boolean | |
| ProjectSubtaskingEnabled | Boolean | |
| ProjectProjectLeaderCanEditProjectLeader | Boolean | |
| ProjectUseDevAttributes | Boolean | |
| ProjectUseWikiTreeView | Boolean | |
| ProjectTextFormattingRule | String | |
| ProjectArchived | Boolean | |
| CreatedById | Int | |
| CreatedByUserId | String | |
| CreatedByName | String | |
| CreatedByKeyword | String | |
| CreatedByNulabAccountName | String | |
| CreatedByNulabId | String | |
| CreatedByNulabAccountUniqueId | String | |
| CreatedByRoleType | Int | |
| CreatedByLanguage | String | |
| CreatedByMailAddress | String |
Returns data from project team members table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM ProjectTeamMembers WHERE ProjectId = 114706
| Name | Type | Description |
| ProjectId | Int | |
| TeamId | Int | |
| MemberId | Int | |
| UserId | String | |
| Name | String | |
| Keyword | String | |
| NulabAccountName | String | |
| NulabId | String | |
| NulabAccountUniqueId | String | |
| RoleType | Int | |
| Lang | String | |
| MailAddress | String |
Returns data from pull request comment changelog table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId, RepositoryId and PullRequestNumber are required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM PullRequestCommentChangeLog WHERE ProjectId = '114706' AND RepositoryId = 22462 AND PullRequestNumber = 2
| Name | Type | Description |
| ProjectId | Int | |
| RepositoryId | Int | |
| PullRequestNumber | Int | |
| AttachmentInfo | String | |
| AttributeInfo | String | |
| Field | String | |
| NewValue | String | |
| NotificationInfo | String | |
| OriginalValue | String |
Returns data from pull request comment notifications table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId, RepositoryId and PullRequestNumber are required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM PullRequestCommentNotifications WHERE ProjectId = '114706' AND RepositoryId = 22462 AND PullRequestNumber = 2
| Name | Type | Description |
| ProjectId | Int | |
| RepositoryId | Int | |
| PullRequestNumber | Int | |
| NotificationId [KEY] | Int | |
| Reason | String | |
| AlreadyRead | Boolean | |
| ResourceAlreadyRead | Boolean | |
| CreatedById | Int | |
| CreatedByUserId | String | |
| CreatedByName | String | |
| CreatedByKeyword | String | |
| CreatedByRoleType | Int | |
| CreatedByLanguage | String | |
| CreatedByMailAddress | String | |
| CreatedByNulabAccountName | String | |
| CreatedByNulabId | String | |
| CreatedByNulabAccountUniqueId | String |
Returns data from pull request comment starts table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId, RepositoryId and PullRequestNumber are required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM PullRequestCommentStars WHERE ProjectId = '114706' AND RepositoryId = 22462 AND PullRequestNumber = 2
| Name | Type | Description |
| ProjectId | Int | |
| RepositoryId | Int | |
| PullRequestNumber | Int | |
| StarId [KEY] | Int | |
| Comment | String | |
| Title | String | |
| Url | String | |
| Created | Datetime | |
| PresenterId | Int | |
| PresenterUserId | String | |
| PresenterName | String | |
| PresenterKeyword | String | |
| PresenterRoleType | Int | |
| PresenterLanguage | String | |
| PresenterMailAddress | String | |
| PresenterNulabAccountName | String | |
| PresenterNulabId | String | |
| PresenterNulabAccountUniqueId | String |
Returns data from project repositories table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM Repositories WHERE ProjectId = 117182 SELECT * FROM Repositories WHERE ProjectId = 117182 AND Id = 22862 SELECT * FROM Repositories WHERE ProjectId = 117182 AND Name = 'First'
| Name | Type | Description |
| Id [KEY] | Int | |
| ProjectId | Int | |
| Name | String | |
| Description | String | |
| HookUrl | String | |
| HttpUrl | String | |
| SshUrl | String | |
| DisplayOrder | Int | |
| PushedAt | Datetime | |
| Created | Datetime | |
| CreatedById | Int | |
| CreatedByUserId | String | |
| CreatedByName | String | |
| CreatedByKeyword | String | |
| CreatedByRoleType | Int | |
| CreatedByLanguage | String | |
| CreatedByMailAddress | String | |
| CreatedByNulabAccountName | String | |
| CreatedByNulabId | String | |
| CreatedByNulabAccountUniqueId | String | |
| Updated | Datetime | |
| UpdatedById | Int | |
| UpdatedByUserId | String | |
| UpdatedByName | String | |
| UpdatedByKeyword | String | |
| UpdatedByRoleType | Int | |
| UpdatedByLanguage | String | |
| UpdatedByMailAddress | String | |
| UpdatedByNulabAccountName | String | |
| UpdatedByNulabId | String | |
| UpdatedByNulabAccountUniqueId | String |
Returns data from resolutions table.
Backlog does not support any column for filtering this table. All filters will be executed client side.
| Name | Type | Description |
| Id [KEY] | Int | |
| Name | String |
Returns information about your space.
Backlog does not support any column for filtering this table. All filters will be executed client side.
| Name | Type | Description |
| SpaceKey | String | |
| Name | String | |
| OwnerId [KEY] | Int | |
| Language | String | |
| Timezone | String | |
| ReportSendTime | Hour | |
| TextFormattingRule | String | |
| Created | Datetime | |
| Updated | Datetime |
Returns information about space disk usage.
Backlog does not support any column for filtering this table. All filters will be executed client side.
| Name | Type | Description |
| Capacity | String | |
| Issue | String | |
| Wiki | String | |
| File | Int | |
| Subversion | Int | |
| Git | Int | |
| GitLFS | Int | |
| PullRequest | Int |
Returns information about space disk details usage.
Backlog does not support any column for filtering this table. All filters will be executed client side.
| Name | Type | Description |
| ProjectId | String | |
| File | Int | |
| Git | Int | |
| GitLFS | Int | |
| Issue | String | |
| Wiki | String | |
| Subversion | Int |
Returns space notification.
Backlog does not support any column for filtering this table. All filters will be executed client side.
| Name | Type | Description |
| Content | String | |
| Updated | Datetime |
Returns recent updates in your space.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM SpaceUpdates WHERE Type = 13 SELECT * FROM SpaceUpdates WHERE Type IN (13, 5)
| Name | Type | Description |
| Id [KEY] | Int | |
| Created | Datetime | |
| Type | String | |
| ContentId | Int | |
| Content | String | |
| ContentDiff | String | |
| ContentKeyId | String | |
| ContentDescription | String | |
| ContentSummary | String | |
| ContentRepository | String | |
| ContentAttachments | String | |
| ContentSharedFiles | String | |
| ContentComments | String | |
| ContentChanges | String | |
| ContentParties | String | |
| ProjectId | Int | |
| ProjectKey | String | |
| ProjectName | String | |
| ProjectDisplayOrder | Int | |
| ProjectChartEnabled | Boolean | |
| ProjectSubtaskingEnabled | Boolean | |
| ProjectProjectLeaderCanEditProjectLeader | Boolean | |
| ProjectUseDevAttributes | Boolean | |
| ProjectUseWikiTreeView | Boolean | |
| ProjectTextFormattingRule | String | |
| ProjectArchived | Boolean | |
| CreatedById | Int | |
| CreatedByUserId | String | |
| CreatedByName | String | |
| CreatedByKeyword | String | |
| CreatedByNulabAccountName | String | |
| CreatedByNulabId | String | |
| CreatedByNulabAccountUniqueId | String | |
| CreatedByRoleType | Int | |
| CreatedByLanguage | String | |
| CreatedByMailAddress | String |
Returns data from team members table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The TeamId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM TeamMembers WHERE TeamId = 54836
| Name | Type | Description |
| TeamId | Int | |
| Id [KEY] | Int | |
| UserId | String | |
| Name | String | |
| Keyword | String | |
| NulabAccountName | String | |
| NulabId | String | |
| NulabAccountUniqueId | String | |
| RoleType | Int | |
| Lang | String | |
| MailAddress | String |
Returns data from teams table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM Teams WHERE Id = 55081
| Name | Type | Description |
| Id [KEY] | Int | |
| Name | String | |
| DisplayOrder | Int | |
| Members | String | |
| Created | Datetime | |
| CreatedById | Int | |
| CreatedByUserId | String | |
| CreatedByName | String | |
| CreatedByRoleType | Int | |
| CreatedByLang | String | |
| CreatedByMailAddress | String | |
| Updated | Datetime | |
| UpdatedById | Int | |
| UpdatedByUserId | String | |
| UpdatedByName | String | |
| UpdatedByRoleType | Int | |
| UpdatedByLang | String | |
| UpdatedByMailAddress | String |
Returns the list of stars that user received.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The UserId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM UserReceivedStars WHERE UserId = 263366
| Name | Type | Description |
| UserId | String | |
| Id [KEY] | Int | |
| Comment | String | |
| Title | String | |
| Url | String | |
| Created | Datetime | |
| PresenterId | Int | |
| PresenterUserId | String | |
| PresenterName | String | |
| PresenterKeyword | String | |
| PresenterRoleType | Int | |
| PresenterLanguage | String | |
| PresenterMailAddress | String | |
| PresenterNulabAccountName | String | |
| PresenterNulabId | String | |
| PresenterNulabAccountUniqueId | String |
Returns list of issues which the user viewed recently.
Backlog does not support any column for filtering this table. All filters will be executed client side.
| Name | Type | Description |
| Id [KEY] | Int | |
| ProjectId | Int | |
| IssueKey | String | |
| KeyId | Int | |
| ParentIssueId | Int | |
| Summary | String | |
| Description | String | |
| StartDate | Date | |
| DueDate | Date | |
| ActualHours | Decimal | |
| EstimatedHours | Decimal |
Returns list of projects which the user viewed recently.
Backlog does not support any column for filtering this table. All filters will be executed client side.
| Name | Type | Description |
| Id [KEY] | Int | |
| ProjectKey | String | |
| Name | String | |
| DisplayOrder | Int | |
| ChartEnabled | Boolean | |
| SubtaskingEnabled | Boolean | |
| ProjectLeaderCanEditProjectLeader | Boolean | |
| UseDevAttributes | Boolean | |
| UseWikiTreeView | Boolean | |
| TextFormattingRule | String | |
| Archived | Boolean |
Returns list of Wikis which the user viewed recently.
Backlog does not support any column for filtering this table. All filters will be executed client side.
| Name | Type | Description |
| ProjectId | Int | |
| Id [KEY] | Int | |
| Name | String | |
| Content | String | |
| Created | Datetime |
Returns user recent updates.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The UserId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM UserRecentUpdates WHERE UserId = 263366 SELECT * FROM UserRecentUpdates WHERE UserId = 263366 AND Type = 3 SELECT * FROM UserRecentUpdates WHERE UserId = 263366 AND Type IN (3, 5)
| Name | Type | Description |
| UserId | String | |
| Id [KEY] | Int | |
| Created | Datetime | |
| Type | String | |
| ContentId | Int | |
| Content | String | |
| ContentDiff | String | |
| ContentKeyId | String | |
| ContentDescription | String | |
| ContentSummary | String | |
| ContentRepository | String | |
| ContentAttachments | String | |
| ContentSharedFiles | String | |
| ContentComments | String | |
| ContentChanges | String | |
| ContentParties | String | |
| ProjectId | Int | |
| ProjectKey | String | |
| ProjectName | String | |
| ProjectDisplayOrder | Int | |
| ProjectChartEnabled | Boolean | |
| ProjectSubtaskingEnabled | Boolean | |
| ProjectProjectLeaderCanEditProjectLeader | Boolean | |
| ProjectUseDevAttributes | Boolean | |
| ProjectUseWikiTreeView | Boolean | |
| ProjectTextFormattingRule | String | |
| ProjectArchived | Boolean | |
| CreatedById | Int | |
| CreatedByUserId | String | |
| CreatedByName | String | |
| CreatedByKeyword | String | |
| CreatedByNulabAccountName | String | |
| CreatedByNulabId | String | |
| CreatedByNulabAccountUniqueId | String | |
| CreatedByRoleType | Int | |
| CreatedByLanguage | String | |
| CreatedByMailAddress | String |
Returns data from users table.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM Users WHERE Id = 54836
| Name | Type | Description |
| Id [KEY] | Int | |
| UserId | String | |
| Name | String | |
| NulabAccountName | String | |
| NulabAccountID | String | |
| NulabAccountUniqueId | String | |
| RoleType | Int | |
| Lang | String | |
| MailAddress | String |
Returns history of Wiki page.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The WikiPageId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM WikiPageHistory WHERE WikiPageId = '639459'
| Name | Type | Description |
| WikiPageId | Int | |
| PageId [KEY] | Int | |
| Name | String | |
| Content | String | |
| Version | Int | |
| Created | Datetime | |
| CreatedById | Int | |
| CreatedByUserId | String | |
| CreatedByName | String | |
| CreatedByKeyword | String | |
| CreatedByRoleType | Int | |
| CreatedByLanguage | String | |
| CreatedByMailAddress | String | |
| CreatedByNulabAccountName | String | |
| CreatedByNulabId | String | |
| CreatedByNulabAccountUniqueId | String |
Returns list of stars received on the Wiki page.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The WikiPageId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM WikiPageStars WHERE WikiPageId = '528251'
| Name | Type | Description |
| WikiPageId | Int | |
| CommentId | Int | |
| StarId [KEY] | Int | |
| Comment | String | |
| Title | String | |
| Url | String | |
| Created | Datetime | |
| PresenterId | Int | |
| PresenterUserId | String | |
| PresenterName | String | |
| PresenterKeyword | String | |
| PresenterRoleType | Int | |
| PresenterLanguage | String | |
| PresenterMailAddress | String | |
| PresenterNulabAccountName | String | |
| PresenterNulabId | String | |
| PresenterNulabAccountUniqueId | String |
Returns list of tags that are used in the project.
The Sync App will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Sync App.
For example, the following query is processed server side:
SELECT * FROM WikiPageTags WHERE ProjectId = '94706'
| Name | Type | Description |
| ProjectId | Int | |
| Id [KEY] | Int | |
| Name | String |
The connection string properties are the various options that can be used to establish a connection. This section provides a complete list of the options you can configure in the connection string for this provider. Click the links for further details.
For more information on establishing a connection, see Establishing a Connection.
| Property | Description |
| URL | The URL of the Backlog account. |
| AuthScheme | The type of authentication to use when connecting to Backlog. |
| ApiKey | The API key allows you make requests to the Backlog API. |
| Property | Description |
| OAuthClientId | Specifies the client Id that was assigned the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server. |
| OAuthClientSecret | Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret ). This secret registers the custom application with the OAuth authorization server. |
| Property | Description |
| SSLServerCert | Specifies the certificate to be accepted from the server when connecting using TLS/SSL. |
| Property | Description |
| FirewallType | Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall. |
| FirewallServer | Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources. |
| FirewallPort | Specifies the TCP port to be used for a proxy-based firewall. |
| FirewallUser | Identifies the user ID of the account authenticating to a proxy-based firewall. |
| FirewallPassword | Specifies the password of the user account authenticating to a proxy-based firewall. |
| Property | Description |
| ProxyAutoDetect | Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server. |
| ProxyServer | The hostname or IP address of the proxy server that you want to route HTTP traffic through. |
| ProxyPort | The TCP port on your specified proxy server (set in the ProxyServer connection property) that has been reserved for routing HTTP traffic to and from the client. |
| ProxyAuthScheme | Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property. |
| ProxyUser | The username of a user account registered with the proxy server specified in the ProxyServer connection property. |
| ProxyPassword | The password associated with the user specified in the ProxyUser connection property. |
| ProxySSLType | The SSL type to use when connecting to the proxy server specified in the ProxyServer connection property. |
| ProxyExceptions | A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property. |
| Property | Description |
| LogModules | Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged. |
| Property | Description |
| Location | Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path. |
| BrowsableSchemas | Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC . |
| Tables | Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC . |
| Views | Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC . |
| Property | Description |
| IncludeCustomFields | Set this to true if you want to retrieve custom fields from the Issues table. |
| MaxRows | Specifies the maximum rows returned for queries without aggregation or GROUP BY. |
| MaxThreads | The Max Thread. |
| Other | Specifies additional hidden properties for specific use cases. These are not required for typical provider functionality. Use a semicolon-separated list to define multiple properties. |
| Pagesize | Specifies the maximum number of results to return from Backlog, per page. This setting overrides the default page size set by the datasource, which is optimized for most use cases. |
| ProjectId | Id of the specific project. |
| PseudoColumns | Specifies the pseudocolumns to expose as table columns. Use the format 'TableName=ColumnName;TableName=ColumnName'. The default is an empty string, which disables this property. |
| Timeout | Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error. The default is 60 seconds. Set to 0 to disable the timeout. |
| UserDefinedViews | Specifies a filepath to a JSON configuration file defining custom views. The provider automatically detects and uses the views specified in this file. |
This section provides a complete list of the Authentication properties you can configure in the connection string for this provider.
| Property | Description |
| URL | The URL of the Backlog account. |
| AuthScheme | The type of authentication to use when connecting to Backlog. |
| ApiKey | The API key allows you make requests to the Backlog API. |
The URL of the Backlog account.
The URL of the Backlog account in the form "https://{sample}.backlog.com".
The type of authentication to use when connecting to Backlog.
The API key allows you make requests to the Backlog API.
Append your API key to the API requests to return data from your account.
This section provides a complete list of the OAuth properties you can configure in the connection string for this provider.
| Property | Description |
| OAuthClientId | Specifies the client Id that was assigned the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server. |
| OAuthClientSecret | Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret ). This secret registers the custom application with the OAuth authorization server. |
Specifies the client Id that was assigned the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server.
OAuthClientId is one of a handful of connection parameters that need to be set before users can authenticate via OAuth. For details, see Establishing a Connection.
Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret ). This secret registers the custom application with the OAuth authorization server.
OAuthClientSecret is one of a handful of connection parameters that need to be set before users can authenticate via OAuth. For details, see Establishing a Connection.
This section provides a complete list of the SSL properties you can configure in the connection string for this provider.
| Property | Description |
| SSLServerCert | Specifies the certificate to be accepted from the server when connecting using TLS/SSL. |
Specifies the certificate to be accepted from the server when connecting using TLS/SSL.
If using a TLS/SSL connection, this property can be used to specify the TLS/SSL certificate to be accepted from the server. Any other certificate that is not trusted by the machine is rejected.
This property can take the following forms:
| Description | Example |
| A full PEM Certificate (example shortened for brevity) | -----BEGIN CERTIFICATE----- MIIChTCCAe4CAQAwDQYJKoZIhv......Qw== -----END CERTIFICATE----- |
| A path to a local file containing the certificate | C:\cert.cer |
| The public key (example shortened for brevity) | -----BEGIN RSA PUBLIC KEY----- MIGfMA0GCSq......AQAB -----END RSA PUBLIC KEY----- |
| The MD5 Thumbprint (hex values can also be either space or colon separated) | ecadbdda5a1529c58a1e9e09828d70e4 |
| The SHA1 Thumbprint (hex values can also be either space or colon separated) | 34a929226ae0819f2ec14b4a3d904f801cbb150d |
If not specified, any certificate trusted by the machine is accepted.
Use '*' to signify to accept all certificates. Note that this is not recommended due to security concerns.
This section provides a complete list of the Firewall properties you can configure in the connection string for this provider.
| Property | Description |
| FirewallType | Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall. |
| FirewallServer | Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources. |
| FirewallPort | Specifies the TCP port to be used for a proxy-based firewall. |
| FirewallUser | Identifies the user ID of the account authenticating to a proxy-based firewall. |
| FirewallPassword | Specifies the password of the user account authenticating to a proxy-based firewall. |
Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Note: By default, the Sync App connects to the system proxy. To disable this behavior and connect to one of the following proxy types, set ProxyAutoDetect to false.
The following table provides port number information for each of the supported protocols.
| Protocol | Default Port | Description |
| TUNNEL | 80 | The port where the Sync App opens a connection to Backlog. Traffic flows back and forth via the proxy at this location. |
| SOCKS4 | 1080 | The port where the Sync App opens a connection to Backlog. SOCKS 4 then passes theFirewallUser value to the proxy, which determines whether the connection request should be granted. |
| SOCKS5 | 1080 | The port where the Sync App sends data to Backlog. If the SOCKS 5 proxy requires authentication, set FirewallUser and FirewallPassword to credentials the proxy recognizes. |
To connect to HTTP proxies, use ProxyServer and ProxyPort. To authenticate to HTTP proxies, use ProxyAuthScheme, ProxyUser, and ProxyPassword.
Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Specifies the TCP port to be used for a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Identifies the user ID of the account authenticating to a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Specifies the password of the user account authenticating to a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
This section provides a complete list of the Proxy properties you can configure in the connection string for this provider.
| Property | Description |
| ProxyAutoDetect | Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server. |
| ProxyServer | The hostname or IP address of the proxy server that you want to route HTTP traffic through. |
| ProxyPort | The TCP port on your specified proxy server (set in the ProxyServer connection property) that has been reserved for routing HTTP traffic to and from the client. |
| ProxyAuthScheme | Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property. |
| ProxyUser | The username of a user account registered with the proxy server specified in the ProxyServer connection property. |
| ProxyPassword | The password associated with the user specified in the ProxyUser connection property. |
| ProxySSLType | The SSL type to use when connecting to the proxy server specified in the ProxyServer connection property. |
| ProxyExceptions | A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property. |
Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server.
When this connection property is set to True, the Sync App checks your system proxy settings for existing proxy server configurations (no need to manually supply proxy server details).
This connection property takes precedence over other proxy settings. Set to False if you want to manually configure the Sync App to connect to a specific proxy server.
To connect to an HTTP proxy, see ProxyServer. For other proxies, such as SOCKS or tunneling, see FirewallType.
The hostname or IP address of the proxy server that you want to route HTTP traffic through.
The Sync App only routes HTTP traffic through the proxy server specified in this connection property when ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True, which is the default, the Sync App instead routes HTTP traffic through the proxy server specified in your system proxy settings.
The TCP port on your specified proxy server (set in the ProxyServer connection property) that has been reserved for routing HTTP traffic to and from the client.
The Sync App only routes HTTP traffic through the proxy server port specified in this connection property when ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True, which is the default, the Sync App instead routes HTTP traffic through the proxy server port specified in your system proxy settings.
For other proxy types, see FirewallType.
Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property.
The authentication type can be one of the following:
For all values other than "NONE", you must also set the ProxyUser and ProxyPassword connection properties.
If you need to use another authentication type, such as SOCKS 5 authentication, see FirewallType.
The username of a user account registered with the proxy server specified in the ProxyServer connection property.
The ProxyUser and ProxyPassword connection properties are used to connect and authenticate against the HTTP proxy specified in ProxyServer.
After selecting one of the available authentication types in ProxyAuthScheme, set this property as follows:
| ProxyAuthScheme Value | Value to set for ProxyUser |
| BASIC | The user name of a user registered with the proxy server. |
| DIGEST | The user name of a user registered with the proxy server. |
| NEGOTIATE | The username of a Windows user who is a valid user in the domain or trusted domain that the proxy server is part of, in the format user@domain or domain\user. |
| NTLM | The username of a Windows user who is a valid user in the domain or trusted domain that the proxy server is part of, in the format user@domain or domain\user. |
| NONE | Do not set the ProxyPassword connection property. |
The Sync App only uses this username if ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True, which is the default, the Sync App instead uses the username specified in your system proxy settings.
The password associated with the user specified in the ProxyUser connection property.
The ProxyUser and ProxyPassword connection properties are used to connect and authenticate against the HTTP proxy specified in ProxyServer.
After selecting one of the available authentication types in ProxyAuthScheme, set this property as follows:
| ProxyAuthScheme Value | Value to set for ProxyPassword |
| BASIC | The password associated with the proxy server user specified in ProxyUser. |
| DIGEST | The password associated with the proxy server user specified in ProxyUser. |
| NEGOTIATE | The password associated with the Windows user account specified in ProxyUser. |
| NTLM | The password associated with the Windows user account specified in ProxyUser. |
| NONE | Do not set the ProxyPassword connection property. |
For SOCKS 5 authentication or tunneling, see FirewallType.
The Sync App only uses this password if ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True, which is the default, the Sync App instead uses the password specified in your system proxy settings.
The SSL type to use when connecting to the proxy server specified in the ProxyServer connection property.
This property determines when to use SSL for the connection to the HTTP proxy specified by ProxyServer. You can set this connection property to the following values :
| AUTO | Default setting. If ProxyServer is set to an HTTPS URL, the Sync App uses the TUNNEL option. If ProxyServer is set to an HTTP URL, the component uses the NEVER option. |
| ALWAYS | The connection is always SSL enabled. |
| NEVER | The connection is not SSL enabled. |
| TUNNEL | The connection is made through a tunneling proxy. The proxy server opens a connection to the remote host and traffic flows back and forth through the proxy. |
A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property.
The ProxyServer is used for all addresses, except for addresses defined in this property. Use semicolons to separate entries.
Note that the Sync App uses the system proxy settings by default, without further configuration needed. If you want to explicitly configure proxy exceptions for this connection, set ProxyAutoDetect to False.
This section provides a complete list of the Logging properties you can configure in the connection string for this provider.
| Property | Description |
| LogModules | Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged. |
Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged.
This property lets you customize the log file content by specifying the logging modules to include. Logging modules categorize logged information into distinct areas, such as query execution, metadata, or SSL communication. Each module is represented by a four-character code, with some requiring a trailing space for three-letter names.
For example, EXEC logs query execution, and INFO logs general provider messages. To include multiple modules, separate their names with semicolons as follows: INFO;EXEC;SSL.
The Verbosity connection property takes precedence over the module-based filtering specified by this property. Only log entries that meet the verbosity level and belong to the specified modules are logged. Leave this property blank to include all available modules in the log file.
For a complete list of available modules and detailed guidance on configuring logging, refer to the Advanced Logging section in Logging.
This section provides a complete list of the Schema properties you can configure in the connection string for this provider.
| Property | Description |
| Location | Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path. |
| BrowsableSchemas | Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC . |
| Tables | Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC . |
| Views | Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC . |
Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path.
The Location property is only needed if you want to either customize definitions (for example, change a column name, ignore a column, etc.) or extend the data model with new tables, views, or stored procedures.
If left unspecified, the default location is %APPDATA%\\CData\\Backlog Data Provider\\Schema, where %APPDATA% is set to the user's configuration directory:
| Platform | %APPDATA% |
| Windows | The value of the APPDATA environment variable |
| Linux | ~/.config |
Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC .
Listing all available database schemas can take extra time, thus degrading performance. Providing a list of schemas in the connection string saves time and improves performance.
Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC .
Listing all available tables from some databases can take extra time, thus degrading performance. Providing a list of tables in the connection string saves time and improves performance.
If there are lots of tables available and you already know which ones you want to work with, you can use this property to restrict your viewing to only those tables. To do this, specify the tables you want in a comma-separated list. Each table should be a valid SQL identifier with any special characters escaped using square brackets, double-quotes or backticks. For example, Tables=TableA,[TableB/WithSlash],WithCatalog.WithSchema.`TableC With Space`.
Note: If you are connecting to a data source with multiple schemas or catalogs, you must specify each table you want to view by its fully qualified name. This avoids ambiguity between tables that may exist in multiple catalogs or schemas.
Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC .
Listing all available views from some databases can take extra time, thus degrading performance. Providing a list of views in the connection string saves time and improves performance.
If there are lots of views available and you already know which ones you want to work with, you can use this property to restrict your viewing to only those views. To do this, specify the views you want in a comma-separated list. Each view should be a valid SQL identifier with any special characters escaped using square brackets, double-quotes or backticks. For example, Views=ViewA,[ViewB/WithSlash],WithCatalog.WithSchema.`ViewC With Space`.
Note: If you are connecting to a data source with multiple schemas or catalogs, you must specify each view you want to examine by its fully qualified name. This avoids ambiguity between views that may exist in multiple catalogs or schemas.
This section provides a complete list of the Miscellaneous properties you can configure in the connection string for this provider.
| Property | Description |
| IncludeCustomFields | Set this to true if you want to retrieve custom fields from the Issues table. |
| MaxRows | Specifies the maximum rows returned for queries without aggregation or GROUP BY. |
| MaxThreads | The Max Thread. |
| Other | Specifies additional hidden properties for specific use cases. These are not required for typical provider functionality. Use a semicolon-separated list to define multiple properties. |
| Pagesize | Specifies the maximum number of results to return from Backlog, per page. This setting overrides the default page size set by the datasource, which is optimized for most use cases. |
| ProjectId | Id of the specific project. |
| PseudoColumns | Specifies the pseudocolumns to expose as table columns. Use the format 'TableName=ColumnName;TableName=ColumnName'. The default is an empty string, which disables this property. |
| Timeout | Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error. The default is 60 seconds. Set to 0 to disable the timeout. |
| UserDefinedViews | Specifies a filepath to a JSON configuration file defining custom views. The provider automatically detects and uses the views specified in this file. |
Set this to true if you want to retrieve custom fields from the Issues table.
If set to true, the ProjectId connection property is also required.
Specifies the maximum rows returned for queries without aggregation or GROUP BY.
This property sets an upper limit on the number of rows the Sync App returns for queries that do not include aggregation or GROUP BY clauses. This limit ensures that queries do not return excessively large result sets by default.
When a query includes a LIMIT clause, the value specified in the query takes precedence over the MaxRows setting. If MaxRows is set to "-1", no row limit is enforced unless a LIMIT clause is explicitly included in the query.
This property is useful for optimizing performance and preventing excessive resource consumption when executing queries that could otherwise return very large datasets.
The Max Thread.
Specifies additional hidden properties for specific use cases. These are not required for typical provider functionality. Use a semicolon-separated list to define multiple properties.
This property allows advanced users to configure hidden properties for specialized scenarios. These settings are not required for normal use cases but can address unique requirements or provide additional functionality. Multiple properties can be defined in a semicolon-separated list.
Note: It is strongly recommended to set these properties only when advised by the support team to address specific scenarios or issues.
Specify multiple properties in a semicolon-separated list.
| DefaultColumnSize | Sets the default length of string fields when the data source does not provide column length in the metadata. The default value is 2000. |
| ConvertDateTimeToGMT | Determines whether to convert date-time values to GMT, instead of the local time of the machine. |
| RecordToFile=filename | Records the underlying socket data transfer to the specified file. |
Specifies the maximum number of results to return from Backlog, per page. This setting overrides the default page size set by the datasource, which is optimized for most use cases.
You may want to adjust the default pagesize to optimize results for a particular object or service endpoint you are querying. Be aware that increasing the page size may improve performance, but it could also result in higher memory consumption per page.
Id of the specific project.
Id of the specific project.
Specifies the pseudocolumns to expose as table columns. Use the format 'TableName=ColumnName;TableName=ColumnName'. The default is an empty string, which disables this property.
This property allows you to define which pseudocolumns the Sync App exposes as table columns.
To specify individual pseudocolumns, use the following format: "Table1=Column1;Table1=Column2;Table2=Column3"
To include all pseudocolumns for all tables use: "*=*"
Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error. The default is 60 seconds. Set to 0 to disable the timeout.
This property controls the maximum time, in seconds, that the Sync App waits for an operation to complete before canceling it. If the timeout period expires before the operation finishes, the Sync App cancels the operation and throws an exception.
The timeout applies to each individual communication with the server rather than the entire query or operation. For example, a query could continue running beyond 60 seconds if each paging call completes within the timeout limit.
Setting this property to 0 disables the timeout, allowing operations to run indefinitely until they succeed or fail due to other conditions such as server-side timeouts, network interruptions, or resource limits on the server. Use this property cautiously to avoid long-running operations that could degrade performance or result in unresponsive behavior.
Specifies a filepath to a JSON configuration file defining custom views. The provider automatically detects and uses the views specified in this file.
This property allows you to define and manage custom views through a JSON-formatted configuration file called UserDefinedViews.json. These views are automatically recognized by the Sync App and enable you to execute custom SQL queries as if they were standard database views. The JSON file defines each view as a root element with a child element called "query", which contains the SQL query for the view. For example:
{
"MyView": {
"query": "SELECT * FROM Issues WHERE MyColumn = 'value'"
},
"MyView2": {
"query": "SELECT * FROM MyTable WHERE Id IN (1,2,3)"
}
}
You can define multiple views in a single file and specify the filepath using this property. For example: UserDefinedViews=C:\Path\To\UserDefinedViews.json. When you use this property, only the specified views are seen by the Sync App.
Refer to User Defined Views for more information.