CData Cloud offers access to Backlog across several standard services and protocols, in a cloud-hosted solution. Any application that can connect to a MySQL or SQL Server database can connect to Backlog through CData Cloud.
CData Cloud allows you to standardize and configure connections to Backlog as though it were any other OData endpoint, or standard SQL Server/MySQL database.
This page provides a guide to Establishing a Connection to Backlog in CData Cloud, as well as information on the available resources, and a reference to the available connection properties.
Establishing a Connection shows how to authenticate to Backlog and configure any necessary connection properties to create a database in CData Cloud
Accessing data from Backlog through the available standard services and CData Cloud administration is documented in further details in the CData Cloud Documentation.
Connect to Backlog by selecting the corresponding icon in the Database tab. Required properties are listed under Settings. The Advanced tab lists connection properties that are not typically required.
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 path 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:
If you do not have access to the user name and password or do not wish to require them, you can use OAuth authentication. Backlog uses the OAuth authentication standard, which requires the authenticating user to interact with Backlog via the browser. The Cloud facilitates the OAuth exchange in various ways, as described in this section.
To obtain the OAuth client credentials, client key, and client secret:
After setting the following connection properties, you are ready to connect:
When you connect, the Cloud opens the OAuth endpoint in your default browser. Log in and grant permissions to the application. The Cloud then completes the following OAuth process:
To obtain the access token, set the following connection properties:
When connecting via a web application, or if the Cloud is not authorized to open a browser window, you need to exchange temporary verification values for the access token:
To connect to data, set the following connection properties:
To automatically refresh the access token when it expires, set InitiateOAuth to REFRESH and set OAuthRefreshToken. Alternatively, call the RefreshOAuthAccessToken stored procedure when the access token expires. Given a refresh token as input, the procedure returns a valid OAuth access token.
Date | Build Number | Change Type | Description |
12/14/2022 | 8383 | General | Changed
|
11/24/2022 | 8363 | Backlog | Added
|
10/04/2022 | 8312 | Backlog | Added
|
09/30/2022 | 8308 | General | Changed
|
08/17/2022 | 8264 | General | Changed
|
09/02/2021 | 7915 | General | Added
|
08/07/2021 | 7889 | General | Changed
|
08/06/2021 | 7888 | General | Changed
|
07/23/2021 | 7874 | General | Changed
|
07/08/2021 | 7859 | General | Added
|
04/23/2021 | 7785 | General | Added
|
04/23/2021 | 7783 | General | Changed
|
04/16/2021 | 7776 | General | Added
Changed
|
04/15 /2021 | 7775 | General | Changed
|
This section details a selection of advanced features of the Backlog Cloud.
The Cloud allows you to define virtual tables, called user defined views, whose contents are decided by a pre-configured query. These views are useful when you cannot directly control queries being issued to the drivers. See User Defined Views for an overview of creating and configuring custom views.
Use SSL Configuration to adjust how Cloud handles TLS/SSL certificate negotiations. You can choose from various certificate formats; see the SSLServerCert property under "Connection String Options" for more information.
Configure the Cloud for compliance with Firewall and Proxy, including Windows proxies and HTTP proxies. You can also set up tunnel connections.
The Cloud offloads as much of the SELECT statement processing as possible to Backlog and then processes the rest of the query in memory (client-side).
See Query Processing for more information.
See Logging for an overview of configuration settings that can be used to refine CData logging. For basic logging, you only need to set two connection properties, but there are numerous features that support more refined logging, where you can select subsets of information to be logged using the LogModules connection property.
The CData Cloud allows you to define a virtual table whose contents are decided by a pre-configured query. These are called User Defined Views, which are useful in situations where you cannot directly control the query being issued to the driver, e.g. when using the driver from a tool. The User Defined Views can be used to define predicates that are always applied. If you specify additional predicates in the query to the view, they are combined with the query already defined as part of the view.
There are two ways to create user defined views:
You can also have multiple view definitions and control them using the UserDefinedViews connection property. When you use this property, only the specified views are seen by the Cloud.
This User Defined View configuration file is formatted as follows:
For example:
{ "MyView": { "query": "SELECT * FROM Issues WHERE MyColumn = 'value'" }, "MyView2": { "query": "SELECT * FROM MyTable WHERE Id IN (1,2,3)" } }Use the UserDefinedViews connection property to specify the location of your JSON configuration file. For example:
"UserDefinedViews", "C:\\Users\\yourusername\\Desktop\\tmp\\UserDefinedViews.json"
SELECT * FROM Customers WHERE City = 'Raleigh';An example of a query to the driver:
SELECT * FROM UserViews.RCustomers WHERE Status = 'Active';Resulting in the effective query to the source:
SELECT * FROM Customers WHERE City = 'Raleigh' AND Status = 'Active';That is a very simple example of a query to a User Defined View that is effectively a combination of the view query and the view definition. It is possible to compose these queries in much more complex patterns. All SQL operations are allowed in both queries and are combined when appropriate.
By default, the Cloud attempts to negotiate SSL/TLS by checking the server's certificate against the system's trusted certificate store.
To specify another certificate, see the SSLServerCert property for the available formats to do so.
To connect through the Windows system proxy, you do not need to set any additional connection properties. To connect to other proxies, set ProxyAutoDetect to false.
In addition, to authenticate to an HTTP proxy, set ProxyAuthScheme, ProxyUser, and ProxyPassword, in addition to ProxyServer and ProxyPort.
Set the following properties:
For sources that do not support SQL-92, the Cloud offloads as much of SQL statement processing as possible to Backlog and then processes the rest of the query in memory (client-side). This results in optimal performance.
For data sources with limited query capabilities, the Cloud handles transformations of the SQL query to make it simpler for the Cloud. The goal is to make smart decisions based on the query capabilities of the data source to push down as much of the computation as possible. The Backlog Query Evaluation component examines SQL queries and returns information indicating what parts of the query the Cloud is not capable of executing natively.
The Backlog Query Slicer component is used in more specific cases to separate a single query into multiple independent queries. The client-side Query Engine makes decisions about simplifying queries, breaking queries into multiple queries, and pushing down or computing aggregations on the client-side while minimizing the size of the result set.
There's a significant trade-off in evaluating queries, even partially, client-side. There are always queries that are impossible to execute efficiently in this model, and some can be particularly expensive to compute in this manner. CData always pushes down as much of the query as is feasible for the data source to generate the most efficient query possible and provide the most flexible query capabilities.
Capturing Cloud logging can be very helpful when diagnosing error messages or other unexpected behavior.
You will simply need to set two connection properties to begin capturing Cloud logging.
Once this property is set, the Cloud will populate the log file as it carries out various tasks, such as when authentication is performed or queries are executed. If the specified file doesn't already exist, it will be created.
The verbosity level determines the amount of detail that the Cloud reports to the Logfile. Verbosity levels from 1 to 5 are supported. These are described in the following list:
1 | Setting Verbosity to 1 will log the query, the number of rows returned by it, the start of execution and the time taken, and any errors. |
2 | Setting Verbosity to 2 will log everything included in Verbosity 1 and additional information about the request. |
3 | Setting Verbosity to 3 will additionally log HTTP headers, as well as the body of the request and the response. |
4 | Setting Verbosity to 4 will additionally log transport-level communication with the data source. This includes SSL negotiation. |
5 | Setting Verbosity to 5 will additionally log communication with the data source and additional details that may be helpful in troubleshooting problems. This includes interface commands. |
The Verbosity should not be set to greater than 1 for normal operation. Substantial amounts of data can be logged at higher verbosities, which can delay execution times.
To refine the logged content further by showing/hiding specific categories of information, see LogModules.
Best Practices for Data Security
Although we mask sensitive values, such as passwords, in the connection string and any request in the log, it is always best practice to review the logs for any sensitive information before sharing outside your organization.
You may want to refine the exact information that is recorded to the log file. This can be accomplished using the LogModules property.
This property allows you to filter the logging using a semicolon-separated list of logging modules.
All modules are four characters long. Please note that modules containing three letters have a required trailing blank space. The available modules are:
LogModules=INFO;EXEC;SSL ;SQL ;META;
Note that these modules refine the information as it is pulled after taking the Verbosity into account.
The CData Cloud supports several operations on data, including querying, deleting, modifying, and inserting.
See SELECT Statements for a syntax reference and examples.
See Data Model for information on the capabilities of the Backlog API.
See INSERT Statements for a syntax reference and examples.
The primary key Id is required to update a record. See UPDATE Statements for a syntax reference and examples.
The primary key Id is required to delete a record. See DELETE Statements for a syntax reference and examples.
Use EXECUTE or EXEC statements to execute stored procedures. See EXECUTE Statements for a syntax reference and examples.
A SELECT statement can consist of the following basic clauses.
The following syntax diagram outlines the syntax supported by the SQL engine of the Cloud:
SELECT {
[ TOP <numeric_literal> | DISTINCT ]
{
*
| {
<expression> [ [ AS ] <column_reference> ]
| { <table_name> | <correlation_name> } .*
} [ , ... ]
}
[ INTO csv:// [ filename= ] <file_path> [ ;delimiter=tab ] ]
{
FROM <table_reference> [ [ AS ] <identifier> ]
} [ , ... ]
[ [
INNER | { { LEFT | RIGHT | FULL } [ OUTER ] }
] JOIN <table_reference> [ ON <search_condition> ] [ [ AS ] <identifier> ]
] [ ... ]
[ WHERE <search_condition> ]
[ GROUP BY <column_reference> [ , ... ]
[ HAVING <search_condition> ]
[ UNION [ ALL ] <select_statement> ]
[
ORDER BY
<column_reference> [ ASC | DESC ] [ NULLS FIRST | NULLS LAST ]
]
[
LIMIT <expression>
[
{ OFFSET | , }
<expression>
]
]
} | SCOPE_IDENTITY()
<expression> ::=
| <column_reference>
| @ <parameter>
| ?
| COUNT( * | { [ DISTINCT ] <expression> } )
| { AVG | MAX | MIN | SUM | COUNT } ( <expression> )
| NULLIF ( <expression> , <expression> )
| COALESCE ( <expression> , ... )
| CASE <expression>
WHEN { <expression> | <search_condition> } THEN { <expression> | NULL } [ ... ]
[ ELSE { <expression> | NULL } ]
END
| <literal>
| <sql_function>
<search_condition> ::=
{
<expression> { = | > | < | >= | <= | <> | != | LIKE | NOT LIKE | IN | NOT IN | IS NULL | IS NOT NULL | AND | OR | CONTAINS | BETWEEN } [ <expression> ]
} [ { AND | OR } ... ]
SELECT * FROM Issues
SELECT [ProjectID] AS MY_ProjectID FROM Issues
SELECT CAST(AnnualRevenue AS VARCHAR) AS Str_AnnualRevenue FROM Issues
SELECT * FROM Issues WHERE StatusID = '1'
SELECT COUNT(*) AS MyCount FROM Issues
SELECT COUNT(DISTINCT ProjectID) FROM Issues
SELECT DISTINCT ProjectID FROM Issues
SELECT ProjectID, MAX(AnnualRevenue) FROM Issues GROUP BY ProjectIDSee Aggregate Functions for details.
SELECT Projects.Id, Projects.ProjectKey, Issues.IssueKey, Issues.KeyId FROM Projects INNER JOIN Issues ON Projects.Id = Issues.ProjectIdSee JOIN Queries for details.
SELECT Id, ProjectID FROM Issues ORDER BY ProjectID ASC
SELECT Id, ProjectID FROM Issues LIMIT 10
SELECT * FROM Issues WHERE StatusID = @param
Some input-only fields are available in SELECT statements. These fields, called pseudo columns, do not
appear as regular columns in the results, yet may be specified as part of the WHERE clause. You can use pseudo columns to access additional features from Backlog.
SELECT * FROM Issues WHERE Category = '3'
Returns the number of rows matching the query criteria.
SELECT COUNT(*) FROM Issues WHERE StatusID = '1'
Returns the number of distinct, non-null field values matching the query criteria.
SELECT COUNT(DISTINCT Id) AS DistinctValues FROM Issues WHERE StatusID = '1'
Returns the average of the column values.
SELECT ProjectID, AVG(AnnualRevenue) FROM Issues WHERE StatusID = '1' GROUP BY ProjectID
Returns the minimum column value.
SELECT MIN(AnnualRevenue), ProjectID FROM Issues WHERE StatusID = '1' GROUP BY ProjectID
Returns the maximum column value.
SELECT ProjectID, MAX(AnnualRevenue) FROM Issues WHERE StatusID = '1' GROUP BY ProjectID
Returns the total sum of the column values.
SELECT SUM(AnnualRevenue) FROM Issues WHERE StatusID = '1'
The CData Cloud supports standard SQL joins like the following examples.
An inner join selects only rows from both tables that match the join condition:
SELECT Projects.Id, Projects.ProjectKey, Issues.IssueKey, Issues.KeyId FROM Projects INNER JOIN Issues ON Projects.Id = Issues.ProjectId
A left join selects all rows in the FROM table and only matching rows in the JOIN table:
SELECT Projects.Id, Projects.ProjectKey, Issues.IssueKey, Issues.KeyId FROM Projects LEFT JOIN Issues ON Projects.Id = Issues.ProjectId
The following date literal functions can be used to filter date fields using relative intervals. Note that while the <, >, and = operators are supported for these functions, <= and >= are not.
The current day.
SELECT * FROM MyTable WHERE MyDateField = L_TODAY()
The previous day.
SELECT * FROM MyTable WHERE MyDateField = L_YESTERDAY()
The following day.
SELECT * FROM MyTable WHERE MyDateField = L_TOMORROW()
Every day in the preceding week.
SELECT * FROM MyTable WHERE MyDateField = L_LAST_WEEK()
Every day in the current week.
SELECT * FROM MyTable WHERE MyDateField = L_THIS_WEEK()
Every day in the following week.
SELECT * FROM MyTable WHERE MyDateField = L_NEXT_WEEK()Also available:
The previous n days, excluding the current day.
SELECT * FROM MyTable WHERE MyDateField = L_LAST_N_DAYS(3)
The following n days, including the current day.
SELECT * FROM MyTable WHERE MyDateField = L_NEXT_N_DAYS(3)Also available:
Every day in every week, starting n weeks before current week, and ending in the previous week.
SELECT * FROM MyTable WHERE MyDateField = L_LAST_N_WEEKS(3)
Every day in every week, starting the following week, and ending n weeks in the future.
SELECT * FROM MyTable WHERE MyDateField = L_NEXT_N_WEEKS(3)Also available:
You can use the SELECT INTO statement to export formatted data to a file.
The following query exports data into a file formatted in comma-separated values (CSV):
SELECT Id, ProjectID INTO [csv://Issues.txt] FROM [Issues] WHERE StatusID = '1'You can specify other formats in the file URI. The possible delimiters are tab, semicolon, and comma with the default being a comma. The following example exports tab-separated values:
SELECT Id, ProjectID INTO [csv://Issues.txt;delimiter=tab] FROM [Issues] WHERE StatusID = '1'You can specify other file formats in the URI. The following example exports tab-separated values:
The Cloud provides functions that are similar to those that are available with most standard databases. These functions are implemented in the CData provider engine and thus are available across all data sources with the same consistent API. Three categories of functions are available: string, date, and math.
The Cloud interprets all SQL function inputs as either strings or column identifiers, so you need to escape all literals as strings, with single quotes. For example, contrast the SQL Server syntax and Cloud syntax for the DATENAME function:
SELECT DATENAME(yy,GETDATE())
SELECT DATENAME('yy',GETDATE())
These functions perform string manipulations and return a string value. See STRING Functions for more details.
SELECT CONCAT(firstname, space(4), lastname) FROM Issues WHERE StatusID = '1'
These functions perform date and date time manipulations. See DATE Functions for more details.
SELECT CURRENT_TIMESTAMP() FROM Issues
These functions provide mathematical operations. See MATH Functions for more details.
SELECT RAND() FROM Issues
SELECT CONCAT('Mr.', SPACE(2), firstname, SPACE(4), lastname) FROM Issues
Returns the ASCII code value of the left-most character of the character expression.
SELECT ASCII('0'); -- Result: 48
Converts the integer ASCII code to the corresponding character.
SELECT CHAR(48); -- Result: '0'
Returns the starting position of the specified expression in the character string.
SELECT CHARINDEX('456', '0123456'); -- Result: 4 SELECT CHARINDEX('456', '0123456', 5); -- Result: -1
Returns the number of UTF-8 characters present in the expression.
SELECT CHAR_LENGTH('sample text') FROM Account LIMIT 1 -- Result: 11
Returns the string that is the concatenation of two or more string values.
SELECT CONCAT('Hello, ', 'world!'); -- Result: 'Hello, world!'
Returns 1 if expressionToFind is found within expressionToSearch; otherwise, 0.
SELECT CONTAINS('0123456', '456'); -- Result: 1 SELECT CONTAINS('0123456', 'Not a number'); -- Result: 0
Returns 1 if character_expression ends with character_suffix; otherwise, 0.
SELECT ENDSWITH('0123456', '456'); -- Result: 1 SELECT ENDSWITH('0123456', '012'); -- Result: 0
Returns the number of bytes present in the file at the specified file path.
SELECT FILESIZE('C:/Users/User1/Desktop/myfile.txt'); -- Result: 23684
Returns the value formatted with the specified format.
SELECT FORMAT(12.34, '#'); -- Result: 12 SELECT FORMAT(12.34, '#.###'); -- Result: 12.34 SELECT FORMAT(1234, '0.000E0'); -- Result: 1.234E3 SELECT FORMAT('2019/01/01', 'yyyy-MM-dd'); -- Result: 2019-01-01 SELECT FORMAT('20190101', 'yyyyMMdd', 'yyyy-MM-dd'); -- Result: '2019-01-01'
Returns a representation of the unix_timestamp argument as a value in YYYY-MM-DD HH:MM:SS expressed in the current time zone.
SELECT FROM_UNIXTIME(1540495231, 1); -- Result: 2018-10-25 19:20:31 SELECT FROM_UNIXTIME(1540495357385, 0); -- Result: 2018-10-25 19:22:37
Returns the hash of the input value as a byte array using the given algorithm. The supported algorithms are MD5, SHA1, SHA2_256, SHA2_512, SHA3_224, SHA3_256, SHA3_384, and SHA3_512.
SELECT HASHBYTES('MD5', 'Test'); -- Result (byte array): 0x0CBC6611F5540BD0809A388DC95A615B
Returns the starting position of the specified expression in the character string.
SELECT INDEXOF('0123456', '456'); -- Result: 4 SELECT INDEXOF('0123456', '456', 5); -- Result: -1
Replaces null with the specified replacement value.
SELECT ISNULL(42, 'Was NULL'); -- Result: 42 SELECT ISNULL(NULL, 'Was NULL'); -- Result: 'Was NULL'
Computes the average value of a JSON array within a JSON object. The path to the array is specified in the jsonpath argument. Return value is numeric or null.
SELECT JSON_AVG('[1,2,3,4,5]', '$[x]'); -- Result: 3 SELECT JSON_AVG('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[x]'); -- Result: 3 SELECT JSON_AVG('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[3..]'); -- Result: 4.5
Returns the number of elements in a JSON array within a JSON object. The path to the array is specified in the jsonpath argument. Return value is numeric or null.
SELECT JSON_COUNT('[1,2,3,4,5]', '$[x]'); -- Result: 5 SELECT JSON_COUNT('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[x]'); -- Result: 5 SELECT JSON_COUNT('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[3..]'); -- Result: 2
Selects any value in a JSON array or object. The path to the array is specified in the jsonpath argument. Return value is numeric or null.
SELECT JSON_EXTRACT('{"test": {"data": 1}}', '$.test'); -- Result: '{"data":1}' SELECT JSON_EXTRACT('{"test": {"data": 1}}', '$.test.data'); -- Result: 1 SELECT JSON_EXTRACT('{"test": {"data": [1, 2, 3]}}', '$.test.data[1]'); -- Result: 2
Gets the maximum value in a JSON array within a JSON object. The path to the array is specified in the jsonpath argument. Return value is numeric or null.
SELECT JSON_MAX('[1,2,3,4,5]', '$[x]'); -- Result: 5 SELECT JSON_MAX('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[x]'); -- Result: 5 SELECT JSON_MAX('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[..3]'); -- Result: 4
Gets the minimum value in a JSON array within a JSON object. The path to the array is specified in the jsonpath argument. Return value is numeric or null.
SELECT JSON_MIN('[1,2,3,4,5]', '$[x]'); -- Result: 1 SELECT JSON_MIN('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[x]'); -- Result: 1 SELECT JSON_MIN('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[3..]'); -- Result: 4
Computes the summary value in JSON according to the JSONPath expression. Return value is numeric or null.
SELECT JSON_SUM('[1,2,3,4,5]', '$[x]'); -- Result: 15 SELECT JSON_SUM('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[x]'); -- Result: 15 SELECT JSON_SUM('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[3..]'); -- Result: 9
Returns the specified number of characters counting from the left of the specified string.
SELECT LEFT('1234567890', 3); -- Result: '123'
Returns the number of characters of the specified string expression.
SELECT LEN('12345'); -- Result: 5
Returns an integer representing how many characters into the string the substring appears.
SELECT LOCATE('sample','XXXXXsampleXXXXX'); -- Result: 6
Returns the character expression with the uppercase character data converted to lowercase.
SELECT LOWER('MIXED case'); -- Result: 'mixed case'
Returns the character expression with leading blanks removed.
SELECT LTRIM(' trimmed'); -- Result: 'trimmed'
Replaces the characters between start_index and end_index with the mask_character within the string.
SELECT MASK('1234567890','*',); -- Result: '**********' SELECT MASK('1234567890','*', 4); -- Result: '1234******' SELECT MASK('1234567890','*', 4, 2); -- Result: '1234****90'
Returns the Unicode character with the specified integer code as defined by the Unicode standard.
Returns the number of bytes present in the expression.
SELECT OCTET_LENGTH('text') FROM Account LIMIT 1 -- Result: 4
Returns the starting position of the first occurrence of the pattern in the expression. Returns 0 if the pattern is not found.
SELECT PATINDEX('123%', '1234567890'); -- Result: 1 SELECT PATINDEX('%890', '1234567890'); -- Result: 8 SELECT PATINDEX('%456%', '1234567890'); -- Result: 4
Returns the starting position of the specified expression in the character string.
SELECT POSITION('456' IN '123456'); -- Result: 4 SELECT POSITION('x' IN '123456'); -- Result: 0
Returns a valid SQL Server-delimited identifier by adding the necessary delimiters to the specified Unicode string.
SELECT QUOTENAME('table_name'); -- Result: '[table_name]' SELECT QUOTENAME('table_name', '"'); -- Result: '"table_name"' SELECT QUOTENAME('table_name', '['); -- Result: '[table_name]'
Replaces all occurrences of a string with another string.
SELECT REPLACE('1234567890', '456', '|'); -- Result: '123|7890' SELECT REPLACE('123123123', '123', '.'); -- Result: '...' SELECT REPLACE('1234567890', 'a', 'b'); -- Result: '1234567890'
Repeats the string value the specified number of times.
SELECT REPLACE('x', 5); -- Result: 'xxxxx'
Returns the reverse order of the string expression.
SELECT REVERSE('1234567890'); -- Result: '0987654321'
Returns the right part of the string with the specified number of characters.
SELECT RIGHT('1234567890', 3); -- Result: '890'
Returns the character expression after it removes trailing blanks.
SELECT RTRIM('trimmed '); -- Result: 'trimmed'
Returns the four-character Soundex code, based on how the string sounds when spoken.
SELECT SOUNDEX('smith'); -- Result: 'S530'
Returns the string that consists of repeated spaces.
SELECT SPACE(5); -- Result: ' '
Returns a section of the string between to delimiters.
SELECT SPLIT('a/b/c/d', '/', 1); -- Result: 'a' SELECT SPLIT('a/b/c/d', '/', -2); -- Result: 'c'
Returns 1 if character_expression starts with character_prefix; otherwise, 0.
SELECT STARTSWITH('0123456', '012'); -- Result: 1 SELECT STARTSWITH('0123456', '456'); -- Result: 0
Returns the character data converted from the numeric data. For example, STR(123.45, 6, 1) returns 123.5.
SELECT STR('123.456'); -- Result: '123' SELECT STR('123.456', 2); -- Result: '**' SELECT STR('123.456', 10, 2); -- Result: '123.46'
Inserts a string into another string. It deletes the specified length of characters in the first string at the start position and then inserts the second string into the first string at the start position.
SELECT STUFF('1234567890', 3, 2, 'xx'); -- Result: '12xx567890'
Returns the part of the string with the specified length; starts at the specified index.
SELECT SUBSTRING('1234567890' FROM 3 FOR 2); -- Result: '34' SELECT SUBSTRING('1234567890' FROM 3); -- Result: '34567890'
Converts the value of this instance to its equivalent string representation.
SELECT TOSTRING(123); -- Result: '123' SELECT TOSTRING(123.456); -- Result: '123.456' SELECT TOSTRING(null); -- Result: ''
Returns the character expression with leading and/or trailing blanks removed.
SELECT TRIM(' trimmed '); -- Result: 'trimmed' SELECT TRIM(LEADING FROM ' trimmed '); -- Result: 'trimmed ' SELECT TRIM('-' FROM '-----trimmed-----'); -- Result: 'trimmed' SELECT TRIM(BOTH '-' FROM '-----trimmed-----'); -- Result: 'trimmed' SELECT TRIM(TRAILING '-' FROM '-----trimmed-----'); -- Result: '-----trimmed'
Returns the integer value defined by the Unicode standard of the first character of the input expression.
Returns the character expression with lowercase character data converted to uppercase.
SELECT UPPER('MIXED case'); -- Result: 'MIXED CASE'
Extracts an XML document using the specified XPath to flatten the XML. A comma is used to separate the outputs by default, but this can be changed by specifying the third parameter.
SELECT XML_EXTRACT('<vowels><ch>a</ch><ch>e</ch><ch>i</ch><ch>o</ch><ch>u</ch></vowels>', '/vowels/ch'); -- Result: 'a,e,i,o,u' SELECT XML_EXTRACT('<vowels><ch>a</ch><ch>e</ch><ch>i</ch><ch>o</ch><ch>u</ch></vowels>', '/vowels/ch', ';'); -- Result: 'a;e;i;o;u'
Returns the current date value.
SELECT CURRENT_DATE(); -- Result: 2018-02-01
Returns the current time stamp of the database system as a datetime value. This value is equal to GETDATE and SYSDATETIME, and is always in the local timezone.
SELECT CURRENT_TIMESTAMP(); -- Result: 2018-02-01 03:04:05
Returns the datetime value that results from adding the specified number (a signed integer) to the specified date part of the date.
SELECT DATEADD('d', 5, '2018-02-01'); -- Result: 2018-02-06 SELECT DATEADD('hh', 5, '2018-02-01 00:00:00'); -- Result: 2018-02-01 05:00:00
Returns the difference (a signed integer) of the specified time interval between the specified start date and end date.
SELECT DATEDIFF('d', '2018-02-01', '2018-02-10'); -- Result: 9 SELECT DATEDIFF('hh', '2018-02-01 00:00:00', '2018-02-01 12:00:00'); -- Result: 12
Returns the datetime value for the specified year, month, and day.
SELECT DATEFROMPARTS(2018, 2, 1); -- Result: 2018-02-01
Returns the character string that represents the specified date part of the specified date.
SELECT DATENAME('yy', '2018-02-01'); -- Result: '2018' SELECT DATENAME('dw', '2018-02-01'); -- Result: 'Thursday'
Returns a character string that represents the specified date part of the specified date.
SELECT DATEPART('yy', '2018-02-01'); -- Result: 2018 SELECT DATEPART('dw', '2018-02-01'); -- Result: 5
Returns the datetime value for the specified date parts.
SELECT DATETIME2FROMPARTS(2018, 2, 1, 1, 2, 3, 456, 3); -- Result: 2018-02-01 01:02:03.456
Returns the datetime value for the specified date parts.
SELECT DATETIMEFROMPARTS(2018, 2, 1, 1, 2, 3, 456); -- Result: 2018-02-01 01:02:03.456
Truncates the date to the precision of the given date part. Modeled after the Oracle TRUNC function.
SELECT DATE_TRUNC('05-04-2005', 'YY'); -- Result: '1/1/2005' SELECT DATE_TRUNC('05-04-2005', 'MM'); -- Result: '5/1/2005'
Truncates the date to the precision of the given date part. Modeled after the PostgreSQL date_trunc function.
SELECT DATE_TRUNC2('year', '2020-02-04'); -- Result: '2020-01-01' SELECT DATE_TRUNC2('week', '2020-02-04', 'monday'); -- Result: '2020-02-02', which is the previous Monday
Returns the integer that specifies the day component of the specified date.
SELECT DAY('2018-02-01'); -- Result: 1
SELECT DAYOFMONTH('04/15/2000'); -- Result: 15
SELECT DAYOFWEEK('04/15/2000'); -- Result: 7
SELECT DAYOFYEAR('04/15/2000'); -- Result: 106
Returns the last day of the month that contains the specified date with an optional offset.
SELECT EOMONTH('2018-02-01'); -- Result: 2018-02-28 SELECT LAST_DAY('2018-02-01'); -- Result: 2018-02-28 SELECT EOMONTH('2018-02-01', 2); -- Result: 2018-04-30
SELECT FDWEEK('02-08-2018'); -- Result: 2/4/2018
SELECT FDMONTH('02-08-2018'); -- Result: 2/1/2018
SELECT FDQUARTER('05-08-2018'); -- Result: 4/1/2018
Returns the time stamp associated with the Date Modified of the relevant file.
SELECT FILEMODIFIEDTIME('C:/Documents/myfile.txt'); -- Result: 6/25/2019 10:06:58 AM
Returns a date derived from the number of days after 1582-10-15 (based upon the Gregorian calendar). This will be equivalent to the MYSQL FROM_DAYS function.
SELECT FROM_DAYS(736000); -- Result: 2/6/2015
Returns the current time stamp of the database system as a datetime value. This value is equal to CURRENT_TIMESTAMP and SYSDATETIME, and is always in the local timezone.
SELECT GETDATE(); -- Result: 2018-02-01 03:04:05
Returns the current time stamp of the database system formatted as a UTC datetime value. This value is equal to SYSUTCDATETIME.
SELECT GETUTCDATE(); -- For example, if the local timezone is Eastern European Time (GMT+2) -- Result: 2018-02-01 05:04:05
Returns the hour component from the provided datetime.
SELECT HOUR('02-02-2020 11:30:00'); -- Result: 11
Returns 1 if the value is a valid date, time, or datetime value; otherwise, 0.
SELECT ISDATE('2018-02-01', 'yyyy-MM-dd'); -- Result: 1 SELECT ISDATE('Not a date'); -- Result: 0
Returns a time stamp equivalent to exactly one week before the current date.
SELECT LAST_WEEK(); //Assume the date is 3/17/2020 -- Result: 3/10/2020
Returns a time stamp equivalent to exactly one month before the current date.
SELECT LAST_MONTH(); //Assume the date is 3/17/2020 -- Result: 2/17/2020
Returns a time stamp equivalent to exactly one year before the current date.
SELECT LAST_YEAR(); //Assume the date is 3/17/2020 -- Result: 3/10/2019
Returns the last day of the provided week.
SELECT LDWEEK('02-02-2020'); -- Result: 2/8/2020
Returns the last day of the provided month.
SELECT LDMONTH('02-02-2020'); -- Result: 2/29/2020
Returns the last day of the provided quarter.
SELECT LDQUARTER('02-02-2020'); -- Result: 3/31/2020
Returns a date value from a year and a number of days.
SELECT MAKEDATE(2020, 1); -- Result: 2020-01-01
Returns the minute component from the provided datetime.
SELECT MINUTE('02-02-2020 11:15:00'); -- Result: 15
Returns the month component from the provided datetime.
SELECT MONTH('02-02-2020'); -- Result: 2
Returns the quarter associated with the provided datetime.
SELECT QUARTER('02-02-2020'); -- Result: 1
Returns the second component from the provided datetime.
SELECT SECOND('02-02-2020 11:15:23'); -- Result: 23
Returns the datetime value for the specified date and time.
SELECT SMALLDATETIMEFROMPARTS(2018, 2, 1, 1, 2); -- Result: 2018-02-01 01:02:00
Parses the provided string value and returns the corresponding datetime.
SELECT STRTODATE('03*04*2020','dd*MM*yyyy'); -- Result: 4/3/2020
Returns the current time stamp as a datetime value of the database system. It is equal to GETDATE and CURRENT_TIMESTAMP, and is always in the local timezone.
SELECT SYSDATETIME(); -- Result: 2018-02-01 03:04:05
Returns the current system date and time as a UTC datetime value. It is equal to GETUTCDATE.
SELECT SYSUTCDATETIME(); -- For example, if the local timezone is Eastern European Time (GMT+2) -- Result: 2018-02-01 05:04:05
Returns the time value for the specified time and with the specified precision.
SELECT TIMEFROMPARTS(1, 2, 3, 456, 3); -- Result: 01:02:03.456
Returns the number of days since 0000-00-01. This will only return a value for dates on or after 1582-10-15 (based upon the Gregorian calendar). This will be equivalent to the MYSQL TO_DAYS function.
SELECT TO_DAYS('02-06-2015'); -- Result: 736000
Returns the week (of the year) associated with the provided datetime.
SELECT WEEK('02-17-2020 11:15:23'); -- Result: 8
Returns the integer that specifies the year of the specified date.
SELECT YEAR('2018-02-01'); -- Result: 2018
Returns the absolute (positive) value of the specified numeric expression.
SELECT ABS(15); -- Result: 15 SELECT ABS(-15); -- Result: 15
Returns the arc cosine, the angle in radians whose cosine is the specified float expression.
SELECT ACOS(0.5); -- Result: 1.0471975511966
Returns the arc sine, the angle in radians whose sine is the specified float expression.
SELECT ASIN(0.5); -- Result: 0.523598775598299
Returns the arc tangent, the angle in radians whose tangent is the specified float expression.
SELECT ATAN(10); -- Result: 1.47112767430373
Returns the angle in radians between the positive x-axis and the ray from the origin to the point (y, x) where x and y are the values of the two specified float expressions.
SELECT ATN2(1, 1); -- Result: 0.785398163397448
Returns the smallest integer greater than or equal to the specified numeric expression.
SELECT CEILING(1.3); -- Result: 2 SELECT CEILING(1.5); -- Result: 2 SELECT CEILING(1.7); -- Result: 2
Returns the trigonometric cosine of the specified angle in radians in the specified expression.
SELECT COS(1); -- Result: 0.54030230586814
Returns the trigonometric cotangent of the angle in radians specified by float_expression.
SELECT COT(1); -- Result: 0.642092615934331
Returns the angle in degrees for the angle specified in radians.
SELECT DEGREES(3.1415926); -- Result: 179.999996929531
Returns the exponential value of the specified float expression. For example, EXP(LOG(20)) is 20.
SELECT EXP(2); -- Result: 7.38905609893065
Evaluates the expression.
SELECT EXPR('1 + 2 * 3'); -- Result: 7 SELECT EXPR('1 + 2 * 3 == 7'); -- Result: true
Returns the largest integer less than or equal to the numeric expression.
SELECT FLOOR(1.3); -- Result: 1 SELECT FLOOR(1.5); -- Result: 1 SELECT FLOOR(1.7); -- Result: 1
Returns the greatest of the supplied integers.
SELECT GREATEST(3,5,8,10,1) -- Result: 10
Returns a the equivalent hex for the input value.
SELECT HEX(866849198); -- Result: 33AB11AE SELECT HEX('Sample Text'); -- Result: 53616D706C652054657874
Returns the least of the supplied integers.
SELECT LEAST(3,5,8,10,1) -- Result: 1
Returns the natural logarithm of the specified float expression.
SELECT LOG(7.3890560); -- Result: 1.99999998661119
Returns the base-10 logarithm of the specified float expression.
SELECT LOG10(10000); -- Result: 4
Returns the integer value associated with the remainder when dividing the dividend by the divisor.
SELECT MOD(10,3); -- Result: 1
Returns the opposite to the real number input.
SELECT NEGATE(10); -- Result: -10 SELECT NEGATE(-12.4) --Result: 12.4
Returns the constant value of pi.
SELECT PI() -- Result: 3.14159265358979
Returns the value of the specified expression raised to the specified power.
SELECT POWER(2, 10); -- Result: 1024 SELECT POWER(2, -2); -- Result: 0.25
Returns the angle in radians of the angle in degrees.
SELECT RADIANS(180); -- Result: 3.14159265358979
Returns a pseudorandom float value from 0 through 1, exclusive.
SELECT RAND(); -- This result may be different, since the seed is randomized -- Result: 0.873159630165044 SELECT RAND(1); -- This result will always be the same, since the seed is constant -- Result: 0.248668584157093
Returns the numeric value rounded to the specified length or precision.
SELECT ROUND(1.3, 0); -- Result: 1 SELECT ROUND(1.55, 1); -- Result: 1.6 SELECT ROUND(1.7, 0, 0); -- Result: 2 SELECT ROUND(1.7, 0, 1); -- Result: 1 SELECT ROUND (1.24); -- Result: 1.0
Returns the positive sign (1), 0, or negative sign (-1) of the specified expression.
SELECT SIGN(0); -- Result: 0 SELECT SIGN(10); -- Result: 1 SELECT SIGN(-10); -- Result: -1
Returns the trigonometric sine of the angle in radians.
SELECT SIN(1); -- Result: 0.841470984807897
Returns the square root of the specified float value.
SELECT SQRT(100); -- Result: 10
Returns the square of the specified float value.
SELECT SQUARE(10); -- Result: 100 SELECT SQUARE(-10); -- Result: 100
Returns the tangent of the input expression.
SELECT TAN(1); -- Result: 1.5574077246549
Returns the supplied decimal number truncated to have the supplied decimal precision.
SELECT TRUNC(10.3423,2); -- Result: 10.34
To create new records, use INSERT statements.
The INSERT statement specifies the columns to be inserted and the new column values. You can specify the column values in a comma-separated list in the VALUES clause, as shown in the following example:
INSERT INTO <table_name>
( <column_reference> [ , ... ] )
VALUES
( { <expression> | NULL } [ , ... ] )
<expression> ::=
| @ <parameter>
| ?
| <literal>
The following is an example query:
INSERT INTO Issues (ProjectID) VALUES ('John')
To modify existing records, use UPDATE statements.
The UPDATE statement takes as input a comma-separated list of columns and new column values as name-value pairs in the SET clause, as shown in the following example:
UPDATE <table_name> SET { <column_reference> = <expression> } [ , ... ] WHERE { Id = <expression> } [ { AND | OR } ... ]
<expression> ::=
| @ <parameter>
| ?
| <literal>
The following is an example query:
UPDATE Issues SET ProjectID='John' WHERE Id = @myId
To delete information from a table, use DELETE statements.
The DELETE statement requires the table name in the FROM clause and the row's primary key in the WHERE clause, as shown in the following example:
<delete_statement> ::= DELETE FROM <table_name> WHERE { Id = <expression> } [ { AND | OR } ... ]
<expression> ::=
| @ <parameter>
| ?
| <literal>
The following is an example query:
DELETE FROM Issues WHERE Id = @myId
To execute stored procedures, you can use EXECUTE or EXEC statements.
EXEC and EXECUTE assign stored procedure inputs, referenced by name, to values or parameter names.
To execute a stored procedure as an SQL statement, use the following syntax:
{ EXECUTE | EXEC } <stored_proc_name>
{
[ @ ] <input_name> = <expression>
} [ , ... ]
<expression> ::=
| @ <parameter>
| ?
| <literal>
Reference stored procedure inputs by name:
EXECUTE my_proc @second = 2, @first = 1, @third = 3;
Execute a parameterized stored procedure statement:
EXECUTE my_proc second = @p1, first = @p2, third = @p3;
PIVOT and UNPIVOT can be used to change a table-valued expression into another table.
"SELECT 'AverageCost' AS Cost_Sorted_By_Production_Days, [0], [1], [2], [3], [4]
FROM
(
SELECT DaysToManufacture, StandardCost
FROM Production.Product
) AS SourceTable
PIVOT
(
AVG(StandardCost)
FOR DaysToManufacture IN ([0], [1], [2], [3], [4])
) AS PivotTable;"
"SELECT VendorID, Employee, Orders
FROM
(SELECT VendorID, Emp1, Emp2, Emp3, Emp4, Emp5
FROM pvt) p
UNPIVOT
(Orders FOR Employee IN
(Emp1, Emp2, Emp3, Emp4, Emp5)
)AS unpvt;"
For further information on PIVOT and UNPIVOT, see FROM clause plus JOIN, APPLY, PIVOT (Transact-SQL)
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 Cloud models the data in Backlog into a list of tables that can be queried using standard SQL statements.
Generally, querying Backlog tables is the same as querying a table in a relational database. Sometimes there are special cases, for example, including a certain column in the WHERE clause might be required to get data for certain columns in the table. This is typically needed for situations where a separate request must be made for each row to get certain columns. These types of situations are clearly documented at the top of the table page linked below.
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 Cloud 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 Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueAttachments WHERE IssueId=6840954You can turn off client-side execution by setting SupportEnhancedSQL to false in which case any search criteria that refers to other columns will cause an error.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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)
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 | |
Resolutions | 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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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
Delete can be executed by specifying the ProjectId, ID AND SubstituteStatusId.
DELETE FROM ProjectIssueTypes WHERE ProjectId = 114706 AND Id = 530958 AND SubstituteStatusId = 343433
Name | Type | ReadOnly | Description |
ProjectId [KEY] | Int | False | |
Id [KEY] | Int | False | |
Name | String | False | |
Color | String | False | |
DisplayOrder | Int | False | |
TemplateSummary | String | False | |
TemplateDescription | 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 |
SubstituteStatusId | String |
Returns data from projects table.
The Cloud 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 Cloud.
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 Cloud 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 Cloud.
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
Delete can be executed by specifying the IssueId, ID AND SubstituteStatusId.
DELETE FROM ProjectStatuses WHERE ProjectId = 114706 AND Id = 18528 AND SubstituteStatusId = 343433
Name | Type | ReadOnly | Description |
Id [KEY] | Int | False | |
ProjectId [KEY] | Int | False | |
Name | String | False | |
Color | String | False | |
DisplayOrder | Int | 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 |
SubstituteStatusId | String |
Returns data from project teams table.
The Cloud 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 Cloud.
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 Cloud 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 Cloud.
For example, the following query is processed server side:
SELECT * FROM ProjectUsers WHERE ProjectId=114706You can turn off client-side execution by setting SupportEnhancedSQL to false in which case any search criteria that refers to other columns will cause an error.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 composed of columns and pseudo columns. Views are similar to tables in the way that data is represented; however, views do not support updates. Entities that are represented as views are typically read-only entities. Often, a stored procedure is available to update the data if such functionality is applicable to the data source.
Queries can be executed against a view as if it were a normal table, and the data that comes back is similar in that regard.
Dynamic views, such as queries exposed as views, and views for looking up specific combinations of project_team work items are supported.
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 Cloud 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 Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueCategories WHERE IssueId=6840954You can turn off client-side execution by setting SupportEnhancedSQL to false in which case any search criteria that refers to other columns will cause an error.
Name | Type | Description |
IssueId | String | |
Id [KEY] | Int | |
Name | String | |
DisplayOrder | String |
Returns data from issue comment change log table.
The Cloud 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 Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueCommentChangeLog WHERE IssueId=6840954You can turn off client-side execution by setting SupportEnhancedSQL to false in which case any search criteria that refers to other columns will cause an error.
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 Cloud 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 Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueCommentNotifications WHERE IssueId=6840954You can turn off client-side execution by setting SupportEnhancedSQL to false in which case any search criteria that refers to other columns will cause an error.
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 Cloud 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 Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueCommentStars WHERE IssueId=6840954You can turn off client-side execution by setting SupportEnhancedSQL to false in which case any search criteria that refers to other columns will cause an error.
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 Cloud 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 Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueMilestones WHERE IssueId=6868745You can turn off client-side execution by setting SupportEnhancedSQL to false in which case any search criteria that refers to other columns will cause an error.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueVersions WHERE IssueId=6868745You can turn off client-side execution by setting SupportEnhancedSQL to false in which case any search criteria that refers to other columns will cause an error.
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 Cloud 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 Cloud.
For example, the following query is processed server side:
SELECT * FROM ProjectRecentUpdates WHERE ProjectId=114706You can turn off client-side execution by setting SupportEnhancedSQL to false in which case any search criteria that refers to other columns will cause an error.
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 Cloud 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 Cloud.
For example, the following query is processed server side:
SELECT * FROM ProjectTeamMembers WHERE ProjectId=114706You can turn off client-side execution by setting SupportEnhancedSQL to false in which case any search criteria that refers to other columns will cause an error.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
For example, the following query is processed server side:
SELECT * FROM SpaceUpdates WHERE Type=13 SELECT * FROM SpaceUpdates WHERE Type IN (13,5)You can turn off client-side execution by setting SupportEnhancedSQL to false in which case any search criteria that refers to other columns will cause an error.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
For example, the following query is processed server side:
SELECT * FROM UserReceivedStars WHERE UserId=263366You can turn off client-side execution by setting SupportEnhancedSQL to false in which case any search criteria that refers to other columns will cause an error.
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 Cloud 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 Cloud.
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)You can turn off client-side execution by setting SupportEnhancedSQL to false in which case any search criteria that refers to other columns will cause an error.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 Cloud 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 Cloud.
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 |
Stored procedures are function-like interfaces that extend the functionality of the Cloud beyond simple SELECT/INSERT/UPDATE/DELETE operations with Backlog.
Stored procedures accept a list of parameters, perform their intended function, and then return, if applicable, any relevant response data from Backlog, along with an indication of whether the procedure succeeded or failed.
Name | Description |
AddStar | Adds star. |
AttachFileToWiki | Attaches file to Wiki. |
LinkSharedFilesToWiki | Links Shared Files to Wiki. |
MarkWatchingAsRead | Mark a watching as read. |
PostAttachmentFile | Posts an attachment file for issue or wiki. |
RemoveSharedFileFromWiki | Removes link to shared file from Wiki. |
UpdatePullRequestCommentInformation | Updates pull request comment information.Authenticated user can update his own comments. |
UpdateSpaceNotification | Updates space notification. |
Adds star.
Name | Type | Required | Description |
IssueId | String | False | Id of the issue. |
CommentId | String | False | Id of the comment. |
WikiId | String | False | Id of the wiki. |
PullRequestId | String | False | Id of the pullRequest. |
PullRequestCommentId | String | False | Id of the pullRequestComment. |
Name | Type | Description |
Success | String | Returns True if procedure succeeded. |
Attaches file to Wiki.
Name | Type | Required | Description |
WikiId | String | True | Id of the issue. |
AttachmentId | String | True | Id of the attachment. You can specify multiple ids separating them by comma ','. |
Name | Type | Description |
Success | String | Returns True if the attachment succeeded. |
Download a specified document.
Name | Type | Required | Description |
ProjectId | String | True | Id of the project. |
FileId | String | True | Id of the file. |
DownloadLocation | String | True | Location of the downloaded file. EX: C:\Temp\downloads\ |
Name | Type | Description |
Success | String | Returns True if the download succeeded. |
Downloads issue's attachment file.
Name | Type | Required | Description |
IssueId | String | True | Id of the issue. |
AttachmentId | String | True | Id of the file. |
DownloadLocation | String | True | Location of the downloaded file. EX: C:\Temp\downloads\ |
Name | Type | Description |
Success | String | Returns True if the download succeeded. |
Download project icon.
Name | Type | Required | Description |
ProjectId | String | True | Id of the project. |
DownloadLocation | String | True | Location of the downloaded file. EX: C:\Temp\downloads\ |
Name | Type | Description |
Success | String | Returns True if the download succeeded. |
Downloads attached files on pull requests.
Name | Type | Required | Description |
ProjectId | String | True | Id of the project. |
RepositoryId | String | True | Id of the repository. |
Number | String | True | Number of the pull request. |
AttachmentId | String | True | Id of the attachment. |
DownloadLocation | String | True | Location of the downloaded file. EX: C:\Temp\downloads\ |
Name | Type | Description |
Success | String | Returns True if the download succeeded. |
Download a specified document.
Name | Type | Required | Description |
DownloadLocation | String | True | Location of the downloaded file. EX: C:\Temp\downloads\ |
Name | Type | Description |
Success | String | Returns True if the download succeeded. |
Downloads Wiki page's attachment file.
Name | Type | Required | Description |
WikiId | String | True | Id of the issue. |
AttachmentId | String | True | Id of the file. |
DownloadLocation | String | True | Location of the downloaded file. EX: C:\Temp\downloads\ |
Name | Type | Description |
Success | String | Returns True if the download succeeded. |
Gets an authentication token from Backlog.
Name | Type | Required | Description |
AuthMode | String | False | The type of authentication mode to use. Select App for getting authentication tokens via a desktop app. Select Web for getting authentication tokens via a Web app.
The allowed values are APP, WEB. The default value is APP. |
Scope | String | False | A comma-separated list of permissions to request from the user. Please check the Backlog API for a list of available permissions. |
CallbackUrl | String | False | The URL the user will be redirected to after authorizing your application. This value must match the Redirect URL you have specified in the Backlog app settings. Only needed when the Authmode parameter is Web. |
Verifier | String | False | The verifier returned from Backlog after the user has authorized your app to have access to their data. This value will be returned as a parameter to the callback URL. |
State | String | False | Indicates any state which may be useful to your application upon receipt of the response. Your application receives the same value it sent, as this parameter makes a round-trip to the Backlog authorization server and back. Uses include redirecting the user to the correct resource in your site, nonces, and cross-site-request-forgery mitigations. |
Name | Type | Description |
OAuthAccessToken | String | The access token used for communication with Backlog. |
OAuthRefreshToken | String | The OAuth refresh token. This is the same as the access token in the case of Backlog. |
ExpiresIn | String | The remaining lifetime on the access token. A -1 denotes that it will not expire. |
Gets the authorization URL that must be opened separately by the user to grant access to your application. Only needed when developing Web apps. You will request the OAuthAccessToken from this URL.
Name | Type | Required | Description |
CallbackUrl | String | False | The URL the user will be redirected to after authorizing your application. This value must match the Redirect URL in the Backlog app settings. |
State | String | False | Indicates any state which may be useful to your application upon receipt of the response. Your application receives the same value it sent, as this parameter makes a round-trip to the Backlog authorization server and back. Uses include redirecting the user to the correct resource in your site, nonces, and cross-site-request-forgery mitigations. |
Name | Type | Description |
URL | String | The authorization URL, entered into a Web browser to obtain the verifier token and authorize your app. |
Mark a watching as read.
Name | Type | Required | Description |
WatchingId | String | True | Id of the watching. |
Name | Type | Description |
Success | String | Returns True if procedure succeeded. |
Posts an attachment file for issue or wiki.
Name | Type | Required | Description |
FileLocation | String | True | Location of the downloaded file. EX: C:\Temp\downloads\file.txt |
Name | Type | Description |
Success | String | Returns True if the upload succeeded. |
Refreshes the OAuth access token used for authentication with Backlog.
Name | Type | Required | Description |
OAuthRefreshToken | String | True | Set this to the token value that expired. |
Name | Type | Description |
OAuthAccessToken | String | The authentication token returned from Backlog. This can be used in subsequent calls to other operations for this particular service. |
OAuthRefreshToken | String | This is the same as the access token. |
ExpiresIn | String | The remaining lifetime on the access token. |
Updates pull request comment information.Authenticated user can update his own comments.
Name | Type | Required | Description |
ProjectId | String | True | Id of the project. |
RepositoryId | String | True | Id of the repository. |
Number | String | True | Number of the pull request. |
CommentId | String | True | Id of the comment. |
Content | String | True | Content of the comment. |
Name | Type | Description |
Success | String | Returns True if procedure succeeded. |
Updates space notification.
Name | Type | Required | Description |
Content | String | True | Content of the update. |
Name | Type | Description |
Success | String | Returns True if the update succeeded. |
You can query the system tables described in this section to access schema information, information on data source functionality, and batch operation statistics.
The following tables return database metadata for Backlog:
The following tables return information about how to connect to and query the data source:
The following table returns query statistics for data modification queries:
Lists the available databases.
The following query retrieves all databases determined by the connection string:
SELECT * FROM sys_catalogs
Name | Type | Description |
CatalogName | String | The database name. |
Lists the available schemas.
The following query retrieves all available schemas:
SELECT * FROM sys_schemas
Name | Type | Description |
CatalogName | String | The database name. |
SchemaName | String | The schema name. |
Lists the available tables.
The following query retrieves the available tables and views:
SELECT * FROM sys_tables
Name | Type | Description |
CatalogName | String | The database containing the table or view. |
SchemaName | String | The schema containing the table or view. |
TableName | String | The name of the table or view. |
TableType | String | The table type (table or view). |
Description | String | A description of the table or view. |
IsUpdateable | Boolean | Whether the table can be updated. |
Describes the columns of the available tables and views.
The following query returns the columns and data types for the Issues table:
SELECT ColumnName, DataTypeName FROM sys_tablecolumns WHERE TableName='Issues'
Name | Type | Description |
CatalogName | String | The name of the database containing the table or view. |
SchemaName | String | The schema containing the table or view. |
TableName | String | The name of the table or view containing the column. |
ColumnName | String | The column name. |
DataTypeName | String | The data type name. |
DataType | Int32 | An integer indicating the data type. This value is determined at run time based on the environment. |
Length | Int32 | The storage size of the column. |
DisplaySize | Int32 | The designated column's normal maximum width in characters. |
NumericPrecision | Int32 | The maximum number of digits in numeric data. The column length in characters for character and date-time data. |
NumericScale | Int32 | The column scale or number of digits to the right of the decimal point. |
IsNullable | Boolean | Whether the column can contain null. |
Description | String | A brief description of the column. |
Ordinal | Int32 | The sequence number of the column. |
IsAutoIncrement | String | Whether the column value is assigned in fixed increments. |
IsGeneratedColumn | String | Whether the column is generated. |
IsHidden | Boolean | Whether the column is hidden. |
IsArray | Boolean | Whether the column is an array. |
Lists the available stored procedures.
The following query retrieves the available stored procedures:
SELECT * FROM sys_procedures
Name | Type | Description |
CatalogName | String | The database containing the stored procedure. |
SchemaName | String | The schema containing the stored procedure. |
ProcedureName | String | The name of the stored procedure. |
Description | String | A description of the stored procedure. |
ProcedureType | String | The type of the procedure, such as PROCEDURE or FUNCTION. |
Describes stored procedure parameters.
The following query returns information about all of the input parameters for the AddStar stored procedure:
SELECT * FROM sys_procedureparameters WHERE ProcedureName='AddStar' AND Direction=1 OR Direction=2
Name | Type | Description |
CatalogName | String | The name of the database containing the stored procedure. |
SchemaName | String | The name of the schema containing the stored procedure. |
ProcedureName | String | The name of the stored procedure containing the parameter. |
ColumnName | String | The name of the stored procedure parameter. |
Direction | Int32 | An integer corresponding to the type of the parameter: input (1), input/output (2), or output(4). input/output type parameters can be both input and output parameters. |
DataTypeName | String | The name of the data type. |
DataType | Int32 | An integer indicating the data type. This value is determined at run time based on the environment. |
Length | Int32 | The number of characters allowed for character data. The number of digits allowed for numeric data. |
NumericPrecision | Int32 | The maximum precision for numeric data. The column length in characters for character and date-time data. |
NumericScale | Int32 | The number of digits to the right of the decimal point in numeric data. |
IsNullable | Boolean | Whether the parameter can contain null. |
IsRequired | Boolean | Whether the parameter is required for execution of the procedure. |
IsArray | Boolean | Whether the parameter is an array. |
Description | String | The description of the parameter. |
Ordinal | Int32 | The index of the parameter. |
Describes the primary and foreign keys.
The following query retrieves the primary key for the Issues table:
SELECT * FROM sys_keycolumns WHERE IsKey='True' AND TableName='Issues'
Name | Type | Description |
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
IsKey | Boolean | Whether the column is a primary key in the table referenced in the TableName field. |
IsForeignKey | Boolean | Whether the column is a foreign key referenced in the TableName field. |
PrimaryKeyName | String | The name of the primary key. |
ForeignKeyName | String | The name of the foreign key. |
ReferencedCatalogName | String | The database containing the primary key. |
ReferencedSchemaName | String | The schema containing the primary key. |
ReferencedTableName | String | The table containing the primary key. |
ReferencedColumnName | String | The column name of the primary key. |
Describes the foreign keys.
The following query retrieves all foreign keys which refer to other tables:
SELECT * FROM sys_foreignkeys WHERE ForeignKeyType = 'FOREIGNKEY_TYPE_IMPORT'
Name | Type | Description |
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
PrimaryKeyName | String | The name of the primary key. |
ForeignKeyName | String | The name of the foreign key. |
ReferencedCatalogName | String | The database containing the primary key. |
ReferencedSchemaName | String | The schema containing the primary key. |
ReferencedTableName | String | The table containing the primary key. |
ReferencedColumnName | String | The column name of the primary key. |
ForeignKeyType | String | Designates whether the foreign key is an import (points to other tables) or export (referenced from other tables) key. |
Describes the primary keys.
The following query retrieves the primary keys from all tables and views:
SELECT * FROM sys_primarykeys
Name | Type | Description |
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
KeySeq | String | The sequence number of the primary key. |
KeyName | String | The name of the primary key. |
Describes the available indexes. By filtering on indexes, you can write more selective queries with faster query response times.
The following query retrieves all indexes that are not primary keys:
SELECT * FROM sys_indexes WHERE IsPrimary='false'
Name | Type | Description |
CatalogName | String | The name of the database containing the index. |
SchemaName | String | The name of the schema containing the index. |
TableName | String | The name of the table containing the index. |
IndexName | String | The index name. |
ColumnName | String | The name of the column associated with the index. |
IsUnique | Boolean | True if the index is unique. False otherwise. |
IsPrimary | Boolean | True if the index is a primary key. False otherwise. |
Type | Int16 | An integer value corresponding to the index type: statistic (0), clustered (1), hashed (2), or other (3). |
SortOrder | String | The sort order: A for ascending or D for descending. |
OrdinalPosition | Int16 | The sequence number of the column in the index. |
Returns information on the available connection properties and those set in the connection string.
When querying this table, the config connection string should be used:
jdbc:cdata:backlog:config:
This connection string enables you to query this table without a valid connection.
The following query retrieves all connection properties that have been set in the connection string or set through a default value:
SELECT * FROM sys_connection_props WHERE Value <> ''
Name | Type | Description |
Name | String | The name of the connection property. |
ShortDescription | String | A brief description. |
Type | String | The data type of the connection property. |
Default | String | The default value if one is not explicitly set. |
Values | String | A comma-separated list of possible values. A validation error is thrown if another value is specified. |
Value | String | The value you set or a preconfigured default. |
Required | Boolean | Whether the property is required to connect. |
Category | String | The category of the connection property. |
IsSessionProperty | String | Whether the property is a session property, used to save information about the current connection. |
Sensitivity | String | The sensitivity level of the property. This informs whether the property is obfuscated in logging and authentication forms. |
PropertyName | String | A camel-cased truncated form of the connection property name. |
Ordinal | Int32 | The index of the parameter. |
CatOrdinal | Int32 | The index of the parameter category. |
Hierarchy | String | Shows dependent properties associated that need to be set alongside this one. |
Visible | Boolean | Informs whether the property is visible in the connection UI. |
ETC | String | Various miscellaneous information about the property. |
Describes the SELECT query processing that the Cloud can offload to the data source.
See SQL Compliance for SQL syntax details.
Below is an example data set of SQL capabilities. The following result set indicates the SELECT functionality that the Cloud can offload to the data source or process client side. Your data source may support additional SQL syntax. Some aspects of SELECT functionality are returned in a comma-separated list if supported; otherwise, the column contains NO.
Name | Description | Possible Values |
AGGREGATE_FUNCTIONS | Supported aggregation functions. | AVG, COUNT, MAX, MIN, SUM, DISTINCT |
COUNT | Whether COUNT function is supported. | YES, NO |
IDENTIFIER_QUOTE_OPEN_CHAR | The opening character used to escape an identifier. | [ |
IDENTIFIER_QUOTE_CLOSE_CHAR | The closing character used to escape an identifier. | ] |
SUPPORTED_OPERATORS | A list of supported SQL operators. | =, >, <, >=, <=, <>, !=, LIKE, NOT LIKE, IN, NOT IN, IS NULL, IS NOT NULL, AND, OR |
GROUP_BY | Whether GROUP BY is supported, and, if so, the degree of support. | NO, NO_RELATION, EQUALS_SELECT, SQL_GB_COLLATE |
OJ_CAPABILITIES | The supported varieties of outer joins supported. | NO, LEFT, RIGHT, FULL, INNER, NOT_ORDERED, ALL_COMPARISON_OPS |
OUTER_JOINS | Whether outer joins are supported. | YES, NO |
SUBQUERIES | Whether subqueries are supported, and, if so, the degree of support. | NO, COMPARISON, EXISTS, IN, CORRELATED_SUBQUERIES, QUANTIFIED |
STRING_FUNCTIONS | Supported string functions. | LENGTH, CHAR, LOCATE, REPLACE, SUBSTRING, RTRIM, LTRIM, RIGHT, LEFT, UCASE, SPACE, SOUNDEX, LCASE, CONCAT, ASCII, REPEAT, OCTET, BIT, POSITION, INSERT, TRIM, UPPER, REGEXP, LOWER, DIFFERENCE, CHARACTER, SUBSTR, STR, REVERSE, PLAN, UUIDTOSTR, TRANSLATE, TRAILING, TO, STUFF, STRTOUUID, STRING, SPLIT, SORTKEY, SIMILAR, REPLICATE, PATINDEX, LPAD, LEN, LEADING, KEY, INSTR, INSERTSTR, HTML, GRAPHICAL, CONVERT, COLLATION, CHARINDEX, BYTE |
NUMERIC_FUNCTIONS | Supported numeric functions. | ABS, ACOS, ASIN, ATAN, ATAN2, CEILING, COS, COT, EXP, FLOOR, LOG, MOD, SIGN, SIN, SQRT, TAN, PI, RAND, DEGREES, LOG10, POWER, RADIANS, ROUND, TRUNCATE |
TIMEDATE_FUNCTIONS | Supported date/time functions. | NOW, CURDATE, DAYOFMONTH, DAYOFWEEK, DAYOFYEAR, MONTH, QUARTER, WEEK, YEAR, CURTIME, HOUR, MINUTE, SECOND, TIMESTAMPADD, TIMESTAMPDIFF, DAYNAME, MONTHNAME, CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, EXTRACT |
REPLICATION_SKIP_TABLES | Indicates tables skipped during replication. | |
REPLICATION_TIMECHECK_COLUMNS | A string array containing a list of columns which will be used to check for (in the given order) to use as a modified column during replication. | |
IDENTIFIER_PATTERN | String value indicating what string is valid for an identifier. | |
SUPPORT_TRANSACTION | Indicates if the provider supports transactions such as commit and rollback. | YES, NO |
DIALECT | Indicates the SQL dialect to use. | |
KEY_PROPERTIES | Indicates the properties which identify the uniform database. | |
SUPPORTS_MULTIPLE_SCHEMAS | Indicates if multiple schemas may exist for the provider. | YES, NO |
SUPPORTS_MULTIPLE_CATALOGS | Indicates if multiple catalogs may exist for the provider. | YES, NO |
DATASYNCVERSION | The CData Data Sync version needed to access this driver. | Standard, Starter, Professional, Enterprise |
DATASYNCCATEGORY | The CData Data Sync category of this driver. | Source, Destination, Cloud Destination |
SUPPORTSENHANCEDSQL | Whether enhanced SQL functionality beyond what is offered by the API is supported. | TRUE, FALSE |
SUPPORTS_BATCH_OPERATIONS | Whether batch operations are supported. | YES, NO |
SQL_CAP | All supported SQL capabilities for this driver. | SELECT, INSERT, DELETE, UPDATE, TRANSACTIONS, ORDERBY, OAUTH, ASSIGNEDID, LIMIT, LIKE, BULKINSERT, COUNT, BULKDELETE, BULKUPDATE, GROUPBY, HAVING, AGGS, OFFSET, REPLICATE, COUNTDISTINCT, JOINS, DROP, CREATE, DISTINCT, INNERJOINS, SUBQUERIES, ALTER, MULTIPLESCHEMAS, GROUPBYNORELATION, OUTERJOINS, UNIONALL, UNION, UPSERT, GETDELETED, CROSSJOINS, GROUPBYCOLLATE, MULTIPLECATS, FULLOUTERJOIN, MERGE, JSONEXTRACT, BULKUPSERT, SUM, SUBQUERIESFULL, MIN, MAX, JOINSFULL, XMLEXTRACT, AVG, MULTISTATEMENTS, FOREIGNKEYS, CASE, LEFTJOINS, COMMAJOINS, WITH, LITERALS, RENAME, NESTEDTABLES, EXECUTE, BATCH, BASIC, INDEX |
PREFERRED_CACHE_OPTIONS | A string value specifies the preferred cacheOptions. | |
ENABLE_EF_ADVANCED_QUERY | Indicates if the driver directly supports advanced queries coming from Entity Framework. If not, queries will be handled client side. | YES, NO |
PSEUDO_COLUMNS | A string array indicating the available pseudo columns. | |
MERGE_ALWAYS | If the value is true, The Merge Mode is forcibly executed in Data Sync. | TRUE, FALSE |
REPLICATION_MIN_DATE_QUERY | A select query to return the replicate start datetime. | |
REPLICATION_MIN_FUNCTION | Allows a provider to specify the formula name to use for executing a server side min. | |
REPLICATION_START_DATE | Allows a provider to specify a replicate startdate. | |
REPLICATION_MAX_DATE_QUERY | A select query to return the replicate end datetime. | |
REPLICATION_MAX_FUNCTION | Allows a provider to specify the formula name to use for executing a server side max. | |
IGNORE_INTERVALS_ON_INITIAL_REPLICATE | A list of tables which will skip dividing the replicate into chunks on the initial replicate. | |
CHECKCACHE_USE_PARENTID | Indicates whether the CheckCache statement should be done against the parent key column. | TRUE, FALSE |
CREATE_SCHEMA_PROCEDURES | Indicates stored procedures that can be used for generating schema files. |
The following query retrieves the operators that can be used in the WHERE clause:
SELECT * FROM sys_sqlinfo WHERE Name='SUPPORTED_OPERATORS'
Note that individual tables may have different limitations or requirements on the WHERE clause; refer to the Data Model section for more information.
Name | Type | Description |
NAME | String | A component of SQL syntax, or a capability that can be processed on the server. |
VALUE | String | Detail on the supported SQL or SQL syntax. |
Returns information about attempted modifications.
The following query retrieves the Ids of the modified rows in a batch operation:
SELECT * FROM sys_identity
Name | Type | Description |
Id | String | The database-generated Id returned from a data modification operation. |
Batch | String | An identifier for the batch. 1 for a single operation. |
Operation | String | The result of the operation in the batch: INSERTED, UPDATED, or DELETED. |
Message | String | SUCCESS or an error message if the update in the batch failed. |
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.
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 | The client Id assigned when you register your application with an OAuth authorization server. |
OAuthClientSecret | The client secret assigned when you register your application with an OAuth authorization server. |
OAuthAccessToken | The access token for connecting using OAuth. |
CallbackURL | The OAuth callback URL to return to when authenticating. This value must match the callback URL you specify in your app settings. |
OAuthVerifier | The verifier code returned from the OAuth authorization URL. |
OAuthRefreshToken | The OAuth refresh token for the corresponding OAuth access token. |
OAuthExpiresIn | The lifetime in seconds of the OAuth AccessToken. |
OAuthTokenTimestamp | The Unix epoch timestamp in milliseconds when the current Access Token was created. |
Property | Description |
SSLServerCert | The certificate to be accepted from the server when connecting using TLS/SSL. |
Property | Description |
FirewallType | The protocol used by a proxy-based firewall. |
FirewallServer | The name or IP address of a proxy-based firewall. |
FirewallPort | The TCP port for a proxy-based firewall. |
FirewallUser | The user name to use to authenticate with a proxy-based firewall. |
FirewallPassword | A password used to authenticate to a proxy-based firewall. |
Property | Description |
ProxyAutoDetect | This indicates whether to use the system proxy settings or not. This takes precedence over other proxy settings, so you'll need to set ProxyAutoDetect to FALSE in order use custom proxy settings. |
ProxyServer | The hostname or IP address of a proxy to route HTTP traffic through. |
ProxyPort | The TCP port the ProxyServer proxy is running on. |
ProxyAuthScheme | The authentication type to use to authenticate to the ProxyServer proxy. |
ProxyUser | A user name to be used to authenticate to the ProxyServer proxy. |
ProxyPassword | A password to be used to authenticate to the ProxyServer proxy. |
ProxySSLType | The SSL type to use when connecting to the ProxyServer proxy. |
ProxyExceptions | A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the ProxyServer . |
Property | Description |
Logfile | A filepath which designates the name and location of the log file. |
Verbosity | The verbosity level that determines the amount of detail included in the log file. |
LogModules | Core modules to be included in the log file. |
MaxLogFileSize | A string specifying the maximum size in bytes for a log file (for example, 10 MB). |
MaxLogFileCount | A string specifying the maximum file count of log files. |
Property | Description |
Location | A path to the directory that contains the schema files defining tables, views, and stored procedures. |
BrowsableSchemas | This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC. |
Tables | This property restricts the tables reported to a subset of the available tables. For example, Tables=TableA,TableB,TableC. |
Views | Restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC. |
Property | Description |
AutoCache | Automatically caches the results of SELECT queries into a cache database specified by either CacheLocation or both of CacheConnection and CacheProvider . |
CacheLocation | Specifies the path to the cache when caching to a file. |
CacheTolerance | The tolerance for stale data in the cache specified in seconds when using AutoCache . |
Offline | Use offline mode to get the data from the cache instead of the live source. |
CacheMetadata | This property determines whether or not to cache the table metadata to a file store. |
Property | Description |
IncludeCustomFields | Set this to true if you want to retrieve custom fields from the Issues table. |
MaxRows | Limits the number of rows returned rows when no aggregation or group by is used in the query. This helps avoid performance issues at design time. |
MaxThreads | The Max Thread. |
Other | These hidden properties are used only in specific use cases. |
Pagesize | The maximum number of results to return per page from Backlog. |
ProjectId | Id of the specific project. |
PseudoColumns | This property indicates whether or not to include pseudo columns as columns to the table. |
Readonly | You can use this property to enforce read-only access to Backlog from the provider. |
RTK | The runtime key used for licensing. |
Timeout | The value in seconds until the timeout error is thrown, canceling the operation. |
UserDefinedViews | A filepath pointing to the JSON configuration file containing your custom views. |
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.
string
""
The URL of the Backlog account in the form "https://{sample}.backlog.com".
The type of authentication to use when connecting to Backlog.
string
"APIToken"
The API key allows you make requests to the Backlog API.
string
""
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 | The client Id assigned when you register your application with an OAuth authorization server. |
OAuthClientSecret | The client secret assigned when you register your application with an OAuth authorization server. |
OAuthAccessToken | The access token for connecting using OAuth. |
CallbackURL | The OAuth callback URL to return to when authenticating. This value must match the callback URL you specify in your app settings. |
OAuthVerifier | The verifier code returned from the OAuth authorization URL. |
OAuthRefreshToken | The OAuth refresh token for the corresponding OAuth access token. |
OAuthExpiresIn | The lifetime in seconds of the OAuth AccessToken. |
OAuthTokenTimestamp | The Unix epoch timestamp in milliseconds when the current Access Token was created. |
The client Id assigned when you register your application with an OAuth authorization server.
string
""
As part of registering an OAuth application, you will receive the OAuthClientId value, sometimes also called a consumer key, and a client secret, the OAuthClientSecret.
The client secret assigned when you register your application with an OAuth authorization server.
string
""
As part of registering an OAuth application, you will receive the OAuthClientId, also called a consumer key. You will also receive a client secret, also called a consumer secret. Set the client secret in the OAuthClientSecret property.
The access token for connecting using OAuth.
string
""
The OAuthAccessToken property is used to connect using OAuth. The OAuthAccessToken is retrieved from the OAuth server as part of the authentication process. It has a server-dependent timeout and can be reused between requests.
The access token is used in place of your user name and password. The access token protects your credentials by keeping them on the server.
The OAuth callback URL to return to when authenticating. This value must match the callback URL you specify in your app settings.
string
""
During the authentication process, the OAuth authorization server redirects the user to this URL. This value must match the callback URL you specify in your app settings.
The verifier code returned from the OAuth authorization URL.
string
""
The verifier code returned from the OAuth authorization URL. This can be used on systems where a browser cannot be launched such as headless systems.
See to obtain the OAuthVerifier value.
Set OAuthSettingsLocation along with OAuthVerifier. When you connect, the Cloud exchanges the OAuthVerifier for the OAuth authentication tokens and saves them, encrypted, to the specified file.
Once the OAuth settings file has been generated, you can remove OAuthVerifier from the connection properties and connect with OAuthSettingsLocation set.
To automatically refresh the OAuth token values, set OAuthSettingsLocation and additionally set InitiateOAuth to REFRESH.
The OAuth refresh token for the corresponding OAuth access token.
string
""
The OAuthRefreshToken property is used to refresh the OAuthAccessToken when using OAuth authentication.
The lifetime in seconds of the OAuth AccessToken.
string
""
Pair with OAuthTokenTimestamp to determine when the AccessToken will expire.
The Unix epoch timestamp in milliseconds when the current Access Token was created.
string
""
Pair with OAuthExpiresIn to determine when the AccessToken will expire.
This section provides a complete list of the SSL properties you can configure in the connection string for this provider.
Property | Description |
SSLServerCert | The certificate to be accepted from the server when connecting using TLS/SSL. |
The certificate to be accepted from the server when connecting using TLS/SSL.
string
""
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 | The protocol used by a proxy-based firewall. |
FirewallServer | The name or IP address of a proxy-based firewall. |
FirewallPort | The TCP port for a proxy-based firewall. |
FirewallUser | The user name to use to authenticate with a proxy-based firewall. |
FirewallPassword | A password used to authenticate to a proxy-based firewall. |
The protocol used by a proxy-based firewall.
string
"NONE"
This property specifies the protocol that the Cloud will use to tunnel traffic through the FirewallServer proxy. Note that by default, the Cloud connects to the system proxy; to disable this behavior and connect to one of the following proxy types, set ProxyAutoDetect to false.
Type | Default Port | Description |
TUNNEL | 80 | When this is set, the Cloud opens a connection to Backlog and traffic flows back and forth through the proxy. |
SOCKS4 | 1080 | When this is set, the Cloud sends data through the SOCKS 4 proxy specified by FirewallServer and FirewallPort and passes the FirewallUser value to the proxy, which determines if the connection request should be granted. |
SOCKS5 | 1080 | When this is set, the Cloud sends data through the SOCKS 5 proxy specified by FirewallServer and FirewallPort. If your 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.
The name or IP address of a proxy-based firewall.
string
""
This property specifies the IP address, DNS name, or host name of a proxy allowing traversal of a firewall. The protocol is specified by FirewallType: Use FirewallServer with this property to connect through SOCKS or do tunneling. Use ProxyServer to connect to an HTTP proxy.
Note that the Cloud uses the system proxy by default. To use a different proxy, set ProxyAutoDetect to false.
The TCP port for a proxy-based firewall.
int
0
This specifies the TCP port for a proxy allowing traversal of a firewall. Use FirewallServer to specify the name or IP address. Specify the protocol with FirewallType.
The user name to use to authenticate with a proxy-based firewall.
string
""
The FirewallUser and FirewallPassword properties are used to authenticate against the proxy specified in FirewallServer and FirewallPort, following the authentication method specified in FirewallType.
A password used to authenticate to a proxy-based firewall.
string
""
This property is passed to the proxy specified by FirewallServer and FirewallPort, following the authentication method specified by FirewallType.
This section provides a complete list of the Proxy properties you can configure in the connection string for this provider.
Property | Description |
ProxyAutoDetect | This indicates whether to use the system proxy settings or not. This takes precedence over other proxy settings, so you'll need to set ProxyAutoDetect to FALSE in order use custom proxy settings. |
ProxyServer | The hostname or IP address of a proxy to route HTTP traffic through. |
ProxyPort | The TCP port the ProxyServer proxy is running on. |
ProxyAuthScheme | The authentication type to use to authenticate to the ProxyServer proxy. |
ProxyUser | A user name to be used to authenticate to the ProxyServer proxy. |
ProxyPassword | A password to be used to authenticate to the ProxyServer proxy. |
ProxySSLType | The SSL type to use when connecting to the ProxyServer proxy. |
ProxyExceptions | A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the ProxyServer . |
This indicates whether to use the system proxy settings or not. This takes precedence over other proxy settings, so you'll need to set ProxyAutoDetect to FALSE in order use custom proxy settings.
bool
true
This takes precedence over other proxy settings, so you'll need to set ProxyAutoDetect to FALSE in order use custom proxy settings.
To connect to an HTTP proxy, see ProxyServer. For other proxies, such as SOCKS or tunneling, see FirewallType.
The hostname or IP address of a proxy to route HTTP traffic through.
string
""
The hostname or IP address of a proxy to route HTTP traffic through. The Cloud can use the HTTP, Windows (NTLM), or Kerberos authentication types to authenticate to an HTTP proxy.
If you need to connect through a SOCKS proxy or tunnel the connection, see FirewallType.
By default, the Cloud uses the system proxy. If you need to use another proxy, set ProxyAutoDetect to false.
The TCP port the ProxyServer proxy is running on.
int
80
The port the HTTP proxy is running on that you want to redirect HTTP traffic through. Specify the HTTP proxy in ProxyServer. For other proxy types, see FirewallType.
The authentication type to use to authenticate to the ProxyServer proxy.
string
"BASIC"
This value specifies the authentication type to use to authenticate to the HTTP proxy specified by ProxyServer and ProxyPort.
Note that the Cloud will use the system proxy settings by default, without further configuration needed; if you want to connect to another proxy, you will need to set ProxyAutoDetect to false, in addition to ProxyServer and ProxyPort. To authenticate, set ProxyAuthScheme and set ProxyUser and ProxyPassword, if needed.
The authentication type can be one of the following:
If you need to use another authentication type, such as SOCKS 5 authentication, see FirewallType.
A user name to be used to authenticate to the ProxyServer proxy.
string
""
The ProxyUser and ProxyPassword options are used to connect and authenticate against the HTTP proxy specified in ProxyServer.
You can select one of the available authentication types in ProxyAuthScheme. If you are using HTTP authentication, set this to the user name of a user recognized by the HTTP proxy. If you are using Windows or Kerberos authentication, set this property to a user name in one of the following formats:
user@domain domain\user
A password to be used to authenticate to the ProxyServer proxy.
string
""
This property is used to authenticate to an HTTP proxy server that supports NTLM (Windows), Kerberos, or HTTP authentication. To specify the HTTP proxy, you can set ProxyServer and ProxyPort. To specify the authentication type, set ProxyAuthScheme.
If you are using HTTP authentication, additionally set ProxyUser and ProxyPassword to HTTP proxy.
If you are using NTLM authentication, set ProxyUser and ProxyPassword to your Windows password. You may also need these to complete Kerberos authentication.
For SOCKS 5 authentication or tunneling, see FirewallType.
By default, the Cloud uses the system proxy. If you want to connect to another proxy, set ProxyAutoDetect to false.
The SSL type to use when connecting to the ProxyServer proxy.
string
"AUTO"
This property determines when to use SSL for the connection to an HTTP proxy specified by ProxyServer. This value can be AUTO, ALWAYS, NEVER, or TUNNEL. The applicable values are the following:
AUTO | Default setting. If the URL is an HTTPS URL, the Cloud will use the TUNNEL option. If the URL is an HTTP URL, the component will use the NEVER option. |
ALWAYS | The connection is always SSL enabled. |
NEVER | The connection is not SSL enabled. |
TUNNEL | The connection is 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 ProxyServer .
string
""
The ProxyServer is used for all addresses, except for addresses defined in this property. Use semicolons to separate entries.
Note that the Cloud uses the system proxy settings by default, without further configuration needed; if you want to explicitly configure proxy exceptions for this connection, you need to set ProxyAutoDetect = false, and configure ProxyServer and ProxyPort. To authenticate, set ProxyAuthScheme and set ProxyUser and ProxyPassword, if needed.
This section provides a complete list of the Logging properties you can configure in the connection string for this provider.
Property | Description |
Logfile | A filepath which designates the name and location of the log file. |
Verbosity | The verbosity level that determines the amount of detail included in the log file. |
LogModules | Core modules to be included in the log file. |
MaxLogFileSize | A string specifying the maximum size in bytes for a log file (for example, 10 MB). |
MaxLogFileCount | A string specifying the maximum file count of log files. |
A filepath which designates the name and location of the log file.
string
""
Once this property is set, the Cloud will populate the log file as it carries out various tasks, such as when authentication is performed or queries are executed. If the specified file doesn't already exist, it will be created.
Connection strings and version information are also logged, though connection properties containing sensitive information are masked automatically.
If a relative filepath is supplied, the location of the log file will be resolved based on the path found in the Location connection property.
For more control over what is written to the log file, you can adjust the Verbosity property.
Log contents are categorized into several modules. You can show/hide individual modules using the LogModules property.
To edit the maximum size of a single logfile before a new one is created, see MaxLogFileSize.
If you would like to place a cap on the number of logfiles generated, use MaxLogFileCount.
The verbosity level that determines the amount of detail included in the log file.
string
"1"
The verbosity level determines the amount of detail that the Cloud reports to the Logfile. Verbosity levels from 1 to 5 are supported. These are detailed in the Logging page.
Core modules to be included in the log file.
string
""
Only the modules specified (separated by ';') will be included in the log file. By default all modules are included.
See the Logging page for an overview.
A string specifying the maximum size in bytes for a log file (for example, 10 MB).
string
"100MB"
When the limit is hit, a new log is created in the same folder with the date and time appended to the end. The default limit is 100 MB. Values lower than 100 kB will use 100 kB as the value instead.
Adjust the maximum number of logfiles generated with MaxLogFileCount.
A string specifying the maximum file count of log files.
int
-1
When the limit is hit, a new log is created in the same folder with the date and time appended to the end and the oldest log file will be deleted.
The minimum supported value is 2. A value of 0 or a negative value indicates no limit on the count.
Adjust the maximum size of the logfiles generated with MaxLogFileSize.
This section provides a complete list of the Schema properties you can configure in the connection string for this provider.
Property | Description |
Location | A path to the directory that contains the schema files defining tables, views, and stored procedures. |
BrowsableSchemas | This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC. |
Tables | This property restricts the tables reported to a subset of the available tables. For example, Tables=TableA,TableB,TableC. |
Views | Restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC. |
A path to the directory that contains the schema files defining tables, views, and stored procedures.
string
"%APPDATA%\\CData\\Backlog Data Provider\\Schema"
The path to a directory which contains the schema files for the Cloud (.rsd files for tables and views, .rsb files for stored procedures). The folder location can be a relative path from the location of the executable. The Location property is only needed if you want to customize definitions (for example, change a column name, ignore a column, and so on) 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" with %APPDATA% being set to the user's configuration directory:
This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC.
string
""
Listing the schemas from databases can be expensive. Providing a list of schemas in the connection string improves the performance.
This property restricts the tables reported to a subset of the available tables. For example, Tables=TableA,TableB,TableC.
string
""
Listing the tables from some databases can be expensive. Providing a list of tables in the connection string improves the performance of the Cloud.
This property can also be used as an alternative to automatically listing views if you already know which ones you want to work with and there would otherwise be too many to work with.
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 that when connecting to a data source with multiple schemas or catalogs, you will need to provide the fully qualified name of the table in this property, as in the last example here, to avoid ambiguity between tables that exist in multiple catalogs or schemas.
Restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC.
string
""
Listing the views from some databases can be expensive. Providing a list of views in the connection string improves the performance of the Cloud.
This property can also be used as an alternative to automatically listing views if you already know which ones you want to work with and there would otherwise be too many to work with.
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 that when connecting to a data source with multiple schemas or catalogs, you will need to provide the fully qualified name of the table in this property, as in the last example here, to avoid ambiguity between tables that exist in multiple catalogs or schemas.
This section provides a complete list of the Caching properties you can configure in the connection string for this provider.
Property | Description |
AutoCache | Automatically caches the results of SELECT queries into a cache database specified by either CacheLocation or both of CacheConnection and CacheProvider . |
CacheLocation | Specifies the path to the cache when caching to a file. |
CacheTolerance | The tolerance for stale data in the cache specified in seconds when using AutoCache . |
Offline | Use offline mode to get the data from the cache instead of the live source. |
CacheMetadata | This property determines whether or not to cache the table metadata to a file store. |
Automatically caches the results of SELECT queries into a cache database specified by either CacheLocation or both of CacheConnection and CacheProvider .
bool
false
When AutoCache = true, the Cloud automatically maintains a cache of your table's data in the database of your choice.
When AutoCache = true, the Cloud caches to a simple, file-based cache. You can configure its location or cache to a different database with the following properties:
Specifies the path to the cache when caching to a file.
string
"%APPDATA%\\CData\\Backlog Data Provider"
The CacheLocation is a simple, file-based cache.
If left unspecified, the default location is "%APPDATA%\\CData\\Backlog Data Provider" with %APPDATA% being set to the user's configuration directory:
The tolerance for stale data in the cache specified in seconds when using AutoCache .
int
600
The tolerance for stale data in the cache specified in seconds. This only applies when AutoCache is used. The Cloud checks with the data source for newer records after the tolerance interval has expired. Otherwise, it returns the data directly from the cache.
Use offline mode to get the data from the cache instead of the live source.
bool
false
When Offline = true, all queries execute against the cache as opposed to the live data source. In this mode, certain queries like INSERT, UPDATE, DELETE, and CACHE are not allowed.
This property determines whether or not to cache the table metadata to a file store.
bool
false
As you execute queries with this property set, table metadata in the Backlog catalog are cached to the file store specified by CacheLocation if set or the user's home directory otherwise. A table's metadata will be retrieved only once, when the table is queried for the first time.
The Cloud automatically persists metadata in memory for up to two hours when you first discover the metadata for a table or view and therefore, CacheMetadata is generally not required. CacheMetadata becomes useful when metadata operations are expensive such as when you are working with large amounts of metadata or when you have many short-lived connections.
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 | Limits the number of rows returned rows when no aggregation or group by is used in the query. This helps avoid performance issues at design time. |
MaxThreads | The Max Thread. |
Other | These hidden properties are used only in specific use cases. |
Pagesize | The maximum number of results to return per page from Backlog. |
ProjectId | Id of the specific project. |
PseudoColumns | This property indicates whether or not to include pseudo columns as columns to the table. |
Readonly | You can use this property to enforce read-only access to Backlog from the provider. |
RTK | The runtime key used for licensing. |
Timeout | The value in seconds until the timeout error is thrown, canceling the operation. |
UserDefinedViews | A filepath pointing to the JSON configuration file containing your custom views. |
Set this to true if you want to retrieve custom fields from the Issues table.
bool
false
If set to true, the ProjectId connection property is also required.
Limits the number of rows returned rows when no aggregation or group by is used in the query. This helps avoid performance issues at design time.
int
-1
Limits the number of rows returned rows when no aggregation or group by is used in the query. This helps avoid performance issues at design time.
The Max Thread.
string
"1"
These hidden properties are used only in specific use cases.
string
""
The properties listed below are available for specific use cases. Normal driver use cases and functionality should not require these properties.
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. |
The maximum number of results to return per page from Backlog.
int
100
The Pagesize property affects the maximum number of results to return per page from Backlog. Setting a higher value may result in better performance at the cost of additional memory allocated per page consumed.
Id of the specific project.
string
""
Id of the specific project.
This property indicates whether or not to include pseudo columns as columns to the table.
string
""
This setting is particularly helpful in Entity Framework, which does not allow you to set a value for a pseudo column unless it is a table column. The value of this connection setting is of the format "Table1=Column1, Table1=Column2, Table2=Column3". You can use the "*" character to include all tables and all columns; for example, "*=*".
You can use this property to enforce read-only access to Backlog from the provider.
bool
false
If this property is set to true, the Cloud will allow only SELECT queries. INSERT, UPDATE, DELETE, and stored procedure queries will cause an error to be thrown.
The runtime key used for licensing.
string
""
The RTK property may be used to license a build.
The value in seconds until the timeout error is thrown, canceling the operation.
int
60
If Timeout = 0, operations do not time out. The operations run until they complete successfully or until they encounter an error condition.
If Timeout expires and the operation is not yet complete, the Cloud throws an exception.
A filepath pointing to the JSON configuration file containing your custom views.
string
""
User Defined Views are defined in a JSON-formatted configuration file called UserDefinedViews.json. The Cloud automatically detects the views specified in this file.
You can also have multiple view definitions and control them using the UserDefinedViews connection property. When you use this property, only the specified views are seen by the Cloud.
This User Defined View configuration file is formatted as follows:
For example:
{ "MyView": { "query": "SELECT * FROM Issues WHERE MyColumn = 'value'" }, "MyView2": { "query": "SELECT * FROM MyTable WHERE Id IN (1,2,3)" } }Use the UserDefinedViews connection property to specify the location of your JSON configuration file. For example:
"UserDefinedViews", "C:\\Users\\yourusername\\Desktop\\tmp\\UserDefinedViews.json"