nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation not working with Advanced compare condition

Boyd K

Jira Data Center 9.0.0 (self-managed/hosted) with Git Integration for Jira to integration with Gitlab 14.10 (self-managed/hosted). Our environment is closed and classified without not connection to the outside.

Trying to set up Automation to transition a Jira Issue when a Pull Request Merged if the "{{pullRequest.destinationBranch.name}} equals CM_test" condition is met. But, the Audit log states that the condition is not met. Not sure if my syntax is incorrect.

Accepted answers

Boyd K

The automation rule now works after I switched to "contains" instead of "equals" in my condition.

All comments

Stefan Salzl

Hi @Boyd K ,

Please try the following smart value:

{{pullRequest.destinationBranch}}

Furthermore for debugging you could add a "Log action" to write result of your smart value to your audit log to check if it´s correct.

In case this doesn´t help please provide some details (eg. a screenshot of your automation rule and the audit log).

Best
Stefan

Boyd K

I tried it with pullRequest.destination and the condition was not met. I added the Log actions to print out the pullRequest.destinationBranch and pullRequest.destinationBranch.name and the both list CM_test. Do I need quote marks around CM_test?

I wish I could simply attach a screenshot but I have no connection to the server which is on a closed classified system. So here is what the log shows:

Pull request trigger

  Issues found for the pull request

    id=10: [ISSUE-22]

Log action

  Log

    Branch is CM_test

Log action

  Log

    Branch name is CM_test

Advanced compare condition

  The following issues did not match the condition:

    ISSUE-22

Here is the Advanced compare condition I currently have:

If: Compare two values

  Check if:

    {{pullRequest.destinationBranch}}

    equals CM_test

Boyd K

I believe I understand why the condition that is not being satisfied which results in the rule not executing.

The workflow has a validator on that transition. Thus, with that validator not satisfied, the rule would not execute.

Does that sound like the possible cause? If so, we would need to rethink that transition in the workflow.

Boyd K

Well, the issue persists even after removing the validator from the workflow transition. In fact, I changed the action of the automation rule to set a field rather that execute a status transition. Still the condition of the automation rule is not met, though the Log action show the values that the condition should have been met. I have no idea what to do. Is the Advanced compare condition the correct check to use when checking pullRequest.destinationBranch or should I be using JQL condition or Related issues condition?

Boyd K

The automation rule now works after I switched to "contains" instead of "equals" in my condition.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

integration

automation