Functions

issues jqlxIssuesWithAllAttachmentsCreatedAfter(string jqlQuery, datetime date [, string extension])

Returns the issues, for which all their attachments were created after the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the extension parameter is specified, then for each issue takes the attachments, which have one of the extensions, specified in the extension parameter. Otherwise, for each issue takes all attachments of this issue.
• If all these attachments’ creation dates are higher than the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’;
• [optional] extension – comma-separated list of extensions. Example: ‘jpeg, png’.

issues jqlxIssuesWithAllAttachmentsCreatedBefore(string jqlQuery, datetime date [, string extension])

Returns the issues, for which all their attachments were created before the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the extension parameter is specified, then for each issue takes the attachments, which have one of the extensions, specified in the extension parameter. Otherwise, for each issue takes all attachments of this issue.
• If all these attachments’ creation dates are lower than the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’;
• [optional] extension – comma-separated list of extensions. Example: ‘jpeg, png’.

issues jqlxIssuesWithAllAttachmentsCreatedByUser(string jqlQuery, string user [, string extension])

Returns the issues, for which all their attachments were created by the specified user.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the extension parameter is specified, then for each issue takes the attachments, which have one of the extensions, specified in the extension parameter. Otherwise, for each issue takes all attachments of this issue.
• If all these attachments were created by the user, specified in the user parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• user – user login name to be compared to the attachments’ creator names. Example: ‘admin’;
• [optional] extension – comma-separated list of extensions. Example: ‘jpeg, png’.

issues jqlxIssuesWithAllAttachmentsCreatedOnDate(string jqlQuery, datetime date [, string extension])

Returns the issues, for which all their attachments were created on the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the extension parameter is specified, then for each issue takes the attachments, which have one of the extensions, specified in the extension parameter. Otherwise, for each issue takes all attachments of this issue.
• If all these attachments’ creation dates are equal to the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’;
• [optional] extension – comma-separated list of extensions. Example: ‘jpeg, png’.

issues jqlxIssuesWithAnyAttachmentsCreatedAfter(string jqlQuery, datetime date [, string extension])

Returns the issues, for which any of their attachments were created after the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the extension parameter is specified, then for each issue takes the attachments, which have one of the extensions, specified in the extension parameter. Otherwise, for each issue takes all attachments of this issue.
• If any of these attachments’ creation dates are higher than the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’;
• [optional] extension – comma-separated list of extensions. Example: ‘jpeg, png’.

issues jqlxIssuesWithAnyAttachmentsCreatedBefore(string jqlQuery, datetime date [, string extension])

Returns the issues, for which any of their attachments were created before the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the extension parameter is specified, then for each issue takes the attachments, which have one of the extensions, specified in the extension parameter. Otherwise, for each issue takes all attachments of this issue.
• If any of these attachments’ creation dates are lower than the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’;
• [optional] extension – comma-separated list of extensions. Example: ‘jpeg, png’.

issues jqlxIssuesWithAnyAttachmentsCreatedByUser(string jqlQuery, string user [, string extension])

Returns the issues, for which any of their attachments were created by the specified user.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the extension parameter is specified, then for each issue takes the attachments, which have one of the extensions, specified in the extension parameter. Otherwise, for each issue takes all attachments of this issue.
• If any of these attachments were created by the user, specified in the user parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• user – user login name to be compared to the attachments’ creator names. Example: ‘admin’;
• [optional] extension – comma-separated list of extensions. Example: ‘jpeg, png’.

issues jqlxIssuesWithAnyAttachmentsCreatedOnDate(string jqlQuery, datetime date [, string extension])

Returns the issues, for which any of their attachments were created on the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the extension parameter is specified, then for each issue takes the attachments, which have one of the extensions, specified in the extension parameter. Otherwise, for each issue takes all attachments of this issue.
• If any of these attachments’ creation dates are equal to the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’;
• [optional] extension – comma-separated list of extensions. Example: ‘jpeg, png’.

issues jqlxIssuesWithAttachmentCountEqualTo(string jqlQuery, long count [, string extension])

