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

What is included when exporting an automation rule?

Adam Bang_vmjd4j

A user on the forum asked me to share an automation. The quickest way would be export the rule and have them import it, but I case the contents of the exported rule include a clientKey, an authorAccountId, Account_ID, ruleBillingHome and so on.

Is it safe to share exported rules?

Accepted answers

Bill Sheboy

Hi @Adam Bang

Yes, and...to the other suggestions:

I recommend sharing the following information rather than providing your rule's JSON export:

an explanation of what problem the rule is trying to solve
any known exceptions / gotchas for the rule, including maintenance needs
an image of the complete rule, in one continuous image for continuity
for complicated rules, images of the details, trigger, conditions, actions, and branches
the smart value expressions used, as plain text, allowing copy / pasting
an example of the audit log details showing the expected rule execution
all the above obfuscated, when needed

Consider sharing a rule this way in how one would write an article to explain a rule rather than providing the implementation for your site's configuration. I am currently writing my own parser / compiler / executer for such rules (outside of Jira) and there is definitely content in the export you may not want to share with others.

Kind regards,
Bill

All comments

John Funk

Hi Adam - It should include all of those when it exports. However, any keys will not match up with the keys in your instance. You just then need to do a little clean up to select the right values for those things.

Karan Sachdev

Hey @Adam Bang

The export contains the user info like account ID etc to provide an option to have the same user as the owner in your new site as well.

If you have any user picker fields in your rule and you're adding specific users there, that info is included as well (because account ID is the unique identifier).

I believe if they don't have the same users on their site, they can't fetch user info based on the account ID only.

You may share screenshots of your rule and have them create it manually on their site following the steps you've taken.

More info on import/export automation rules here: https://support.atlassian.com/cloud-automation/docs/import-and-export-jira-automation-rules/

Thanks!

Bill Sheboy

Hi @Adam Bang

Yes, and...to the other suggestions:

I recommend sharing the following information rather than providing your rule's JSON export:

an explanation of what problem the rule is trying to solve
any known exceptions / gotchas for the rule, including maintenance needs
an image of the complete rule, in one continuous image for continuity
for complicated rules, images of the details, trigger, conditions, actions, and branches
the smart value expressions used, as plain text, allowing copy / pasting
an example of the audit log details showing the expected rule execution
all the above obfuscated, when needed

Kind regards,
Bill

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud