issuesUnderEpic()

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

The current issue will 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

issuesUnderEpic() #Output: Issue list

Parser expression	Description
%{issuesUnderEpic()}	This example returns an issue list with all issues linked to the same epic as the current issue, e.g. [JWT-2, JWT-3, JWT-4]

This function returns an ISSUE LIST

Variant where you additionally define an issue list.

Duplicated issues are filtered from the output.

Syntax

issuesUnderEpic(issueList) #Output: Issue list

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

Parameters used in this function

Parameter	Input (data type)	Description
`issueList`	ISSUELIST	Any given issue list.

This function returns an ISSUE LIST

Variant where you define issue keys instead.

syntax

issuesUnderEpic(issueKeys) #Output: Issue list

Parser expression

Description

%{issuesUnderEpic("CRM-15, HD-21")}

This example returns an issue list of issues linked to the same epics as CRN-15 and HD-21, e.g.

[CRM-22, CRM-23, HD-24, HD-26, HD-27]

%{issuesUnderEpic(%{issue.cf10112})}

This example returns an issue list of issues linked to the same epics as those that are stored in the custom field, e.g.

[JWT-2, JWT-3, JWT-4, HD-24, HD-26, HD-27]

Additional information

Parameters used in this function

Parameter	Input (data type)	Description
`issueKeys`	TEXT	A text containing issue keys sepparated by commas.

This function returns an ISSUE LIST

If you want to remove the given issues from the output have a look at siblingIssuesUnderEpic() instead.

Use cases and examples

Use case
No content found.