siblingIssuesUnderEpic()

This function returns an issue list containing sibling issues which are linked to same epic as the current issue.

The current issue will not be included in the output, except if it is an epic itself.

Only standard issues (no sub-tasks) will be returned and duplicates are being removed.

Syntax

siblingIssuesUnderEpic() #Output: Issue list

Parser expression	Description
siblingIssuesUnderEpic()	This example returns a list with the all issues linked to the same epic as the current issue, excluding the current issue, e.g.: [JWT-2, JWT-3, JWT-4]

This function returns an ISSUE LIST

Variant where you additionally define issues.

Duplicated issues are filtered from the output.

Syntax

siblingIssuesUnderEpic(issueList) #Output: Issue list

Parser expression	Description
siblingIssuesUnderEpic(linkedIssues("is blocked by"))	This example returns the issue list of all all issues linked to the same Epics as the issues blocking the current issue, excluding the blocking issue e.g.: [JWT-2, JWT-3, JWT-4] To achieve this the following functions are used: linkedIssues()

Parameters used in this function

Parameter	Input (data type)	Description
`issueList`	ISSUE LIST	Any given issue list. Usually this value is retrieved from a function (e.g. linkedIssues() or siblingIssuesUnderEpic()).

This function returns an ISSUE LIST

Variant where you define issue keys instead.

Syntax

siblingIssuesUnderEpic(issueKeys) #Output: Issue list

Parser expression	Description
siblingIssuesUnderEpic("CRM-15, HD-21")	This example returns an issue list of issues linked to the same epics as CRM-15 and HD-21. excluding issues with keys CRM-15 and HD-21 from the output.

Parameters used in this function

Parameter	Input (data type)	Description
`issueKeys`	TEXT	A comma separated list of issue keys.

This function returns an ISSUE LIST

If you want to include the given issues in the output, have a look at issuesUnderEpic() instead.

Use cases and examples

Use case
No content found.