On this page
| Function | |
|---|---|
| Type | |
| Use case description | This is one of the built-in usage examples and simply checks whether 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 | BEGINNER |
Configuration steps
Definition of basic (required) parameters
| Parameter | Value(s) / Steps to set value(s) | Notes |
|---|---|---|
Jira expression | issue.parent != null && (issue.parent.issueType.name == 'Story') | This expression makes sure that:
|
only works for su-tasks)Variations
You can easily modify this use case to check for specific statuses.
| Parameter | Value(s) / Steps to set value(s) | Notes |
|---|---|---|
Jira expression | issue.parent != null && (issue.parent.issueType.name == 'Bug') && ((issue.parent.status == 'To Do')) | This expression makes sure that:
|
| Jira expression | issue.parent != null && (issue.parent.issueType.name == 'Bug') && ((issue.parent.resolution != null)) | This expression makes sure that:
|
This is how it's done
<Screencast goes in here> Detailed instruction can be found here: https://www.decadis.net/confluence/display/XAPPSBRANDING/Screencasts+Framework
Use multimedia macro!
This is how it should look like
| Where | Final configuration |
|---|---|
| Backend | |
| Frontend |
Related examples