Returns the issues, for which the number of attachments with specified extension is equal to the specified number.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the extension parameter is specified, then for each issue takes the attachments, which have one of the extensions, specified in the extension parameter. Otherwise, for each issue takes all attachments of this issue.
• Counts the amount of such attachments and checks if this number is equal to the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the number of issues’ attachments. Example: 1;
• [optional] extension – comma-separated list of extensions. Example: ‘jpeg, png’.

issues jqlxIssuesWithAttachmentCountGreaterThan(string jqlQuery, long count [, string extension])

Datacenter Only

Returns the issues, for which the number of attachments with specified extension is greater than the specified number.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the extension parameter is specified, then for each issue takes the attachments, which have one of the extensions, specified in the extension parameter. Otherwise, for each issue takes all attachments of this issue.
• Counts the amount of such attachments and checks if this number is greater than the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the number of issues’ attachments. Example: 1;
• [optional] extension – comma-separated list of extensions. Example: ‘jpeg, png’.

issues jqlxIssuesWithAttachmentCountLessThan(string jqlQuery, long count [, string extension])

Returns the issues, for which the number of attachments with specified extension is less than the specified number.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the extension parameter is specified, then for each issue takes the attachments, which have one of the extensions, specified in the extension parameter. Otherwise, for each issue takes all attachments of this issue.
• Counts the amount of such attachments and checks if this number is smaller than the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the number of issues’ attachments. Example: 1;
• [optional] extension – comma-separated list of extensions. Example: ‘jpeg, png’.

issues jqlxHasAttachments(string jqlQuery)

New!

Returns the issues, out of the ones matching the JQL query, which have at least one attachment.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• Adds an issue to the result if it has at least one attachment.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’.

issues jqlxIssuesWithAllCommentsCreatedAfter(string jqlQuery, datetime date)

Returns the issues, for which all their comments were created after the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the comments of this issue.
• If all these comments’ creation dates are higher than the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’.

issues jqlxIssuesWithAllCommentsCreatedBefore(string jqlQuery, datetime date)

Returns the issues, for which all their comments were created before the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the comments of this issue.
• If all these comments’ creation dates are lower than the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’.

issues jqlxIssuesWithAllCommentsCreatedByUser(string jqlQuery, string user)

Retu Returns the issues, for which all their comments were created by the specified user.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the comments of this issue.
• If all these comments were created by the user, specified in the user parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• user – user login name to be compared to the comments’ creator names. Example: ‘admin’.

issues jqlxIssuesWithAllCommentsCreatedOnDate(string jqlQuery, datetime date)

Returns the issues, for which all their comments were created right at the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the comments of this issue.
• If all these comments’ creation dates are equal to the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’.

issues jqlxIssuesWithAnyCommentsCreatedAfter(string jqlQuery, datetime date)

Returns the issues, for which any of their comments were created after the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the comments of this issue.
• If any of these comments’ creation dates are higher than the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’.

issues jqlxIssuesWithAnyCommentsCreatedBefore(string jqlQuery, datetime date)

Returns the issues, for which any of their comments were created before the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the comments of this issue.
• If any of these comments’ creation dates are lower than the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’.

issues jqlxIssuesWithAnyCommentsCreatedByUser(string jqlQuery, string user)

Returns the issues, for which any of their comments were created by the specified user.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the comments of this issue.
• If any of these comments were created by the user, specified in the user parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• user – date to be compared to the comments’ creation dates. Example: ‘2020-01-01’.

issues jqlxIssuesWithAnyCommentsCreatedOnDate(string jqlQuery, datetime date)

Returns the issues, for which any of their comments were created right at the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the comments of this issue.
• If any of these comments’ creation dates are equal to the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’.

issues jqlxIssuesWithCommentCountEqualTo(string jqlQuery, long count)

Returns the issues, for which the number of comments is equal to the specified number.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the comments of this issue.
• Counts the amount of these comments and checks if this number is equal to the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the number of issues’ attachments. Example: 1.

issues jqlxIssuesWithCommentCountGreaterThan(string jqlQuery, long count)

Returns the issues, for which the number of comments is higher than the specified number.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the comments of this issue.
• Counts the amount of these comments and checks if this number is higher than the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the number of issues’ attachments. Example: 1.

issues jqlxIssuesWithCommentCountLessThan(string jqlQuery, long count)

