Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel

On this page

Table of Contents
exclude(On this page).*
stylecircle
typeflat
separatorpipe



UI Text Box
sizemedium
typeinfo

Use case

Check whether the parent of the current issue is of a certain issue type.

This is particularly important if you want to reuse a workflow for multiple sub-task issue types but only want a transition to be available if the sub-task belongs to a certain user story or a bug.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.


Configuration

UI Steps


UI Step

Jira expression*

Code Block
linenumberstrue
issue.parent != null && (issue.parent.issueType.name == "Story")

This expression makes sure that:

  1. the current issue has a parent (only for sub-tasks)
  2. the parent is a Story


UI Step


UI Steps

Variations

You can easily modify this use case to check for specific statuses.

UI Step

Jira expression*

Code Block
linenumberstrue
issue.parent != null && (issue.parent.issueType.name == "Bug") 
&& ((issue.parent.status == "To Do"))

This expression makes sure that:

  1. the parent is a Bug
  2. the Bug is still in the
    Status
    subtletrue
    titleto do
    status


UI Step

Jira expression*

Code Block
linenumberstrue
issue.parent != null && (issue.parent.issueType.name == "Bug") 
&& ((issue.parent.resolution != null))

This expression makes sure that:

  1. the parent is a Bug
  2. the Bug is still unresolved.





Related examples

Page properties report
firstcolumnUse case
headingsJWT feature, Workflow function, Use case description, Complexity
sortByTitle
cqllabel = "use-case" and label = "jira_expression" and space = currentSpace()


Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue


Page properties
hiddentrue


JWT feature

Workflow function

Jira expression condition

Jira expression validator

Use case description

Check whether the parent of the current issue is of a certain issue type.

This is particularly important if you want to reuse a workflow for multiple sub-task issue types but only want a transition to be available if the sub-task belongs to a certain user story or a bug.

This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.

Complexity

Status
colourGrey
titleintermediate