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; } } }

Jira Edge Connector - Automation question

Tyler Groves_gen8r5

Hello,

I am using Jira Edge Connector in an automation rule to call some remote script. I am running the script on my machine in Docker. The connectivity etc is working and I can see that the script is running (this took a while to get setup). I see this log line -

DEBUG[2025-05-22T14:23:07.113832723Z] Successfully sent result of message[9dcb37b1-ef45-4685-be0c-7ffbd7991fd9] to Jira Service Management and it took 1.071570 seconds.

But I'm not sure how to access the value that is returned, in the automation rule or if this is even possible? The main issue I am having is that the JEC documentation is very light on details and understanding how it is supposed to work seem to be very trial and error based.

Does anyone else have experience using this successfully?

Accepted answers

All comments

Tyler Groves_gen8r5

For more clarity, I mean that Jira Edge Connect is running in docker and is executing the script and sending a response to Jira to confirm its completion. But it seems like it does not return and values.

Presumably this is designed to be invoked at the end of an automation rule?

Marc -Devoteam-

Hi @Tyler Groves

Welcome to the community.

There seems to be a smart values for that but currently only if on an enterprise plan.

You could see if anything works on your Premium plan.

"This action supports waiting for response only for Enterprise plan.

This action allows you to pause the rule until a response is received from JEC. When enabled, the rule will resume only if JEC returns a success response within the specified duration (up to 15 minutes). If no success response is received within this time, the rule will fail.

Additionally, you can configure the rule to resume in the following cases:

Resume on failed response: If JEC returns a failed response within the specified time, the rule will still resume.

Resume on no response: If JEC doesn’t return a response within the specified time, the rule will still resume.

To access the payload from JEC, use the {{jecAction.output}} smart value.

To determine the status of the response, you can use the smart value {{jecAction.status}} and it will display either "success" or "failed." In cases where no response is received, the value will be empty."

Tyler Groves_gen8r5

Thank you @Marc -Devoteam- for the quick response.

I've tried to access the smart values returned but it seems they have no value. As a test I tried to send the returned value to myself in an email (seemed easiest) but it has nothing (attached some images)

Screenshot 2025-05-22 at 16.21.23.png Screenshot 2025-05-22 at 16.22.12.png Screenshot 2025-05-22 at 16.06.12.png

I think it might be as you say that these features are reserved for enterprise licenced customers

Lee Geonhui

I am also facing the same problem.

It runs fine, but I can't get any response.I'm facing the same issue,

runs fine, but I can't get any response.

Marc -Devoteam-

Hi @geonhui.lee

Welcome to the community.

This only works if you have a Jira Enterprise subscription

Lee Geonhui

Hi @Marc -Devoteam-
I am using Jira Service Management Enterprise Cloud.

Does this functionality only apply to Jira Software Enterprise, or is Jira Service Management (JSM) Enterprise included as well?

From my understanding, JSM Enterprise should also be eligible for these features.

If my understanding is incorrect, could you please clarify?

Thank you.

Marc -Devoteam-

HI @geonhui.lee

It should work with JSM enterprise, see https://support.atlassian.com/cloud-automation/docs/use-jira-automation-with-jira-edge-connector-jec/

Matthew Lucas

I am also running JEC in docker. We are using custom actionMappings for on prem automation solutions. I was able to find the answer to this, as it is not documented on Atlassian's side but is quite hidden. It's worth noting, we do have enterprise licensing.

I expected jecAction.output to contain stdout from scripts we were executing, but that is not the case. You need to manually populate the return pipe that JEC will send into JSM/Jira automation.

You can find the answer hidden away in the JEC repository, in this python script. You need to add the "-jecNamedPipe" argument, and implement the writeCallback function as demonstrated (though there are a few syntax/logical errors in the example).

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management

jira-edge-connector