Returns the issues, for which the number of comments is lower than the specified number.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the comments of this issue.
• Counts the amount of these comments and checks if this number is lower than the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the number of issues’ attachments. Example: 1.

issues jqlxHasComments(string jqlQuery)

New!

Returns the issues, out of the ones matching the JQL query, which have at least one comment.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• Adds an issue to the result if it has at least one comment.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’.

datetime jqlxDate(long year [, long month, long day])

Returns the datetime value for the specified year, month and day of month.

How it works:

• This function just converts specified parameters into a datetime value. Hours, minutes, seconds and milliseconds are set to zeroes.

Parameters:

• year – a year value. Example: ‘2020’;
• [optional] month – a 1-based month number. If not specified, 1 (January) is taken. Example: 1;
• [optional] day – a 1-based day of month. If not specified, 1 is taken. Example: 1.

datetime jqlxEndOfHalfYear([datetime date])

Returns the datetime value for the last day of the half year of the specified date.

How it works:

• If date parameter is specified, takes this date. Otherwise takes current date.
• Calculates the last month and the day of month of the half year, containing this date.
• Initializes the returned value with the year of the specified date, calculated month and day of month. Hours, minutes, seconds and milliseconds are set to zeroes.

Parameters:

• [optional] date – a date, which should be inside the found period. If not specified, current date is taken. Example: “2020-01-01”.

datetime jqlxEndOfQuarter([datetime date])

Returns the datetime value for the last day of the quarter of the specified date.

How it works:

• If date parameter is specified, takes this date. Otherwise takes current date.
• Calculates the last month and the day of month of the quarter, containing this date.
• Initializes the returned value with the year of the specified date, calculated month and day of month. Hours, minutes, seconds and milliseconds are set to zeroes.

Parameters:

• [optional] date – a date, which should be inside the found period. If not specified, current date is taken. Example: “2020-01-01”.

datetime jqlxStartOfHalfYear([datetime date])

Returns the datetime value for the first day of the half year of the specified date.

How it works:

• If date parameter is specified, takes this date. Otherwise takes current date.
• Calculates the first month and the day of month of the half year, containing this date.
• Initializes the returned value with the year of the specified date, calculated month and day of month. Hours, minutes, seconds and milliseconds are set to zeroes.

Parameters:

• [optional] date – a date, which should be inside the found period. If not specified, current date is taken. Example: “2020-01-01”.

datetime jqlxStartOfQuarter([datetime date])

Returns the datetime value for the first day of the quarter of the specified date.

How it works:

• If date parameter is specified, takes this date. Otherwise takes current date.
• Calculates the first month and the day of month of the quarter, containing this date.
• Initializes the returned value with the year of the specified date, calculated month and day of month. Hours, minutes, seconds and milliseconds are set to zeroes.

Parameters:

• [optional] date – a date, which should be inside the found period. If not specified, current date is taken. Example: “2020-01-01”.

issues jqlxIssuesWithDuplicateFieldValues(string jqlQuery, string fieldId [, boolean ignoreCase])

Returns all issues with duplicate values of the specified field. The issues, where specified field is absent, are ignored.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue reads the specified field value and counts the numbers of similar fields' values using this value.
• Returns the issues which have field value with at least two occurrences among this and other issues.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’.
• fieldId – an identified of the field to take values from. Example: ‘assignee’, ‘created’. You may read about how to determine field ID here.
• [optional] ignoreCase – a flag, which specifies, whether comparisons should be case sensitive or not. If not specified, case is ignored.

issues jqlxIssuesWithFieldValueEqualTo(string jqlQuery, string fieldId, string valueToCompare [, boolean ignoreCase])

Returns all issues with specified field value equal to the specified value.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue reads the specified field value and compares it to the valueToCompare parameter value.
• Returns the issues which have field values, equal to the specified one.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’.
• fieldId – an identified of the field to take values from. Example: ‘assignee’, ‘created’. You may read about how to determine field ID here.
• valueToCompare – a value to compare field values to. Example: ‘admin’, ‘2020-09-15 00:00’.
• [optional] ignoreCase – a flag, which specifies, whether comparisons should be case sensitive or not. If not specified, case is ignored.

