Jira Expressions in Workflow Validators

[perla.miranda]

I'm having an issue with Jira Expressions. I'm unclear on how to use if statements.

Goal: I've got an issue type of "Groundwork" that uses a workflow that is standard for all subtasks. When this groundwork status is updated to "Complete", I want to check that all sibling subtasks are assigned (because this is just part of the responsibilities for the person who completes the groundwork task). If any are Unassigned this transition should fail.

Steps Taken:

• In the workflow, I'm adding a validator during the transition to "Complete".
• I've looked at the Jira Expressions documentation: https://developer.atlassian.com/cloud/jira/platform/jira-expressions/

Problem:

• I'm unsure how to really use functions or if statements in Jira Expressions. I'm getting the following error and I'm unsure how to translate this into Jira Expressions. Error: "Jira expression failed to parse: line 3, column 1:\nexpression expected, reserved keyword 'if' encountered."

passesCondition = true

// if issue is groundwork type
if (issue.issueType.name.match('^(Groundwork)$') != null) {
    
    // get parent
    parentIssue = issue.parent

    // get subtasks
    def subTasks = parentIssue.getSubTaskObjects()

    // for each subtask
    subTasks.each {
        // if not assigned
        if (it.assignee == null)
             passesCondition = false
    } 
}
passesCondition 

Questions:

1. How can I translate the code above to Jira Expressions?
2. Are there any other alternatives, without Jira Automation?

[perla.miranda · Accepted solution]

Final answer:

If issue type is not Groundwork, automatically pass, otherwise, check sibling subtasks and assignee.

issue.issueType.name.match('^(Groundwork)$') == null || (issue.issueType.name.match('^(Groundwork)$') != null && issue.parent.subtasks.filter(subtask => subtask.assignee != null).length == issue.parent.subtasks.length)? true : false

[Chris Davies]

This doesn't address the OP's original situation or requirement but posting in case this helps others. The suggestion from @perla.miranda put me on the right tracks.

My requirement was to validate Custom Field A and:

- If it was null, the issue could transition

- If it was not null, make Custom Field B required.

This is the simple validator code that worked for me:

issue.customfield_A == null || issue.customfield_A != null && issue.customfield_B != null

[Vikrant Yadav]

Hi @perla.miranda  Kindly create a separate workflow for issue type "Groundwork" and apply following script in scripted validator on Complete transition :- 

  issue.subtasks.filter(subtask => subtask.assignee != null).length == issue.subtasks.length

Type an error message to show when the validator fails.

Thanks

V.Y

[perla.miranda]

@Vikrant Yadav Can you elaborate on this?

Groundwork is a "subtask" issue type, so this issue will not have any subtasks. I need to check that the siblings are assigned.

Also, the workflow is exactly the same as all other subtasks, so would I need to create a different workflow just to add a validator? Is there no way to check this with if statements?

The solution of duplicating a workflow just for a validator doesn't seem ideal. The Jira expression documentation mentions the following code for checking issue type:

issue.issueType.name.match('^(Groundwork)$')!= null

  I'm just unsure how to use this in combination with the other things that I need.

[Vikrant Yadav]

@perla.miranda  Okay, i thought "Groundwork" is a Parent task. 

Groundwork is subtask issue type, you want to check that all subtasks  of "Groundwork" subtask issue type only must be assigned before moving to complete status, right ? 

[perla.miranda]

No. Please look at the details in the post. Here is an explanation. Groundwork is a subtask. There are other sibling subtasks.

For example:

- Parent Issue
       - Groundwork subtask (when this is marked as complete, check that all other sibling subtasks are assigned)
       - subtask
       - subtask

[Vikrant Yadav]

@perla.miranda  Checked with Atlassian experts and documents, it's not possible to add if statement in JIRA expression. Meanwhile i suggest you to create a separate workflow for Groundwork issue type and apply above scripted validator. 

Thanks

[perla.miranda]

I took the code you mentioned before and modified it. I ended up doing the following which works. No need for a separate workflow since all subtasks use the same one and Groundwork is a subtask. Thanks!

issue.issueType.name.match('^(Groundwork)$') == null || (issue.issueType.name.match('^(Groundwork)$') != null && issue.parent.subtasks.filter(subtask => subtask.assignee != null).length == issue.parent.subtasks.length)? true : false

[Vikrant Yadav]

@perla.miranda  Great 😊 , Finally you made it.