Status | ||||
---|---|---|---|---|
|
Note | ||||||
---|---|---|---|---|---|---|
Documentation for
|
Excerpt |
---|
A workflow condition that allows you to hide/show a particular transition from the list of available transitions based on the status of issues related to the |
current issue. Checks the status of related issues (such as linked issues, Stories of an Epic, Epic of a Story, subtasks of an issue, issues returned by a Groovy script or a JQL search, etc.). The transition to which the condition is added will be available only if the issue's |
related issues are all in one of the selected statuses. |
Note |
---|
|
To add '
Related Issues Status Condition' to a transition:
- Click
Edit
for the workflow that has the transition you wish to configure the condition on. - In the Workflow Designer, select the transition.
- Click on
Conditions
in the properties panel. - Click on
Add
condition
. - Select
-
Related Issues Status Condition
from the list of conditions. - Click on
Add
to add the condition on the transition.
- Select the
Issue Link
drop-down, or leave it as Any
for any link type other than Issue/Subtask, Epic/Story and Jira Portfolio hierarchy- related issues from
Which issue(s)
drop-down - Select the issue type from the
Issue Type
field, or leave it asAny
for any issue type. - Select the status(es) from the
Statuses
field. - Click on
Add
to add the condition to the transition.
Panel |
---|
Related links : |
When you add this condition to a transition, the add-on checks the Status of the issue's linked related issues. If the linked related issues are all in one of the selected statuses, then then the transition will be available to the user. If not, the transition will be hidden.
Note |
---|
The list of statuses that is displayed under the |
You can further customize the condition using the following option:
Target Issues
Select the issues to check the constraints on. They can be:
Linked issues: Select issue(s) linked to the current issue through any link type or a specific link type such as
blocks
,is cloned by
, etc.Sub-tasks of the current issue: Select this option to operate on the sub-tasks of the current issue
Parent issue of the current sub-task: Select this option to operate on the parent of the current issue
Issues that belong to the current Epic: Select this option to operate on the issues that belong to the current Epic
Epic of the current issue: Select this option to operate on the Epic of the current issue
Child issues of the current issue in the Portfolio hierarchy: Select this option to operate on the child issues of the current issue in the Portfolio hierarchy
Parent issue of the current issue in the Portfolio hierarchy: Select this option to operate on the parent issue of the current issue in the Portfolio hierarchy
Issues returned by a Groovy script: Input a Groovy script that returns either a single Issue object, or a Collection of Issue objects, or a String representing the key of an issue, or a Collection of Strings each representing an issue key. For example:
"TEST-1"
["TEST-1","TEST-2"]
ComponentAccessor.issueManager.getIssueObject("TEST-1")
[ComponentAccessor.issueManager.getIssueObject("TEST-1"),ComponentAccessor.issueManager.getIssueObject("TEST-2")]
issue.parentObject
issue.getLinkedIssues()
Issues returned by a JQL search: Input a JQL search expression, including an optional Groovy Template markup. For example:
project = TEST
returns issues of the project with the key TESTproject = ${issue.get("project").key} and assignee = ${currentUser.name}
returns issues of the project the current issue belongs to and assigned to the current userTo operate on issues of a project with key
TEST
and issue type name same as the value in a text fieldCode Block <% if (issue.get("Single line text")) { %> project = TEST and issuetype = "${issue.get("Single line text")}" <% } else { %> issuekey=INVALID-1 <% } %>
Note |
---|
|