issues jqlxIssuesWithFieldValueNotEqualTo(string jqlQuery, string fieldId, string valueToCompare [, boolean ignoreCase])

Returns all issues with specified field value not equal to the specified value.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue reads the specified field value and compares it to the valueToCompare parameter value.
• Returns the issues which have field values, not equal to the specified one.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’.
• fieldId – an identified of the field to take values from. Example: ‘assignee’, ‘created’. You may read about how to determine field ID here.
• valueToCompare – a value to compare field values to. Example: ‘admin’, ‘2020-09-15 00:00’.
• [optional] ignoreCase – a flag, which specifies, whether comparisons should be case sensitive or not. If not specified, case is ignored.

issues jqlxIssuesWithUniqueFieldValues(string jqlQuery, string fieldId [, boolean ignoreCase])

Returns all issues with unique values of the specified field. The issues, where specified field is absent, are ignored.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue reads the specified field value and counts the numbers of similar fields' values using this value.
• Returns the issues which have field value with only one occurrence among this and other issues.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’.
• fieldId – an identified of the field to take values from. Example: ‘assignee’, ‘created’. You may read about how to determine field ID here.
• [optional] ignoreCase – a flag, which specifies, whether comparisons should be case sensitive or not. If not specified, case is ignored.

issues jqlxBlockersOf(string jqlQuery)

Datacenter Only

Returns blockers for the issues conforming to the specified JQL query.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes all linked issues and takes such of them, which are linked with ‘blocks’ link type.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’.

issues jqlxClonesOf(string jqlQuery)

Datacenter Only

Returns clones for the issues conforming to the specified JQL query.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes all linked issues and takes such of them, which are linked with ‘clones’ link type.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’.

issues jqlxDuplicatesOf(string jqlQuery)

Datacenter Only

Returns duplicates for the issues conforming to the specified JQL query.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes all linked issues and takes such of them, which are linked with ‘duplicates’ link type.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’.

issues jqlxEpicsOf(string jqlQuery)

Datacenter Only

Returns epics for the issues conforming to the specified JQL query.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes all linked issues and takes such of them, which are linked with ‘epic of’ link type.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’.

issues jqlxIssuesWithLinkCountEqualTo(string jqlQuery, long count [, string linkTypes])

Returns all issues having equal number of links of specified type to the specified amount

Returns all the issues conforming to the specified JQL query, which have the same number of links as specified.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the linkTypes parameter is specified, then for each issue takes the links of the types, specified in the linkTypes parameter. If this parameter is not specified, takes all the links of this issue.
• Counts the amount of these links and checks if this number is equal to the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the number of issues’ links. Example: 1;
• [optional] linkTypes – comma-separated list of link types. Example: ‘blocks, duplicates’.

issues jqlxIssuesWithLinkCountGreaterThan(string jqlQuery, long count [, string linkTypes])

Returns all the issues conforming to the specified JQL query, which have bigger number of links than specified.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the linkTypes parameter is specified, then for each issue takes the links of the types, specified in the linkTypes parameter. If this parameter is not specified, takes all the links of this issue.
• Counts the amount of these links and checks if this number is bigger than the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the number of issues’ links. Example: 1;
• [optional] linkTypes – comma-separated list of link types. Example: ‘blocks, duplicates’.

issues jqlxIssuesWithLinkCountLessThan(string jqlQuery, long count [, string linkTypes])

Returns all the issues conforming to the specified JQL query, which have smaller number of links than specified.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the linkTypes parameter is specified, then for each issue takes the links of the types, specified in the linkTypes parameter. If this parameter is not specified, takes all the links of this issue.
• Counts the amount of these links and checks if this number is smaller than the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the number of issues’ links. Example: 1;
• [optional] linkTypes – comma-separated list of link types. Example: ‘blocks, duplicates’.

issues jqlxIssuesWithLinksOfTypes(string jqlQuery, string linkTypes)

Datacenter Only

Returns all the issues conforming to the specified JQL query, which have at least one link of the specified types.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue checks if it contains at least one link of the types, specified in linkTypes parameter. If it does, adds this issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• [optional] linkTypes – comma-separated list of link types. Example: ‘blocks, duplicates’.

