Page History

linkedIssuesFromFilter()

Finds all issues which are linked by specified relation with those found by saved filter. When relationDirection is provided then relation should also be provided. 
When recursionNumber is specified then issues linked to found linked issues are also considered as a result.

Since version 2.10.0 we added relationDescription handling in queries.

Parameters:

• filter - could be given by name or its id.
• relation - is optional and given by name (about relation parameter more information in FAQ section), name of relation (or relation description) must match names that are set in configuration, by default they start with capital letter see more
• relationDescription  avilable since version 2.10.0  (about relation description parameter more information in FAQ section), must match descriptions that are set in configuration, see more
• relationDirection - optional, have values inward or outward (do not provide if you choose direction by relation description)
• recursionNumber - optional, have positive integer values (not supported with relation description parameter)

Syntax:

Examples:
Find all issues linked by any relation to all issues returned by filter myFilter

Find all issues linked by relation Duplicate to all issues returned by filter myFilter

Finds all issues linked by relation Duplicate in direction inward to all issues returned by filter myFilter

Find all issues linked by relation Duplicate in direction outward to all issues returned by filter myFilter

Find all issues linked by any relation to all issues returned by filter with id 102010

linkedIssuesFromQuery()

Finds all issues which are linked by specified relation with those found by JQL. When relationDirection is provided then relation should also be provided. 
When recursionNumber is specified then issues linked to found linked issues are also considered as a result.

Since version 2.10.0 we added relationDescription handling in queries.

Parameters:

• JQL- could be given by JQL query
• relation - is optional and given by name (about relation parameter more information in FAQ section), name of relation (or relation description) must match names that are set in configuration, by default they start with capital letter see more
• relationDescription  avilable since version 2.10.0  (about relation description parameter more information in FAQ section), must match descriptions that are set in configuration, see more
• relationDirection - optional, have values inward or outward (do not provide if you choose direction by relation description)
• recursionNumber - optional, have positive integer values (not supported with relation description parameter)

Syntax:

Examples:
Find all issues linked by any relation to all issues returned by JQL

Find all issues linked by relation Blocks to all issues returned by query issuekey >= X

Find all issues linked by relation Blocks in direction inward to all issues returned by JQL

Find all issues linked by relation Blocks in direction outward to all issues returned by JQL

Find all Y and Z, when X is blocked by Y and Y is blocked by Z? (Recursive lookup)

You have issues DEMO-1 cloned by DEMO-2, DEMO-2 cloned by DEMO-3, DEMO-3 cloned by DEMO-4. Finds issues clones DEMO-1 for only 2 recursive lookup, then JIRA will return DEMO-2, and DEMO-3

You have issues DEMO-1 duplicated by DEMO-2, DEMO-2 duplicated by DEMO-3, DEMO-3 duplicated by DEMO-4. Finds issues duplicats DEMO-1 for only 3 recursive lookup, then JIRA will return DEMO-2, DEMO-3 and DEMO-4.

parentIssuesFromFilter()

Finds all issues which are parents of subtasks issues selected by specified saved filter.

Parameters:

• filter - could be given by name or its id.

Syntax:

Examples:

Finds all parent issues for all issues returned by filter myFilter

Finds all parent issues for all issues returned by filter with id 102010

parentIssuesFromQuery()

Finds all issues which are parents of subtasks issues selected by JQL.

Parameters:

• JQL- could be given by JQL query

Syntax:

Examples:
Find all parent issues for all issues returned by JQL

subtaskIssuesFromFilter()

Finds all issues which are subtasks of issues selected by specified saved filter

Parameters:

• filter - could be given by name or its id.

Syntax:

Examples:
Find all subtask issues for all issues returned by filter myFilter

Find all subtask issues for all issues returned by filter with id 102010

subtaskIssuesFromQuery()

Finds all  issues which are subtasks of issues selected by JQL

Parameters:

• JQL- could be given by JQL query

Syntax:

Examples:
Find all subtask issues for all issues returned by JQL

numberOfLinkedIssuesFromQuery()

This function is available in 2.5.0 plugin version and later.

Finds all issues which number of linked issue meet a condition. Relation type and direction is not analyse by function so all linked issues are proceeded to check condition. Query has three required parameters.

Parameters:

• JQL- JQL query to analyse.
• mathematicalSymbol- available symbols ==, <=, !=, >=, >, <
• numberOfLinkedIssues- number of linked issues
  
  

Syntax:

Examples:
Finds all linked issues from DEMO project which contain more than two linked issues.

numberOfLinkedIssuesFromFilter()

This function is available in 2.5.0 plugin version and later.

Finds all issues which number of linked issue meet a condition. Relation type and direction is not analyse by function so all linked issues are proceeded to check condition. Query has three required parameters.

Parameters:

• filter - could be given by name or its id.
• mathematicalSymbol- available symbols ==, <=, !=, >=, >, <
• numberOfLinkedIssues- number of linked issues
  
  

Syntax:

Examples:
Finds all linked issues returned by myFilter which contain less than three linked issues.

Finds all linked issues returned by 102011 filter id which contain exacly one linked issue.

having...()

This function is available in 2.4.0 plugin version and later.

Since version 2.10.0 we added relationDescription handling in queries.
All the above functions have their  having...  counterparts:

havingLinkedIssuesFromQuery(...),  

havingLinkedIssuesFromFilter(...),  

havingSubtaskIssuesFromQuery(...), 

havingSubtaskIssuesFromFilter(...), 

havingParentIssuesFromQuery(...),  

havingParentIssuesFromFilter(...).

 
Those functions do the same task as the previously-existing functions, but return not the link 'targets', but link 'sources' that generated the targets. havingXXXX("subquery") is equivalent to: reversedXXX("") and subquery, (where "" is a subquery which matches all the issues).

For example:

returns those issues which are parents of some subtask issues, and contain linux text somewhere. This is equivalent to (but faster than) this query:

Note that this is not the same as query:

which returns parent issues of subtask issues containing linux (returned parents themselves don't have to contain linux).

Similarly other having... queries work.
 

epicsFromFilter()

This function is available in 2.9.0 version plugin version and later.

This function is available only with JIRA Software.

Function will return all Epics that where assigned to issues returned by given filter parameter.

Function allows you to discover all Epics that where used in your issue set. In this case issue set is defined as filter.

Parameters:

• filter - could be given by name or its id.
  
  

Syntax:

Examples:

epicsFromQuery()

This function is available in 2.9.0 version plugin version and later.

This function is available only with JIRA Software.

Function will return all Epics that where assigned to issues returned by given query parameter.

Function allows you to discover all Epics that where used in your issue set. In this case issue set is defined as query.

Parameters:

• JQL- could be given by JQL query
  
  

Syntax:

Examples:

epicsWithIssue()

This function is available in 2.9.0 version plugin version and later.

This function is available only with JIRA Software.

Function will returned all Epics that have at least one issue assigned. Function will search for all Epics in your JIRA instance.

Parameters: no

Syntax:

Examples:

epicsWithoutIssue()

This function is available in 2.9.0 version plugin version and later.

This function is available only with JIRA Software.

Function will returned all Epics that have no issues assigned. Function will check all Epics in your JIRA instance.

Parameters: no

Syntax:

Example: