Skip to end of banner
Go to start of banner

Related Issues Status Condition

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Are you using JMWE for Jira Cloud and want to learn how to use this condition? Head to our documentation here.

Documentation for JMWE 5.0.0 - 6.1.3 is available here.

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.

  • This post-function does not work with remote links (links to Jira issues residing on another Jira instance/server).

  • JMWE now considers "symmetrical" link types (such as "relates to") as one link direction instead of two on the configuration screens and in the condition's execution. 

To add 'Related Issues Status Condition' to a transition:

  1. Click Edit for the workflow that has the transition you wish to configure the condition on.

  2. In the Workflow Designer, select the transition.

  3. Click on Conditions in the properties panel.

  4. Click on Add condition.

  5. Select Related Issues Status Condition from the list of conditions.

  6. Click on Add to add the condition to the transition.

  7. Select the related issues from Which issue(s) drop-down

  8. Select the issue type from the Issue Type field, or leave it as Any for any issue type.

  9. Select the status(es) from the Statuses field.

  10. Click on Add to add the condition to the transition.

Related links :

When you add this condition to a transition, the add-on checks the Status of the issue's related issues. Based on the option selected under "Related Issues Status Condition#Mode" if the related issues satisfy the condition then the transition will be available to the user. If not, the transition will be hidden.

The list of statuses that is displayed under the Statuses field has all the statuses across different workflows. This is because the workflow of an issue and that of its related issues can be different.

You can further customize the condition using the following options:

Which 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 TEST

    • project = ${issue.get("project").key} and assignee = ${currentUser.name} returns issues of the project the current issue belongs to and assigned to the current user

    • To operate on issues of a project with key TEST and issue type name same as the value in a text field

      <% if (issue.get("Single line text")) { %>
    project = TEST and issuetype = "${issue.get("Single line text")}"
<% } else { %>
    issuekey=INVALID-1
<% } %>


  • Note that the <% if %> block is necessary to avoid an invalid JQL query when the Single-line text field is empty. In that case, the template will return a valid JQL query that returns no issue (issuekey=INVALID-1). This is in general applicable to JQL operating on select type fields with pre-determined values like Affects Version/s, Checkboxes etc.

  • The maximum number of issues returned by a valid JQL is limited to 1000.

Mode

  • All issues must be in the selected statuses below: All the related issues must be in one of the status(es) selected under "Statuses"

  • At least one issue must be in one of the selected statuses below: At least one related issue must be in one of the status(es) selected under "Statuses"

  • No issue must be in one of the selected statuses below: No issue must in one of the status(es) selected under "Statuses"

  • At least one issue must not be in one of the selected statuses below: At least one issue must not be in one of the statuses selected under "Statuses"

  • No labels