issues jqlxLinkedIssues(string jqlQuery [, string linkTypes[, string linkFields]])

Datacenter Only

Returns all the linked issues for the issues conforming to the specified JQL query, taking into account link types.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• If the linkTypes parameter is specified, then for each issue takes all issues, linked with one of the link types, specified in the linkTypes parameter of specified linkField and adds it to the result. If this parameter is not specified, adds all linked issues to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• [optional] linkTypes – comma-separated list of link types. Example: ‘blocks, duplicates’. Either inward, outward descriptions, or link names may be specified
• [optional] linkFields – link field to be checked, one of the following: “Inward”, “Outward”, “Name” or “Any”. Specify this parameter if only one of the field types should be checked, for example for the case when link name and inward description are the same. If this parameter is not specified, any field is taken.

issues jqlxFlattenedTwoLevelTree(string jqlQuery [, string linkTypes[, string linkFields]])

Datacenter Only

Returns the issues conforming to the specified JQL query together with all issues directly linked to them, combined into a single flat list – for example, to flatten an Epic-and-its-Stories tree into one report.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter, and adds them to the result.
• If the linkTypes parameter is specified, then for each issue also takes the issues linked with one of the link types, specified in the linkTypes parameter of the specified linkFields, and adds them to the result. If this parameter is not specified, all directly linked issues are added.
• Each issue appears in the result only once, even if it is reachable through several links.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: “Project=TST”;
• [optional] linkTypes – comma-separated list of link types. Example: “blocks, duplicates”. Either inward, outward descriptions, or link names may be specified
• [optional] linkFields – link field to be checked, one of the following: “Inward”, “Outward”, “Name” or “Any”. Specify this parameter if only one of the field types should be checked, for example for the case when link name and inward description are the same. If this parameter is not specified, any field is taken.

issues jqlxHasLinks(string jqlQuery)

New!

Returns the issues, out of the ones matching the JQL query, which have at least one issue link of any type, inward or outward.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• Adds an issue to the result if it has at least one issue link.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’.

issues jqlxIssuesWithAllSubTasksCreatedAfter(string jqlQuery, datetime date)

Returns the issues, for which all their subtasks were created after the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the subtasks of this issue.
• If all these subtasks’ creation dates are higher than the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’.

issues jqlxIssuesWithAllSubTasksCreatedBefore(string jqlQuery, datetime date)

Returns the issues, for which all their subtasks were created before the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the subtasks of this issue.
• If all these subtasks’ creation dates are lower than the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’.

issues jqlxIssuesWithAllSubTasksCreatedByUser(string jqlQuery, string user)

Retu Returns the issues, for which all their subtasks were created by the specified user.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the subtasks of this issue.
• If all these subtasks were created by the user, specified in the user parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• user – user login name to be compared to the subtasks’ creator names. Example: ‘admin’.

issues jqlxIssuesWithAllSubTasksCreatedOnDate(string jqlQuery, datetime date)

Returns the issues, for which all their subtasks were created right at the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the subtasks of this issue.
• If all these subtasks’ creation dates are equal to the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’.

issues jqlxIssuesWithAnySubTasksCreatedAfter(string jqlQuery, datetime date)

Returns the issues, for which any of their subtasks were created after the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the subtasks of this issue.
• If any of these subtasks’ creation dates are higher than the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’.

issues jqlxIssuesWithAnySubTasksCreatedBefore(string jqlQuery, datetime date)

Returns the issues, for which any of their subtasks were created before the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the subtasks of this issue.
• If any of these subtasks’ creation dates are lower than the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’.

issues jqlxIssuesWithAnySubTasksCreatedByUser(string jqlQuery, string user)

Returns the issues, for which any of their subtasks were created by the specified user.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the subtasks of this issue.
• If any of these subtasks were created by the user, specified in the user parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• user – date to be compared to the subtasks’ creation dates. Example: ‘2020-01-01’.

issues jqlxIssuesWithAnySubTasksCreatedOnDate(string jqlQuery, datetime date)

