Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×As some we are taking a lot of care not to mix cloud with self-hosted infrastructure... and open ports to our (hosted) jewel of the crown.
So despite having tons of jira automation, we never found a great way to trigger things from Jira itself, because of security risks.
Enter "Jira edge connector".
In short
- Take any of your vm, server,...
- Install jec
- Configure "actions"
- Each action when triggered will call bash, python, go... scripts (with key/value pairs)! and do whatever you want.
- Actions can be configured/triggered in "automation for jira".
Overall super simple, very efficient and communication is bottom-up (edge to jira-cloud) which does NOT require to open a port from Jira to edge.
This is a fantastic feature, and super happy it exists now. Solves a hell of issues.
But... I am crying.
To get it working in first direction, you need to have Jira service mgt premium or enterprise. Great it works for us (20 pax).
But this guy can give a feedback to Jira too (the other direction)... but....
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.
--------
Just checked... we are short 780 users to get Enterprise :-(
Hey Atlassian,... you are killing one of the most beautiful feature of your solution! Serious people will never trigger things seriously without having a feedback channel.
Hi Dominique, I think you are right. JEC has huge potential and we are also investigating what use cases make sense. The waiting for response should be in premium. Or at least offer it as an "add-on" service which you can purchase separately.
BTW the Enterprise plan is available for lower agent levels. You just need to contact sales.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.