Returns the issues, for which any of their subtasks were created right at the specified date.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the subtasks of this issue.
• If any of these subtasks’ creation dates are equal to the date, specified in the date parameter, adds an issue to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• date – date to be compared to the attachments’ creation dates. Example: ‘2020-01-01’.

issues jqlxIssuesWithSubTaskCountEqualTo(string jqlQuery, long count)

Returns the issues, for which the number of subtasks is equal to the specified number.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the subtasks of this issue.
• Counts the amount of these subtasks and checks if this number is equal to the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the number of issues’ attachments. Example: 1.

issues jqlxIssuesWithSubTaskCountGreaterThan(string jqlQuery, long count)

Returns the issues, for which the number of subtasks is higher than the specified number.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the subtasks of this issue.
• Counts the amount of these subtasks and checks if this number is higher than the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the number of issues’ attachments. Example: 1.

issues jqlxIssuesWithSubTaskCountLessThan(string jqlQuery, long count)

Returns the issues, for which the number of subtasks is lower than the specified number.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes the subtasks of this issue.
• Counts the amount of these subtasks and checks if this number is lower than the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the number of issues’ attachments. Example: 1.

issues jqlxHasSubTasks(string jqlQuery)

New!

Returns the issues, out of the ones matching the JQL query, which have at least one subtask.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• Adds an issue to the result if it has at least one subtask.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’.

issues jqlxChildIssuesOf(string jqlQuery)

New! Datacenter Only

Returns the subtasks of every issue matching the JQL query.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes its subtasks and adds them to the result.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’.

issues jqlxIssuesWithWatcherCountEqualTo(string jqlQuery, long count)

New!

Returns the issues, for which the number of watchers is equal to the specified number.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• Counts the watchers of each issue and checks if this number is equal to the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the count. Example: 1.

issues jqlxIssuesWithWatcherCountGreaterThan(string jqlQuery, long count)

New!

Returns the issues, for which the number of watchers is higher than the specified number.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• Counts the watchers of each issue and checks if this number is higher than the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the count. Example: 1.

issues jqlxIssuesWithWatcherCountLessThan(string jqlQuery, long count)

New!

Returns the issues, for which the number of watchers is lower than the specified number.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• Counts the watchers of each issue and checks if this number is lower than the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the count. Example: 1.

issues jqlxIssuesWatchedByUser(string jqlQuery, string user)

New!

Returns the issues, out of the ones matching the JQL query, which are currently watched by the specified user.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• Adds an issue to the result if the user, specified in the user parameter, is watching it.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• user – user login name. Example: ‘admin’.

issues jqlxIssuesWithVoteCountGreaterThan(string jqlQuery, long count)

New!

Returns the issues, for which the number of votes is higher than the specified number.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• Counts the votes of each issue and checks if this number is higher than the number, specified in the count parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• count – number to be compared to the count. Example: 1.

issues jqlxIssuesWithWorklogsByUser(string jqlQuery, string user)

New!

Returns the issues, out of the ones matching the JQL query, which have at least one worklog entry logged by the specified user.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• For each issue takes its worklog entries.
• Adds an issue to the result if at least one worklog entry was logged by the user, specified in the user parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• user – user login name. Example: ‘admin’.

issues jqlxIssuesInProjectsLedBy(string jqlQuery, string user)

New!

Returns the issues, out of the ones matching the JQL query, whose project is led by the specified user.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• Adds an issue to the result if its project's lead is the user, specified in the user parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• user – user login name. Example: ‘admin’.

issues jqlxIssuesWithAssigneeInGroup(string jqlQuery, string group)

New!

Returns the issues, out of the ones matching the JQL query, whose assignee is a member of the specified group.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• Adds an issue to the result if its assignee is a member of the group, specified in the group parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• group – group name. Example: ‘developers’.

issues jqlxIssuesWithReporterInGroup(string jqlQuery, string group)

New!

Returns the issues, out of the ones matching the JQL query, whose reporter is a member of the specified group.

How it works:

• Takes issues conforming to the JQL query, specified in the jqlQuery parameter.
• Adds an issue to the result if its reporter is a member of the group, specified in the group parameter.

Parameters:

• jqlQuery – query to select an initial set of issues. Example: ‘Project=TST’;
• group – group name. Example: ‘developers’.